orpc-v2: citynode.app adopts the migrated platform and redeploys its runtime

Ticket ID: B8

Parent

#248 — orpc-v2: consolidate fork into everything-dev and migrate platform to oRPC v2 + Effect 4 (epic)

What to build

Completion: citynode.app takes the migrated platform. Fast-forward the fork (or its post-M1 equivalent) to the migrated upstream main — the M1 identity reconciliation decides exactly which tree publishes. Atomically redeploy the citynode runtime (bos publish --deploy from the reconciled config, bos://v1.citynode.near/citynode.app) and coordinate external API consumers (deployed-URL and API-key users) through the cutover. Verify production end-to-end. A follow-up epic (out of scope) then breaks citynode.app off as a pure child app.

Acceptance criteria

• citynode source tree at migrated upstream main (identity reconciliation intact)
• bos publish --deploy completes; runtime healthy at the citynode gateway
• Production spot-checks green (sign-in, key app routes, MCP/API surfaces)
• External consumers confirmed unbroken through the cutover

Blocked by

• #267 — atomic integrate, verify, and release

Start with blocked issue #267 and the M1 identity reconciliation that determines the publishing tree. Inspect the reconciled citynode source, then run bos publish --deploy for bos://v1.citynode.near/citynode.app. Done means the runtime is healthy, sign-in and key routes work, MCP/API surfaces pass, and external consumers remain unbroken.