I2482 — Every screen of the UI has a case, and no link on the UI is dead
Prove every screen of majordomus ui through a real server, and prove that every link the UI draws inside the server answers.
DONE wave 4 · p1 · implementation profile · runs alone
Part of development-runtime — The runtime has a development surface.
Objective
Prove every screen of majordomus ui through a real server, and prove that every link the UI draws inside the server answers.
Why
The owner asked on 2026-10-12 that majordomus ui be tested and verified. The audit of the merged UI found six screens no case or integration test reaches (Command, Issues & PRs, Capabilities, Mesh, Deployments with its delivery panel, Documentation), a Governance screen with no unit test, and nothing that checks a link the UI draws leads anywhere.
Current state
Cases 1075-1083 prove the drain, the roadmap, CI timings, the trail, throughput, issues, intents, claims and rules; tests/ui_surface.rs proves the Dashboard and the queue panel. The other screens and every link are unproven.
Desired state
Cases 1088-1091 serve a fixture and read the Command, Issues & PRs, Capabilities (with an inspected capability), Mesh (with a node), Deployments (with the delivery panel) and Documentation screens, each saying what it must show; governance.rs has unit tests; tests/ui_links.rs serves a fixture, reads every screen of the navigation and every link under /ui and /cockpit/object it draws, and fails on any that does not answer 200.
Scope
- apps/majordomus-cli/src/ui/governance.rs
- apps/majordomus-cli/tests/ui_links.rs
- test/cases/1088_the_command_and_capability_screens_answer.sh
- test/cases/1089_the_work_and_mesh_screens_answer.sh
- test/cases/1090_the_deployments_and_docs_screens_answer.sh
- test/cases/1091_no_link_on_the_ui_is_dead.sh
- .ai/repo/project/issues/I2482.yaml
Dependencies
Acceptance criteria
- every screen of the navigation is read by a case through a real server
- governance.rs has unit tests
- every link under /ui and /cockpit/object the screens draw answers 200, and a test fails when one does not
Validation
- cargo test --lib ui::governance
- cargo test --test ui_links
- test/run.sh 1088_the_command_and_capability_screens_answer
Evidence required
- ui_screen_cases_1088_1091
- ui_links_integration_test
Evidence
| covers | type | command | result | at commit |
|---|---|---|---|---|
| ui_screen_cases_1088_1091 | test | MJ_TEST_JOBS=4 bash test/run.sh 1088_the_command_and_capability_screens_answer 1089_the_work_and_mesh_screens_answer 1090_the_deployments_and_docs_screens_answer 1091_no_link_on_the_ui_is_dead | ok 1088 2s, ok 1089 2s, ok 1090 2s, ok 1091 8s (run of 11: 11 passed, 0 failed, 0 skipped) at 09c334079f5 with the executable of #1304; and cargo test --lib ui::governance: test result: ok. 2 passed; 0 failed | 09c3340 |
| ui_links_integration_test | test | cargo test --manifest-path apps/majordomus-cli/Cargo.toml --test ui_links | test result: ok. 2 passed; 0 failed (every_link_the_ui_draws_inside_the_server_answers, the_crawl_reads_hrefs_and_follows_only_the_servers_own_pages) at 09c334079f5; delivered by 995496f6ffa | 09c3340 |
Timeline
- started
- 2026-10-16T16:43:24Z
- verified
- 2026-10-16T16:43:29Z
- completed
- 2026-10-16T16:43:38Z
Those three fields, the evidence above and the state of the dependencies are all the status is made of. There is no status field to disagree with them.
Canonical record: .ai/repo/project/issues/I2482.yaml. Read it back with majordomus plan show I2482.