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.
I0809 · M003 · p1 · wave 3
Record only edges that a file states, each with where it was observed
Implement the resolve and graph stages: edges derived from the explicit relationships the canonical files already declare — claim to source, implementation and test; issue to milestone and to its dependencies; evidence to issue; doctrine to validator, claim and test; record to task — each carrying the file and field it was observed in, and none carrying a relationship inferred from prose.
- Depends on
I0808- Blocked by
- none
- Serves
- none
- Scope
lib/knowledge.shlib/knowledge.awktest/cases/74_knowledge_edges.shtest/cases/75_knowledge_mutation.sh- Evidence
- 2 of 2
- Started
- 2026-09-04 18:14:13Z
- Verified
- not yet
- Completed
- 2026-09-04 18:31:05Z
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.