orpc-v2: atomic integrate, verify, and release (changesets, npm, redeploy)

Ticket ID: B7

Parent

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

What to build

Stage B gate — the integrate-and-verify ticket where green is finally promised. On the orpc-v2 branch: full monorepo test/lint/typecheck, browser + api regression suites against a spawned stack, dev-stack smoke, bos mf check. Then atomic merge + release:

• Merge orpc-v2 to main in one piece.
• Changesets + npm publish for every-plugin and everything-dev so generated child repos can bos upgrade.
• Redeploy the everything.dev runtime (bos publish --deploy) and spot-check key routes + MCP.
• Update repo docs for the new patterns (scoped-resources guidance → Layer pattern; publisher rename notes; AGENTS.md common-pattern sections).

Acceptance criteria

• orpc-v2 branch fully green (tests, lint, typecheck, regression suites, mf check)
• Merged to main atomically; CI green on main
• every-plugin + everything-dev published to npm; scratch-child bos upgrade verified
• everything.dev runtime redeployed and healthy (routes + MCP spot-check)
• Docs updated for the new plugin patterns

Blocked by

• #261 — migrate _template scaffold to the new plugin API
• #262 — migrate auth plugin to the new plugin API
• #263 — migrate apps and votes plugins to the new plugin API
• #264 — migrate proposals plugin to the new plugin API
• #265 — host handlers, OpenAPI 3.1.1 pin, and MCP tool generation
• #266 — UI client and everything-dev type-gen on v2 types

Start on the orpc-v2 branch by reviewing the acceptance criteria and the blocked issues #261–#266. Run the listed tests, lint, typecheck, regression suites, dev-stack smoke checks, and bos mf check before attempting the atomic merge. Done means main is green, packages are published, bos upgrade succeeds in a scratch child, everything.dev is healthy, and the documented plugin patterns are updated.