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.
I2300 · work-graph-github · p1 · wave 0
A head is judged against what it changes, not against GitHub's live state
Make scripts/ci/github-check report as pending, and not refuse, the drift an apply would write on the records a head changed since its merge base, and on the trunk on the records that changed in a landing younger than a declared window; refuse the same drift on every other record, and on the trunk past the window with the remedy named.
- Depends on
- none
- Blocked by
- none
- Unblocks
- none
- Serves
- none
- Scope
scripts/ci/github-check.ai/repo/ci/github.yaml.ai/repo/ci/README.md.ai/repo/rules/project/github-projection-gated.v1.md.ai/repo/automation/inventory.jsonltest/cases/1038_a_head_is_judged_against_what_it_changes.shand 5 more- Evidence
- 2 of 2
- Started
- 2026-10-14 08:02:34Z
- Verified
- not yet
- Completed
- 2026-10-14 08:02:42Z
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.