internal/gateway/dashboard_tools.go holds 33 path, label and description triples for page_index and dashboard_navigate, hand-maintained beside the real routes in ui/src/router/index.ts and the nav in ui/src/lib/nav.ts.
Seven destinations the dashboard offers are missing from it, so the assistant cannot point an operator at schedules, issue routing, usage, alerts, extensions, organisations or the channels settings page, and dashboard_navigate refuses those paths. Channels carries a different description in each place.
Done when: one catalogue feeds the router's labels and page_index both, every destination the dashboard offers can be named by the assistant, and a new route cannot land without a catalogue entry.
internal/gateway/dashboard_tools.go holds 33 path, label and description triples for `page_index` and `dashboard_navigate`, hand-maintained beside the real routes in ui/src/router/index.ts and the nav in ui/src/lib/nav.ts.
Seven destinations the dashboard offers are missing from it, so the assistant cannot point an operator at schedules, issue routing, usage, alerts, extensions, organisations or the channels settings page, and `dashboard_navigate` refuses those paths. Channels carries a different description in each place.
Done when: one catalogue feeds the router's labels and `page_index` both, every destination the dashboard offers can be named by the assistant, and a new route cannot land without a catalogue entry.
The dashboard was consolidated into one SPA while this was being worked, so the catalogue now derives from ui/src/router/routes.ts rather than either of the two previous apps.
Fix (32fbf8b69): the route table moved to routes.ts with no component imports, and ui/scripts/pages.ts writes ui/pages/pages.json from it: 46 pages, every one with a description, including the eight that were missing (runs, controls, schedules, issue routing, usage, alert webhook, and the instance channels and extensions pages). page_index and dashboard_navigate read that file.
Staleness, not duplication, is what remains: task pages:check runs in the gate and fails when the committed catalogue is behind the router. Verified by renaming a route's label and watching the check reject the diff. task check green.
The dashboard was consolidated into one SPA while this was being worked, so the catalogue now derives from `ui/src/router/routes.ts` rather than either of the two previous apps.
Fix (32fbf8b69): the route table moved to `routes.ts` with no component imports, and `ui/scripts/pages.ts` writes `ui/pages/pages.json` from it: 46 pages, every one with a description, including the eight that were missing (runs, controls, schedules, issue routing, usage, alert webhook, and the instance channels and extensions pages). `page_index` and `dashboard_navigate` read that file.
Staleness, not duplication, is what remains: `task pages:check` runs in the gate and fails when the committed catalogue is behind the router. Verified by renaming a route's label and watching the check reject the diff. task check green.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
internal/gateway/dashboard_tools.go holds 33 path, label and description triples for
page_indexanddashboard_navigate, hand-maintained beside the real routes in ui/src/router/index.ts and the nav in ui/src/lib/nav.ts.Seven destinations the dashboard offers are missing from it, so the assistant cannot point an operator at schedules, issue routing, usage, alerts, extensions, organisations or the channels settings page, and
dashboard_navigaterefuses those paths. Channels carries a different description in each place.Done when: one catalogue feeds the router's labels and
page_indexboth, every destination the dashboard offers can be named by the assistant, and a new route cannot land without a catalogue entry.The dashboard was consolidated into one SPA while this was being worked, so the catalogue now derives from
ui/src/router/routes.tsrather than either of the two previous apps.Fix (
32fbf8b69): the route table moved toroutes.tswith no component imports, andui/scripts/pages.tswritesui/pages/pages.jsonfrom it: 46 pages, every one with a description, including the eight that were missing (runs, controls, schedules, issue routing, usage, alert webhook, and the instance channels and extensions pages).page_indexanddashboard_navigateread that file.Staleness, not duplication, is what remains:
task pages:checkruns in the gate and fails when the committed catalogue is behind the router. Verified by renaming a route's label and watching the check reject the diff. task check green.