feat(ui): Codex/defenseclaw monitor spans

[namrataghadi-galileo]

Summary

• Added a dedicated Events tab to agent details so recent control executions no longer clutter the aggregate Monitor view.
• Improved event details and content-disclosure labels while preserving evaluator-neutral behavior.

Scope

• User-facing/API changes:
  • Added a routable Events tab beside Controls and Monitor.
  • Displays evaluator, result, action, trace/span/request IDs, rule IDs, stage, and duration.
  • Displays blocked input, enforcement reason, and raw request body when provided.
  • Uses Full content, Redacted content, and Metadata only labels only when disclosure metadata is explicitly present.
  • No API contract changes.
• Internal changes:
  • Moved event querying and polling out of the Monitor component.
  • Updated tab routing and direct-link handling.
  • Updated Playwright coverage for routing, event states, and built-in evaluators.
• Out of scope:
  • Changes to event ingestion or storage contracts.
  • Adding a typed, universal content-disclosure field.
  • Changing evaluator execution or enforcement behavior.

Risk and Rollout

• Risk level: low
• Rollback plan:
  • Revert the Events-tab UI changes to restore Recent executions inside Monitor.
  • No data migration or API rollback is required.

Testing

• Added or updated automated tests
• Ran make check (not run; the changes are UI-only)
• Manually verified behavior
  • TypeScript, ESLint, Prettier, and git diff --check passed.
  • All 52 focused Playwright tests passed.

Checklist

• Linked issue/spec (if applicable)
• Updated docs/examples for user-facing changes
• Included any required follow-up tasks
  • Consider adding a typed content-disclosure field to the event contract if all event producers need consistent privacy labeling.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!