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.
I2461 · development-runtime · p1 · wave 0
majordomus ui is served at /ui as its own product, with screens composed from capabilities
Serve the UI, the primary human surface the owner names `majordomus ui`, as its own native surface on the shared server: its own mount, shell, delivery-vocabulary navigation and assets, with a first Dashboard composed only from capabilities, each value citing the capability and pointer it was read from.
- Depends on
- none
- Blocked by
- none
- Serves
- none
- Scope
apps/majordomus-cli/src/uiapps/majordomus-cli/src/generate.rsscripts/ci/cockpit-projection-check.ai/repo/ci/gates.yaml.ai/repo/features/ui.mdtest/cases/389_cockpit_projection.shand 15 more- Evidence
- 3 of 3
- Started
- 2026-10-12 10:58:53Z
- Verified
- 2026-10-12 10:59:05Z
- Completed
- 2026-10-12 10:59:30Z
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.