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.
I2744 · truthful-plan-surfaces · p0 · wave 1
The UI roadmap reads delivery and the releases themselves, and its now is where work is
Make /ui/roadmap (apps/majordomus-cli/src/ui/roadmap.rs) show each issue's inferred stage from plan.delivery beside its declared status, derive Now as the milestones with work in flight (open pull requests, mesh claims, ACTIVE) and Next from the graph, and read the latest release from the releases (tags and the published latest.json) at the moment it renders, so a snapshot never shows an older release than the executable that drew it.
- Depends on
I2740- Blocked by
I2740- Unblocks
- none
- Serves
- none
- Scope
apps/majordomus-cli/src/ui/roadmap.rsapps/majordomus-cli/src/ui/dashboard.rsapps/majordomus-cli/src/ui/chrome.rsapps/majordomus-cli/tests/ui_roadmap.rstest/cases/3104_the_ui_roadmap_reads_delivery.sh- Evidence
- 0 of 1
- Started
- not yet
- Verified
- not yet
- 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.