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.
I2474 · development-runtime · p1 · wave 4
The drain draws its merge throughput: each day's merges over the fortnight its trail ends on
Draw on the PR Drain how many pull requests the executor merged on each of the fourteen days that end on the day of its trail's newest event, as a chart whose counts are written in its label and in a table beside it.
- Depends on
I2473- Blocked by
- none
- Unblocks
- none
- Serves
- none
- Scope
apps/majordomus-cli/src/ui/prs.rs.ai/repo/project/issues/I2474.yamldocs/MAJORDOMUS_UI.mdtest/cases/1079_the_drain_draws_its_throughput.sh- Evidence
- 2 of 2
- Started
- 2026-10-12 11:03:47Z
- Verified
- 2026-10-12 11:03:54Z
- Completed
- 2026-10-12 11:04:08Z
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.