A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:01:48Z by majordomus 0.29.0. Nothing on this page is read again. See it live
PR Drain
Pull requests converging on master, one at a time.
Every open pull request as the integration lane assessed it: what it waits for, what would move it, what it depends on and overlaps, and the issue it carries.
- Issues ready86plan.status /counts/by_status/READY
- Issues active1plan.status /counts/by_status/ACTIVE
- Issues blocked159plan.status /counts/by_status/BLOCKED
- Issues done161plan.status /counts/by_status/DONE
Issue
One issue of the plan, as the plan records it.
I2482 · development-runtime · p1 · wave 4
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.
- Depends on
I2481- Blocked by
- none
- Unblocks
- none
- Serves
- none
- Scope
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.shand 1 more- Evidence
- 0 of 2
- Started
- not yet
- Verified
- not yet
- Completed
- not yet
plan.issues0 msAPI/api/v1/plan/issuesMCPmajordomus_plan_issuestechnical view
Pull-request drain
The integration lane asks the forge for every open pull request; this takes a while and arrives after the screen.