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.
I1947 · test-evidence · p1 · wave 0
Every feature reaches a test, and every use case has a feature
Give every active use case an owning feature, and give the cockpit and deployments features a claim naming their own tests, so that a homepage panel routed to a use case reaches a feature and every feature reaches a test through the subject index (ADR 0087 decision 9).
- Depends on
- none
- Blocked by
- none
- Unblocks
I1952- Serves
- none
- Scope
.ai/repo/features/finish-contract.md.ai/repo/features/commit.md.ai/repo/features/install.md.ai/repo/features/continuity.md.ai/repo/features/cockpit.md.ai/repo/features/deployments.mdand 5 more- Evidence
- 2 of 2
- Started
- 2026-10-08 10:49:57Z
- Verified
- 2026-10-08 10:50:33Z
- Completed
- 2026-10-08 10:50:38Z
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.