A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:01:48Z by majordomus 0.29.0. Nothing on this page is read again. See it live
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.
I1508 · development-runtime · p1 · wave 0
The navigation is derived from the dispatcher, not kept beside it
Reconcile the Cockpit's area list against the routes the dispatcher actually answers, and derive or check the route table in docs/COCKPIT.md, so that a routed page cannot be invisible.
- Depends on
- none
- Blocked by
- none
- Unblocks
- none
- Serves
- none
- Scope
apps/majordomus-cli/src/cockpitdocs/COCKPIT.mdtest/cases- Evidence
- 2 of 2
- Started
- 2026-10-14 07:58:39Z
- Verified
- not yet
- Completed
- 2026-10-14 07:58:48Z
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.