orpc-v2: every-plugin on Effect 4

Ticket ID: A2

Parent

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

What to build

Stage A, step 1: migrate the every-plugin package to Effect 4 — runtime services, plugin loader, build/runtime internals, and its full test suite (unit, integration, fixtures plugin). Wire-compatible: no oRPC version changes, no public API changes — host and plugins compile and run unchanged against it.

Acceptance criteria

• every-plugin on effect 4.0.0-rc.112 (workspace + catalog), oRPC untouched
• every-plugin unit + integration suites green, including fixtures plugin loading
• Public API unchanged — host/api/plugins typecheck against it without modification
• bos dev smoke: plugin loads over Module Federation with a single effect singleton

Blocked by

• #253 — Effect 4 + oRPC v2 feasibility spike (hard gate)

Start with the every-plugin package and wait for the #253 feasibility spike, then inspect its runtime services, plugin loader, build/runtime internals, and unit and integration suites. Include the fixtures plugin and host/api/plugins typechecks, then run the bos dev smoke test; done means Effect 4 works without oRPC or public API changes and plugins load with one effect singleton.