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.
I0816 · M003 · p1 · wave 8
Prove the loop on a real issue, without a transcript
Execute the whole lifecycle against a real issue of this repository — session start, plan next, plan show, context, knowledge retrieval, work, checkpoint and decision, evidence, plan done, session close, knowledge sync, watch — and record as evidence what a following session could determine from the records alone.
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.