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.
I2002 · intent-bound-work · p1 · wave 2
The context of a bound task says what the intent asks of this work
Add an INTENT section to majordomus context for a task that named an issue or an intent: statement, invariants, the criteria served with the state of their evidence, the critique's open blocking findings and the gap's conditions, each read from intents.binding and bounded by the context budget.
- Depends on
I2001- Blocked by
I2001milestone:intent-bound-work- Unblocks
- none
- Scope
lib/context.shlib/intent_binding.shtest/cases/960_a_task_starts_bound_to_what_it_serves.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.