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.
I1001 · capability-graph · p0 · wave 0
One typed graph composes the registries that already own their facts
Extend the executable's graph derivation into a typed, deterministic model that composes the existing authoritative registries — capabilities, commands, routes, MCP exposure, skills, rules, decisions, documents, use cases, benchmarks — without any of them ceasing to be authoritative.
- Depends on
- none
- Blocked by
- none
- Serves
- none
- Scope
apps/majordomus-cli/src/graph.rs- Evidence
- 2 of 2
- Started
- 2026-09-06 15:33:09Z
- Verified
- not yet
- Completed
- 2026-09-06 15:48:16Z
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.