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.
I2004 · intent-bound-work · p1 · wave 1
plan start refuses an issue whose binding is refused, in both engines
Where the policy requires binding, have the start transition ask the binding of the issue before it stamps: plan::check in the Rust engine through the intent engine, and the shell engine through the built executable, with the same refusal text; where the policy does not require it, neither engine changes.
- Depends on
I2000- Blocked by
I2000milestone:intent-bound-work- Unblocks
- none
- Scope
apps/majordomus-cli/src/plan.rsapps/majordomus-cli/src/capability/builtin/plan.rslib/plan.shlib/intent_binding.shtest/cases/962_plan_start_asks_the_binding_in_both_engines.shtest/cases/133_plan_transition.sh- Evidence
- 0 of 1
- 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.