A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:01:48Z by majordomus 0.29.0. Nothing on this page is read again. See it live
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.
I1101 · two-folder-integration · p0 · wave 0
What this tool leaves behind, established by inspection rather than by memory
Establish, from the repository rather than from recollection, every path Majordomus writes, generates or mutates when a project adopts it — where each lands, which subsystem writes it, whether anything records it, and which are canonical, derived or accidental.
- Depends on
- none
- Blocked by
- none
- Serves
- none
- Scope
docs/TWO_FOLDER_CONSOLIDATION.md.ai/repo/adrs- Evidence
- 2 of 2
- Started
- 2026-10-16 11:25:07Z
- Verified
- 2026-10-16 12:15:38Z
- Completed
- not yet
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.