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.
I1949 · test-evidence · p1 · wave 0
CI evidence is recorded clean, and its report is the tracked ledger's verdict
Fix PR #577 on its own branch so that the CI evidence job derives its report from the tracked ledger before it records the run's executions, every job that runs tests measures its tree where it ran, and the site publishes current only under ADR 0087's interim rule (decision 1).
- Depends on
- none
- Blocked by
- none
- Unblocks
I1951- Serves
- none
- Scope
.github/workflows/validate.ymlscripts/ci/evidence-collectscripts/pagessite/templates/evidence.htmldocs/EVIDENCE.mddocs/CLAIMS.yamland 2 more- Evidence
- 2 of 2
- Started
- 2026-10-14 07:59:48Z
- Verified
- not yet
- Completed
- 2026-10-14 07:59:56Z
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.