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.
I2741 · truthful-plan-surfaces · p0 · wave 1
Merged work the plan has not recorded is drift, and on the trunk past a window it is red
Add plan.drift over plan.delivery with the classes merged_not_recorded, active_without_work and done_without_trace (advisory), and a gate scripts/ci/plan-drift-check that refuses merged_not_recorded older than a window declared in .ai/repo/ci/plan.yaml on the trunk, naming majordomus plan verify|done <id>.
- Depends on
I2740- Blocked by
I2740- Unblocks
I2748- Serves
- none
- Scope
apps/majordomus-cli/src/capability/builtin/plan.rsapps/majordomus-cli/src/planapps/majordomus-cli/tests/plan_drift.rsscripts/ci/plan-drift-check.ai/repo/ci/plan.yaml.ai/repo/ci/README.mdand 4 more- Evidence
- 0 of 2
- Started
- not yet
- Verified
- not yet
- 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.