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.
I1004 · capability-graph · p0 · wave 1
Availability and visibility are metadata, not conditions in a template
Model where a capability is available — always, only in a static build, only with a running backend, only when authenticated, only at build time — and whether it is public or internal, so that every surface derives its behaviour from that rather than from its own conditionals.
- Depends on
I1001- Blocked by
- none
- Serves
- none
- Scope
apps/majordomus-cli/src/capability/model.rs- Evidence
- 2 of 2
- Started
- 2026-09-06 16:22:51Z
- Verified
- not yet
- Completed
- 2026-09-06 16:54:53Z
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.