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.
I1407 · work-graph-github · p1 · wave 3
One issue travels the whole path and back, as an executable case
Prove the milestone with a case that carries one synthetic issue from outcome to accepted completion and then traverses the same chain backwards, offline, against fixtures.
- Blocked by
- none
- Unblocks
- none
- Serves
- none
- Scope
test/casesapps/majordomus-cli/tests.ai/repo/use-cases- Evidence
- 1 of 1
- Started
- 2026-09-09 22:00:42Z
- Verified
- 2026-09-09 22:00:54Z
- Completed
- 2026-09-09 22:00:58Z
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.