A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:06:01Z by majordomus 0.29.0. Nothing on this page is read again. See it live
I2482
Every screen of the UI has a case, and no link on the UI is dead
Where it stands
devtask.issue- Readiness
- ready no dependency and no gate holds it; nobody has started it
- Status
- READY
- Can start
- startable
- Milestone
- Milestone status
- ACTIVE
- Wave
4- Waiting on
- none
- Holds back
- none
- Behind it in all
0- Evidence
0of2
Moves
plan.transitionWhat it is
- 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.
- Now
- 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.
- Wanted
- 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.
- Done when
- unknown: the record declares no `completion`
- Risk
- unknown: the record declares no `risk`
Acceptance
- 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::governancecargo test --test ui_linkstest/run.sh 1088_the_command_and_capability_screens_answer- Evidence required
ui_screen_cases_1088_1091ui_links_integration_test- Evidence present
- unknown: the record carries no `evidence` entries
Scope
- Touches
apps/majordomus-cli/src/ui/governance.rsapps/majordomus-cli/tests/ui_links.rstest/cases/1088_the_command_and_capability_screens_answer.shtest/cases/1089_the_work_and_mesh_screens_answer.shtest/cases/1090_the_deployments_and_docs_screens_answer.shtest/cases/1091_no_link_on_the_ui_is_dead.sh.ai/repo/project/issues/I2482.yaml- Not
- unknown: the record declares no `non_scope`
- Depends on
- Priority
- p1
- Profile
- implementation
- Parallel safe
- false
- Owner
- unknown: the record declares no `owner`
The work so far
- Branches
- none
- Merged
- none
- Commits
0- Trunk
- master
- Sessions
- none
- Created
- 2026-10-12
- Updated
- 2026-10-12
- Started
- unknown: the record declares no `started_at`
- Verified
- unknown: the record declares no `verified_at`
- Completed
- unknown: the record declares no `completed_at`
Synchronisation
- Adapter
scripts/github-sync- Repository
- unknown: the derived plan's header carries no repository
- External issue
- unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
- State there
- unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
Findings
Nothing is wrong with these records.