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.
I2780 · idd-workspace · p0 · wave 0
The UI has an intent workspace: an intent, its milestones, issues, waves and graph on one screen
Add /ui/idd to the UI's screens: the intents as a choice with stage and verdict, the chosen one's criteria, its milestones in the roadmap's order with status, its issues with status, wave, priority and what blocks them, the waves those issues occupy, and the dependency graph between them with a table beneath it, every entity a link to its existing inspector and every ready issue a link to the move that starts it.
- Depends on
- none
- Blocked by
- none
- Unblocks
- none
- Scope
apps/majordomus-cli/src/uiapps/majordomus-cli/tests/ui_idd.rsdocs/MAJORDOMUS_UI.md.ai/repo/project- Evidence
- 1 of 1
- Started
- 2026-10-16 21:12:37Z
- Verified
- 2026-10-16 21:13:23Z
- Completed
- not yet
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.