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.
I2054 · development-runtime · p1 · wave 0
A tag does not turn every other pull request red until its record lands
From the moment a release tag is pushed until its release record is on master, a pull request that changes nothing about releases keeps a green structure job. Either scripts/ci/release-check holds a published tag without a record only when no open pull request proposes that record, or the record is proposed before the tag is pushed; the choice is the implementer's and is written down with what it costs.
- Depends on
- none
- Blocked by
- none
- Unblocks
I2712- Serves
- none
- Scope
scripts/ci/release-check.github/workflows.ai/repo/ciapps/majordomus-cli/src/releasetest/casesdocs- Evidence
- 1 of 1
- Started
- 2026-10-14 14:52:51Z
- Verified
- not yet
- Completed
- 2026-10-14 14:53:16Z
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.