feat(server): add oRPC 2 control-plane transport

[RedStar071]

Summary

Adds apps/server: a typed oRPC 2 control-plane transport exposing health, tasks.list/get/create, and approvals.decide over a plain Node HTTP listener, plus one aggregate GET /api/dashboard endpoint for the dashboard to consume. This restores the control-plane half of the productionization work merged as PR #21 (6277cd2 in the original branch), which was stripped out of that PR before merge — main currently ships the frontend-only dashboard shell with no data source behind it.

Review follow-up (97be63c)

Control-plane mutations now fail closed behind an operator-issued access policy: AGENT_ZERO_CONTROL_PLANE_TOKENS (comma-separated name:token bearer credentials) authenticates callers, AGENT_ZERO_CONTROL_PLANE_REPOSITORIES allow-lists the paths tasks.create may target, and approval decisions record the authenticated principal's name instead of a wire-supplied actor. Reads stay open for the dashboard.

constauthenticated=procedure.use(({ context, next })=>{constprincipal=context.principal;if(!principal)thrownewORPCError('UNAUTHORIZED',{message: 'Authentication required'});returnnext({context: { principal }});});

TaskScheduler also now enforces maxQueued for per-repository-blocked submissions even while global capacity is free, so blocked work can no longer grow the queue without bound.

Review follow-up (5e838dd)

Execution modes are now part of the per-principal policy: AGENT_ZERO_CONTROL_PLANE_MODES (comma-separated name:mode|mode grants) controls which modes each principal may request, tasks.create rejects ungranted modes, and principals without a grant are limited to the non-writable observe and suggest modes, so fix and autonomous require an explicit operator grant.

Why

main's apps/dashboard has no backend: the index page renders an empty DashboardOverview with a no-op refresh. apps/server is the composition root that resolves repository policy, constructs a runner, persists task history, and schedules work — the missing piece the dashboard is meant to read from.

Ported forward rather than copied verbatim, adapted to main as it stands after #22 (runner write-anchoring/local review scope) and #23 (Node 22.18 baseline):

• Built with tsdown like packages/cli, instead of the Nitro 3 beta + vue-tsc pipeline apps/dashboard already owns (Nitro 3/h3 v2/unstorage are all pre-release; a plain Node HTTP listener needed none of that).
• Persistence is a KeyValueStorage contract with a filesystem implementation by default (FileKeyValueStorage), so Redis, KV, or a Nitro storage driver drop in unchanged without pulling Nitro into this package.
• Listens on port 3001 by default (PORT env override) so aube run dev can start the dashboard (3000) and the control plane together without a port collision.

Verification

• aube run check:repo
• aube run lint:ci
• aube run typecheck
• aube test — all packages pass except @agent-zero/runner, which has 2 pre-existing Windows-only failures (descriptor-anchored writes are not supported on this platform) unrelated to this change and already present on main after fix(runner): resolve unresolved review feedback on write anchoring and local review scope #22; every other package, including the new apps/server (42/42 tests), passes.
• aube run build

Safety and compatibility

• Added deterministic tests for the new package: router.test.ts (ported), control-plane.test.ts (ported), rpc.test.ts, dashboard.test.ts, storage.test.ts, index.test.ts — none touch the network or depend on wall-clock timing.
• observe stays read-only; the control plane's runTask is the same composition root the CLI uses and still resolves mayModifyRepository before constructing a runner.
• Runtime commands and target-repository writes stay behind packages/runner; apps/server only validates, delegates, and persists.
• Stored task records are redacted (redactSecrets) before persistence and never include review input or checkout paths.
• Updated docs/architecture.md, AGENTS.md/CLAUDE.md, README.md, and added the orpc-server Agent Skill (with its .agents/skills symlink) describing the transport's boundaries.

Reviewer notes

• oRPC pinned to 2.0.0-beta.26 (same version the original branch used) since 2.x is still in beta; @orpc/server's stable 1.x line predates the context-based procedure API this router relies on.
• packages/runner's 2 failing tests are unrelated to this PR — they fail identically on main at c3642cf on this Windows environment and are out of scope here.

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is enabled.}

Confidence Score: 5/5

No blocking failure remains.

No accepted blocking findings remain after the scheduler capacity scenario was exercised against the current implementation.

T-Rex Logs

What T-Rex did

• Prepared a narrow authorization harness for anonymous task creation and approvals, then attempted a focused RPC test, but the run could not start because the Aube package manager is unavailable.
• Used a self-contained Node harness to exercise the repository queue path before and after the change; before the change a third repository-A submission with active=1 and queued=1 grew the queue to two, but after the change the same submission was rejected with TaskQueueQuotaError and the queue remained at one.
• Documented that rpc.ts applies authenticated middleware to mutations, derives the approval actor from context.principal.name, rejects ungranted modes, and that approvalInput does not accept an actor field; the executable harness failed to load due to module resolution for @orpc/server and the missing Aube dependency blocked the focused test.
• Compared the pre- and post-change queue states and observed the quota-bound behavior: the pre-change run accepted a third submission (active=1, queued=1, queue became 2) while the post-change run rejected with TaskQueueQuotaError and left the queue at active=1, queued=1; initial Vitest execution could not run due to missing dependencies and Aube, but the self-contained harness exercised the scheduler path.

_{Ran code and verified through T-Rex}

_{Reviews (3): Last reviewed commit: "fix(server): validate mode grants with a..." | Re-trigger Greptile}

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	esbuild@​0.28.2
	@​orpc/​server@​2.0.0-beta.26
	@​agent-zero/​github@​0.3.0	N/A	N/A	N/A	N/A	N/A

View full report