fix(api): recover cold worker initialization

[Makisuo]

Summary

• evict and dispose the exact cached HTTP handler when its real first request exposes a lazy layer-acquisition failure
• acquire the ManagedRuntime context before caching RPC initialization, disposing failed builds so later calls can retry
• add a small recoverable promise memo with identity-guarded eviction for overlapping requests
• add regression coverage for concurrent memoization, rejected-build eviction, lazy HTTP layer acquisition, and lazy ManagedRuntime acquisition

Context

Follow-up to #594. Effect rc.108 acquires both HttpRouter.toWebHandler layers and ManagedRuntime layers lazily. The previous outer promise memoizers resolved before that work happened, so their rejection handlers could not evict a failed inner build; one first-acquisition defect could pin the isolate until eviction.

HTTP recovery now happens only when a real application request rejects during lazy handler acquisition. That exact cached wrapper is evicted and disposed, allowing the next request to rebuild it. RPC initialization awaits runtime.context() so acquisition failure remains inside the recoverable build promise.

The existing inline health and OPTIONS fast paths are unchanged.

Validation

• API focused tests: 5 passed
• API typecheck through the Turbo dependency graph
• oxlint on all changed files
• Wrangler deploy dry-run bundle succeeded

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

[github-actions]

🍁 Maple PR preview

Note

Preview resources were removed when this pull request closed.

Final commit 80e4b32 · View workflow run