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.
I2416 · test-evidence · p1 · wave 0
The ci verdict asks every selected gate for a receipt, and a gate whose step never ran is red
Make scripts/ci/verdict green only when every gate the plan selected left a receipt from the step that ran it, every receipt `success`: a job's success is not a gate's, because a job carries many gates and a step its condition skipped does not fail the job. Cancelled, skipped, missing and absent never pass, and each has a fixture.
- Depends on
- none
- Blocked by
- none
- Unblocks
- none
- Serves
- none
- Scope
scripts/ci/verdictscripts/ci/timedscripts/ci/run-plan.github/workflows/validate.ymltest/cases/94_ci_plan.shtest/cases/26_ci_wiring.sh- Evidence
- 1 of 1
- Started
- 2026-10-14 08:00:49Z
- Verified
- not yet
- Completed
- 2026-10-14 08:00:55Z
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.