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.
I2001 · intent-bound-work · p1 · wave 1
start asks what the task serves and refuses a refused binding where the policy requires it
Give start the flags --issue, --intent, --exempt and --because; ask intents.binding through the built executable; under policy intent.binding: required refuse a refused or unreadable binding, under advisory report it, and when the key is absent change nothing. Record what was named and the revision in the task record and the task.started ledger event.
- Depends on
I2000- Blocked by
I2000milestone:intent-bound-work- Scope
lib/start.shlib/intent_binding.sh.ai/repo/policy.yamlapps/majordomus-cli/src/capability/builtin/continuity.rstest/cases/960_a_task_starts_bound_to_what_it_serves.shdocsand 8 more- Evidence
- 0 of 4
- 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.