https://entire.com/gh/phaseoteam/-/trails/148/changes/Phaseo/148

IMPORTANT

Merge only after phaseo-realtime exists. First run the Realtime relay deploy workflow with initial=true; the realtime-maintenance skill covers the first deploy. Merging first would make the gateway deploy fail, because the binding would point at a Worker that doesn't exist.

What changed

• phaseo-gateway (wrangler.toml) and phaseo-jobs (wrangler.jobs.toml) bind REALTIME_RELAY with script_name = "phaseo-realtime". Relay connections and reconciliation calls now go to the relay Worker added in #3367.
• phaseo-gateway still exports its old RealtimeRelayDurableObject class and keeps its migration, so nothing is deleted. Removing it later is a destructive migration that needs explicit approval.
• A config test checks both bindings. A changeset is included.

Why

Every merge to main deploys phaseo-gateway, and a deploy restarts the Durable Objects it hosts, which ends every live realtime call. #3367 added phaseo-realtime, which deploys only in maintenance windows. In a test with throwaway Workers, redeploying a Worker that forwards a WebSocket to a Durable Object in another Worker didn't cut the connection over 9+ minutes. Redeploying the Durable Object's own Worker cut it about 4 minutes later. This PR is the switch that puts live calls behind that protection.

How

• Binding only: clients still connect through api.phaseo.app, and the gateway's relay route forwards to the binding as before, so SDKs and URLs don't change.
• Fresh namespace: the new Worker's namespace has no state, and none is needed. No realtime session has run in production since 2026-09-11.
• Calls in progress: any call in the gateway's old namespace ends when this deploy lands, like any gateway deploy today. The skill says to check the live-session count first.

Before and after

Verification

• wrangler deploy --dry-run (gateway): env.REALTIME_RELAY (RealtimeRelayDurableObject, defined in phaseo-realtime). Same for pnpm run build:jobs.
• vitest run src/realtime-worker-config.test.ts: 4 passed. With main's wrangler.toml restored, the new binding test fails (1 failed, 3 passed).
• Not verified yet: a connection through production after the switch. Once deployed, I'll run the skill's relay probe, which expects 401 realtime session not found or token invalid from the relay.

Model: Claude Opus 5.5 (effort unknown) · Harness: Claude Code in T3 Code

🤖 Generated with Claude Code