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.
I0808 · M003 · p1 · wave 2
Extract nodes with identities that survive a rebuild
Implement the extract and normalise stages in lib/knowledge.awk: one node per canonical object, with an identity derived from its canonical id or its repository path, a kind that is only asserted when a structural fact establishes it, and a title taken from the record or from the document's first heading.
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.