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.
I2462 · development-runtime · p1 · wave 1
The UI has every screen, and its mesh is a graph whose nodes open an inspector
Complete the navigation of majordomus ui against the owner's references with the Command, Capabilities, Deployments and Documentation screens. Make the Mesh screen interactive: a graph of machines, runtimes and sessions, each node selectable into an inspector whose selection is a URL.
- Depends on
I2461- Blocked by
- none
- Serves
- none
- Scope
apps/majordomus-cli/src/uishare/ui.ai/repo/project/issues/I2462.yamldocs/MAJORDOMUS_UI.md.ai/repo/features/ui.md- Evidence
- 2 of 2
- Started
- 2026-10-12 11:00:05Z
- Verified
- 2026-10-12 11:00:10Z
- Completed
- 2026-10-12 11:00:20Z
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.