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.
I2301 · development-runtime · p1 · wave 0
Whether the work is done is answered by measurement: the done invariant asks about debt, what was left behind and the backlog
Add to the done invariant the three questions a person asks when a session ends that it does not yet ask — did the recorded debt grow, is a branch or worktree created since the task started still there, is a pull request opened since still open — each read from the record that holds the fact, and state as a project rule that a closing question is answered by that reading and never by a worker's recollection.
- Depends on
- none
- Blocked by
- none
- Unblocks
- none
- Serves
- none
- Scope
apps/majordomus-cli/src/gates/closing.rsapps/majordomus-cli/src/gates/done.rsapps/majordomus-cli/src/gates/mod.rsapps/majordomus-cli/src/capability/builtin/gates.rs.ai/repo/rules/project.ai/repo/workflows/task-lifecycle.mdand 6 more- Evidence
- 2 of 2
- Started
- 2026-10-10 21:36:49Z
- Verified
- 2026-10-10 21:36:58Z
- Completed
- 2026-10-10 21:56:14Z
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.