published Aug 30, 2026, 2:38 AM · updated Aug 30, 2026, 2:38 AM
Summary
Affected routes: /cao/dispatches/, /cao/workflows/, /cao/runs/, and /cao/coverage/. Severity: medium. Finding fingerprint: route-navigation-mislabels-and-omits-sections|routes:coverage,dispatches,runs,workflows.
Evidence
The deployed dashboard renders inconsistent and misleading navigation labels on multiple published routes, contradicting each route title and URL:
https://githubnext.github.io/central-agentic-ops/cao/workflows/<title>isWorkflows | central-agentic-ops.- Primary nav marks
Repositoriesas the current page (aria-current="page") instead ofWorkflows. - Report breadcrumb shows
Repositories > All workflowsrather than a workflows route label.
https://githubnext.github.io/central-agentic-ops/cao/runs/<title>isRuns | central-agentic-ops.- Primary nav marks
Overviewas the current page instead ofRuns.
https://githubnext.github.io/central-agentic-ops/cao/coverage/<title>isCoverage diagnostics | central-agentic-ops.- Primary nav marks
Overviewas the current page instead ofCoverage diagnostics.
https://githubnext.github.io/central-agentic-ops/cao/dispatches/<title>isDispatches | central-agentic-ops.- Primary nav contains only
Overview,Dispatches,Repositories, andPackages; there are no primary-nav entries forWorkflows,Runs, orCoverage, so operators cannot navigate directly to those published routes from this page.
This is reproducible in the published HTML itself and is not explained by coverage disclaimers. The pages and styles do load, but internal navigation is not intact because the dashboard advertises the wrong active route and omits reachable sections from the main navigation on several pages.
Trusted comparison context:
- deployment:
https://githubnext.github.io/central-agentic-ops/cao/ - expected inventory:
/tmp/gh-aw/agent/cao-dashboard-review/expected-inventory.json - Actions evidence:
https://github.com/githubnext/central-agentic-ops/actions/runs/33288114901
Viewport relevance: reproduced from the same published markup, so it affects both desktop and mobile presentations.
Impact
Operators using the dashboard to audit workflow and run coverage can be routed to the wrong section context or conclude that published routes do not exist from the dashboard navigation. That undermines routine audit tasks, especially when moving between overview, workflow inventory, run status, and coverage diagnostics.
Acceptance criteria
- The primary navigation includes direct entries for every published top-level CAO route: Overview, Dispatches, Packages, Repositories, Workflows, Runs, and Coverage diagnostics.
- Each route sets
aria-current="page"on its own navigation entry, not on a different section. - The workflows route identifies itself as a workflows page in its visible breadcrumb/report navigation rather than as a repositories page.
- The fix is visible on
/cao/dispatches/,/cao/workflows/,/cao/runs/, and/cao/coverage/in the published Pages deployment.
References
- https://githubnext.github.io/central-agentic-ops/cao/dispatches/
- https://githubnext.github.io/central-agentic-ops/cao/workflows/
- https://githubnext.github.io/central-agentic-ops/cao/runs/
Generated by CAO Dashboard Review · pi · gpt54 · 43.2 AIC · ⌖ 5.81 AIC · ⊞ 3.9K · ◷
- expires on Sep 13, 2026, 2:38 AM UTC