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.
I2486 · development-runtime · p0 · wave 1
No screen waits for a source: a page shows the latest reading with its age, read again behind the reader
Take every handler, git call and file read off the path of a UI request: the executor keeps the latest reading of each source a page asked for, a screen is rendered from those readings at once, and a worker reads a source again behind the reader whenever the reading is not of the repository as it is now.
- Depends on
I2461- Blocked by
- none
- Serves
- none
- Scope
apps/majordomus-cli/src/capability/readings.rsapps/majordomus-cli/src/capability/executor.rsapps/majordomus-cli/src/capability/handler.rsapps/majordomus-cli/src/capability/mod.rsapps/majordomus-cli/src/uiapps/majordomus-cli/src/http/router.rsand 8 more- Evidence
- 4 of 4
- Started
- 2026-10-13 12:45:05Z
- Verified
- 2026-10-13 12:45:29Z
- Completed
- 2026-10-13 12:47:30Z
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.