Dashboard: Incidents
Route: /incidents (DashboardIncidents.tsx, backed by dashboard.incidents())
Titled "Incidents & Exceptions" — "Circuit breakers and items requiring human attention." Currently thin: it renders exactly one category, Schedule Issues (raw JSON of whatever schedule_issues the backend returns — the same drift entries hoziron-cli competency check-schedules/GET /competencies/schedule-health report), or a "No active incidents" empty state when there are none.
Despite the page's stated scope ("circuit breakers and items requiring human attention"), there is no circuit-breaker feed here yet — that state lives on Observability › Gateway & Providers (reachable/auth_status per pool entry) instead, not surfaced as an incident here. ADR-062 describes this screen's incident rows deep-linking into the Audit Trail (?run_id=), which isn't wired up for schedule-issue rows specifically today.
Related:
- reference/api/competencies.md — the schedule-drift data this page renders
- observability.md — Gateway & Providers, where circuit-breaker/reachability state actually lives
- audit-trail.md — the deep-link target ADR-062 specifies for incident rows