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.
I0802 · M003 · p1 · wave 0
Specify the session record before writing one
Define the session object in docs/SCHEMAS.md and docs/CONTINUITY.md: what a session is, how it differs from a task and from a handover, the filename grammar of a closed record, the exact field list, which fields are computed from git, and the rule that the reference envelope is derived rather than accumulated.
- Depends on
- none
- Blocked by
- none
- Unblocks
I0803- Serves
- none
- Scope
docs/SCHEMAS.mddocs/CONTINUITY.mddocs/CONCEPTS.md- Evidence
- 1 of 1
- Started
- not yet
- Verified
- not yet
- Completed
- 2026-09-04 15:46:06Z
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.