Fix dashboard Codex capacity accounting

[hxy91819]

Summary

• count only jobs that execute Codex against the 128-slot worker budget
• expose independent review-admission and result-publication queue telemetry while preserving legacy aggregate fields
• report publisher, comment-router, and reconciler workflows as GitHub Actions control-plane load
• render the capacity surfaces separately on desktop and mobile

Root cause

The dashboard's workflow fallback used a broad name match for review, codex, repair, worker, or commit. That classified deterministic clawsweeper_comment, exact publication, comment-sync, and lease-reconciliation workflows as Codex workers whenever job detail was unavailable. The exact-review API also exposed only a mixed aggregate even though review and publication already have independent admission limits.

This made control-plane runner pressure consume the displayed 128-slot Codex budget and hid which exact-review lane was saturated.

Compatibility and safety

• Existing top-level /api/exact-review-queue fields remain unchanged; lanes.review and lanes.publication are additive.
• No Durable Object state shape, dispatch, retry, capacity, workflow concurrency, or GitHub mutation behavior changes.
• feat(dashboard): OpenClaw Bay improvements #597 is not modified or used as a dependency.

Validation

• pnpm run check (Node 24): passed
• dashboard build, lint, smoke, operational-health, exact-review-health, and dashboard-worker tests: passed (130 tests in the focused autoreview run)
• post-rebase focused regression tests: passed
• git diff --check: passed
• autoreview with Codex gpt-5.6-sol: clean after addressing two in-scope findings (over-budget display and comment-sync control-plane classification)

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[brokemac79]

@hxy91819 - can i ask you to not merge anything to clawsweeper for now pls - need to get it stable