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.
I2068 · M004 · p2 · wave 0
A verdict that depends on the runner says so, and one cold sample is not a regression
Make the timing verdicts this repository's CI and its adopters' hooks hand down distinguish a slower change from a slower machine: a benchmark regression is judged from more than one cold sample and against the load it was measured under, and a case whose cost sits within a few percent of its kill bound is reported as a budget risk before it fails a suite whose every case passed.
- Depends on
- none
- Blocked by
- none
- Unblocks
- none
- Serves
- none
- Scope
test/cases/82_bench_check.shtest/cases/95_executable_reference.shtest/cases/417_the_suite_finishes_inside_its_bound.shscripts/ci/suite-budgetapps/majordomus-cli/src/bench- Evidence
- 2 of 2
- Started
- 2026-10-16 07:54:07Z
- Verified
- 2026-10-16 07:54:13Z
- 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.