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.
I2399 · development-runtime · p1 · wave 0
Every session briefs itself on an interval, without being asked
Give every worker of a supervised repository one short, typed brief of what surrounds it (its own episode and task, the peers of every board, the mesh, the integration queue and the derive queue), projected to the command line, HTTP, MCP and the Cockpit, and have a Claude Code provider mod the policy switches keep that brief in front of the session on its own: as the status line, injected on an interval, and with the session told at its start how to keep itself awake.
- Depends on
- none
- Blocked by
- none
- Unblocks
- none
- Serves
- none
- Scope
.ai/repo/project/issues/I2399.yaml.ai/repo/adrs/0136-every-session-briefs-itself-on-an-interval.mdapps/majordomus-cli/src/capability/builtin/brief.rsapps/majordomus-cli/src/capability/builtin/mod.rsapps/majordomus-cli/src/capability/builtin/peers.rsapps/majordomus-cli/src/commands/prs.rsand 26 more- Evidence
- 2 of 2
- Started
- 2026-10-14 07:59:26Z
- Verified
- not yet
- Completed
- 2026-10-14 07:59:34Z
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.