orpc-v2: merge citynode.app into everything-dev main and reconcile repo identity

Ticket ID: M1

Parent

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

What to build

Merge citynode.app's history into everything-dev main (post-M0 this is a fast-forward or trivially clean merge), making everything-dev the single platform home containing the full citynode work (geo/nodes/validators API, dashboard UI, regression suites, CLI improvements).

Reconcile the fork's citynode-specific identity with upstream's platform identity:

• everything-dev keeps its identity as the everything.dev platform repo (AGENTS.md self-description, README, its own bos.config.json).
• citynode's production publish path stays reproducible after the merge — record the decision where citynode's runtime config (bos://v1.citynode.near/citynode.app) lives until the planned break-off child repo (in-repo citynode-specific config vs fork-side).
• Repo docs that currently point at NEARBuilders/citynode.app as tracker/home (docs/agents/issue-tracker.md, AGENTS.md) updated for the consolidated repo.

Acceptance criteria

• everything-dev main contains the fork's full history; upstream CI green on the merge commit
• Repo identity docs coherent: everything.dev platform home, citynode deploy path documented
• citynode runtime still publishable from the post-merge tree (bos publish dry-run or equivalent verification)
• plans/infra/orpc-v2-effect-migration.md and the docs/agents skills layout available on upstream main

Blocked by

• #249 — sync citynode.app main with everything-dev

Start with blocked issue #249 and inspect the merge history, then review AGENTS.md, README, bos.config.json, docs/agents/issue-tracker.md, and plans/infra/orpc-v2-effect-migration.md. Verify the consolidated tree and upstream CI, document the citynode runtime configuration location, and run a bos publish dry-run or equivalent to confirm the production path remains publishable.