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.
I2471 · development-runtime · p1 · wave 3
The roadmap opens a milestone: what it holds, what can start, its critical path, and what it waits for
Let a reader of majordomus ui open any milestone of the plan (/ui/roadmap?milestone=M004) into an inspector that shows its issues and where each stands, the issues that can start now, the longest chain of open work through it, the intents its issues serve, and the milestones it waits for, is blocked by and unblocks, every one of them a link.
- Depends on
I2470- Blocked by
- none
- Serves
- none
- Scope
apps/majordomus-cli/src/ui/milestone.rsapps/majordomus-cli/src/ui/roadmap.rsapps/majordomus-cli/src/ui/dashboard.rsapps/majordomus-cli/src/ui/mod.rs.ai/repo/project/issues/I2471.yamldocs/MAJORDOMUS_UI.mdand 1 more- Evidence
- 2 of 2
- Started
- 2026-10-12 11:01:59Z
- Verified
- 2026-10-12 11:02:03Z
- Completed
- 2026-10-12 11:02:16Z
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.