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.
I1600 · public-proof · p1 · wave 0
The challenge is one recorded run, and every public surface replays it
Record one scenario in which a worker strays outside its scope, claims it is done, hands over, and is refused until the repository's own test passes; render that run on the homepage and on /challenge/; make README.md's first transcript a step of it; and verify the public site serves it after publication.
- Depends on
- none
- Blocked by
- none
- Unblocks
- none
- Serves
- none
- Scope
lib/usecase.shlib/finish.shshare/schemas/majordomus/use-case.ai/repo/use-casestestscriptsand 7 more- Evidence
- 3 of 3
- Started
- 2026-10-11 04:18:57Z
- Verified
- 2026-10-11 04:40:44Z
- Completed
- 2026-10-11 04:40:59Z
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.