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.
I2483 · development-runtime · p1 · wave 2
The UI is published as a snapshot: read once at the published commit and carried by the site at /ui
Let a person who has not cloned the repository open majordomus ui on the public site: the UI's own answers for every screen and panel, and for the inspectors they link to up to a bound, written as static files at the commit the site publishes, every page saying it is a snapshot and none of them leading to nothing.
- Depends on
I2462- Blocked by
- none
- Unblocks
I2495- Serves
- none
- Scope
apps/majordomus-cli/src/web/report/snapshot.rsapps/majordomus-cli/src/web/report/mod.rsapps/majordomus-cli/src/commands/web.rsapps/majordomus-cli/src/cli.rsshare/ui/ui.js.github/workflows/pages.ymland 6 more- Evidence
- 4 of 4
- Started
- 2026-10-13 12:47:49Z
- Verified
- 2026-10-13 12:48:08Z
- Completed
- 2026-10-13 12:49:21Z
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.