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.
I2481 · development-runtime · p1 · wave 3
The UI links every entity it names, and says none where a source has no value
Make every entity a screen of majordomus ui names lead somewhere: to the UI's own screen or inspector for it, to its technical view when the UI has no screen for it, or to the address its source gives when it lives elsewhere; say none where a source has no value; say how much a cut list leaves out; and count throughput over the window the queue states rather than one the screen chooses.
- Depends on
I2478- Blocked by
- none
- Unblocks
I2482- Serves
- none
- Scope
apps/majordomus-cli/src/ui/view.rsapps/majordomus-cli/src/ui/source.rsapps/majordomus-cli/src/ui/dashboard.rsapps/majordomus-cli/src/ui/delivery.rsapps/majordomus-cli/src/ui/deployments.rsapps/majordomus-cli/src/ui/command.rsand 11 more- Evidence
- 1 of 1
- Started
- 2026-10-14 07:59:38Z
- Verified
- not yet
- Completed
- 2026-10-14 07:59:44Z
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.