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.
I1118 · two-folder-integration · p0 · wave 7
Every invariant of this milestone is a rule with a check that runs
Turn the invariants — bounded footprint, no manual registration, disposable derived artifacts, reversible managed mutations, idempotent reconciliation, root files as adapters, zero-registration extension — into project rules, each with an executable check that CI runs and a negative test that proves it fires.
- Unblocks
I1123- Serves
- none
- Scope
.ai/repo/rules/project- Evidence
- 0 of 3
- Started
- not yet
- Verified
- not yet
- Completed
- not yet
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.