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.
I2475 · development-runtime · p1 · wave 4
The issues are browsed: every issue of the plan by status, milestone, priority or text, each a link onward
Give majordomus ui an Issues screen (/ui/issues) that lists every issue of the plan, narrowed by the plan's own statuses as tabs and by milestone, priority and text in a GET form, each issue leading to its inspector, its milestone to the milestone's and what blocks it to that issue's.
- Blocked by
- none
- Unblocks
- none
- Serves
- none
- Scope
apps/majordomus-cli/src/ui/issues.rsapps/majordomus-cli/src/ui/mod.rs.ai/repo/project/issues/I2475.yamldocs/MAJORDOMUS_UI.mdtest/cases/1080_the_issues_are_browsed.sh- Evidence
- 2 of 2
- Started
- 2026-10-12 11:04:21Z
- Verified
- 2026-10-12 11:04:28Z
- Completed
- 2026-10-12 11:04:42Z
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.