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.
I1301 · external-workspaces · p0 · wave 0
A workspace is a declared object of the layer; only its content is local
Register `workspace` as a kind — allowed keys, schema, directory contract — and declare the first workspace under .ai/repo/workspaces/, so that the catalogue of what may be synced is the repository's own tracked statement while the synced content stays out of the tracked tree.
- Depends on
- none
- Blocked by
- none
- Unblocks
I1302- Serves
- none
- Scope
.ai/repo/workspacesshare/kinds.yamlshare/allow/workspace.txtshare/schemas- Evidence
- 4 of 4
- Started
- 2026-09-09 18:25:15Z
- Verified
- 2026-09-09 18:26:21Z
- Completed
- 2026-09-09 18:26:36Z
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.