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.
I0830 · M004 · p0 · wave 5
docs/PERFORMANCE.md, README, CONTRIBUTING and CLI reference
Write the reference: goals, phases and counters, batch reads, the flatten cache, cold versus warm, result and baseline schemas, the policy block, the regression workflow, the contributor workflow and the limitations; add the README section and the bench section of docs/CLI.md.
- Blocked by
- none
- Unblocks
I0843- Serves
- none
- Scope
docs/PERFORMANCE.mdREADME.mdCONTRIBUTING.mddocs/CLI.mddocs/README.mdsite/data/generated- Evidence
- 1 of 1
- Started
- 2026-09-05 03:47:33Z
- Verified
- 2026-09-05 03:47:33Z
- Completed
- 2026-09-05 03:47:33Z
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.