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.
I2491 · adopter-upgrades · p1 · wave 0
A personal layer changes nothing shared: init --personal and install.sh --personal keep the layer one person's own, verify it, and --shared hands it to the team
Let one person use the tool on real work in a repository other people share without changing anything shared: one flag on init and on the installer, every later writer covered by the same mechanism, the result verified at install and on every doctor, the executable reading an untracked layer without being told to, and one command that hands the layer to the team.
- Depends on
- none
- Blocked by
- none
- Unblocks
- none
- Serves
- none
- Scope
lib/common.shlib/init.shlib/update.shlib/capture.shlib/doctor.shshare/install/install.sh.inand 14 more- Evidence
- 2 of 2
- Started
- 2026-10-14 07:39:44Z
- Verified
- not yet
- Completed
- 2026-10-14 07:39:55Z
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.