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.
I2470 · development-runtime · p1 · wave 2
The pull requests drain in the UI: a queue a reader narrows, inspects and follows to what each depends on
Give majordomus ui a PR Drain screen (/ui/prs) that shows every open pull request as the integration lane assessed it, lets the reader narrow it by disposition, lane and text, inspect one pull request and the plan issue it names, and follow each dependency and overlap to the pull request it leads to; every control is a link or a GET form, so every view has an address and the screen is complete without JavaScript.
- Depends on
I2462- Blocked by
- none
- Serves
- none
- Scope
apps/majordomus-cli/src/ui/prs.rsapps/majordomus-cli/src/ui/mod.rsapps/majordomus-cli/src/ui/dashboard.rs.ai/repo/project/issues/I2470.yamldocs/MAJORDOMUS_UI.mdtest/cases/1075_the_pull_requests_drain_in_the_ui.sh- Evidence
- 2 of 2
- Started
- 2026-10-12 11:00:46Z
- Verified
- 2026-10-12 11:00:51Z
- Completed
- 2026-10-12 11:00:58Z
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.