sandbox proxy: archived logical-running sandboxes cannot be restored #73

What happened

The sandbox proxy accepts an archived, deadline-free sandbox as logically running but calls wakeSandbox directly and has no Archiver dependency. Direct wake explicitly rejects archived and restoring rows.

Reproduction:

1. Create a native sandbox with no deadline.
2. Cool it through frozen, stopped, and archived using the scanner and Archiver.
3. Request its wildcard port-proxy hostname.
4. Make an envd filesystem request to the same sandbox for comparison.

Expected: Traffic to an eligible logical-running sandbox should join restoration and then proxy the request.

Actual: The proxy returns HTTP 502, leaves the row archived, and does not consume the archive object. The subsequent envd request restores the same sandbox and succeeds.

Impact: Preview and service URLs for logically-running archived sandboxes remain unavailable until another restore-capable control-plane or envd operation intervenes.

dor doctor output

Not applicable — the proxy behavior was reproduced with real sockets and the focused scanner, Archiver, ledger, and fake executor and does not depend on installed-host readiness. dor doctor was not run.

Environment

• Reproduction mode: Focused-source reproduction
• Dormice commit: 4417ae14938273f5d937c476cf7cdc57e22e53a5
• Executor: fake
• Transport: real sockets
• Verification: Verified with real sockets, the current Fastify app, scanner, MemStore-backed Archiver, ledger, and FakeExecutor at 4417ae14938273f5d937c476cf7cdc57e22e53a5.