[Admin][UI] Errors & Ops page

[serge-ivo]

[Admin][UI] Errors & Ops page

Scope

• Ops queue (top): cards for stuck/failed coding sessions & workflows, instances with a dead runtime, agents in error, no-key users, recent error spikes — each linking to the offending user/instance.
• Errors feed: cross-user error_log with filters (source/level/since/user), newest-first, expandable stack/context.
• Trace viewer: query agent_events by trace_id/instance to reconstruct a run timeline (chat + apply + tool + error interleaved).
• MCP audit: table of MCP tool calls (user/tool/scope/allow-deny/time).

Acceptance criteria

• Ops cards compute live and link through.
• Errors feed filters + paginates; stack/context expandable.
• Trace viewer reconstructs a run by trace id.
• MCP audit is filterable.

Relevant code

• store/admin/ Errors/Ops page; consumes Errors/Events/Ops/MCP-audit API.

References

• FGS Ops + Errors + SessionView; FAS agent-errors.

Part of the PAGS Admin Portal epic. Depends on UI scaffold + Errors/Trace/Ops API.

[serge-ivo]

Closing as implemented on main. Evidence: store/admin/src/pages/Errors.tsx, Ops.tsx, TraceView.tsx, and McpAudit.tsx exist and consume the corresponding admin APIs. The remaining moderation UI is tracked separately by #41/#34.

[serge-ivo]

Implementation links: no associated PR was found; this landed direct on main in 9745b6a.