/api/usage route missing on the engine (Organization + Run-Agents views 404)

[TonsOfFun]

Part of an ActiveAgent + actionagent dashboard functional review (multi-agent, adversarially verified). Severity: 🟡 Minor.

Findings

Engine dashboard calls <mount>/api/usage, a route the engine does not define (404)

• Where: actionagent/frontend/components/dashboard/OrganizationView.jsx:21 · severity: major · kind: missing · repo: activeagent
• What breaks: OrganizationView.jsx:21 and SandboxRunner.jsx:186 both fetch <mount>/api/usage, but actionagent/config/routes.rb defines no usage resource under the api namespace. Live-proof: GET http://localhost:3001/activeagents/api/usage returns 404 while driving the Organization and Run-Agents views in a browser. The platform app has this route (app/controllers/api/usage_controller.rb); the engine never gained it during extraction.
• Evidence: Browser sweep of the mounted engine dashboard (test/dummy at /activeagents) recorded "HTTP 404 GET http://localhost:3001/activeagents/api/usage" on the Organization and Run-Agents views; grep confirms the two callers and the absence of a usage route in actionagent/config/routes.rb.
• Suggested fix: Either add a usage route+controller to the engine (backed by ActionAgent's host-provided usage_counter seam, so a host that wires quotas gets real numbers and a bare mount gets zeros), or make the two callers degrade gracefully (treat a 404 as "usage reporting unavailable" and hide the meter) instead of leaving the fetch to fail.

Verification

Each finding above was produced by a dedicated per-feature review agent, then confirmed by an independent adversarial verifier (all rated high-confidence; zero rejected in this set). File:line citations are against the current main/HEAD of each repo; many were reproduced live against a booted dashboard.