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.
I2074 · a-session-leaves-what-it-observed · p1 · wave 1
An observation becomes a candidate that says what it is about, and reading groups recurrence
Add the observation.recorded row to mj_knowledge_evidence with ADR 0091's per-episode id over kind, subject and statement; add optional about and route to knowledge/v1 (proto, generate); have knowledge candidates and the Rust knowledge_base.candidates group by about, listing each record and its episodes.
- Depends on
I2073- Blocked by
- none
- Unblocks
I2075- Serves
a-session-leaves-what-it-observed#an-observation-becomes-a-candidatea-session-leaves-what-it-observed#recurrence-is-grouped- Scope
lib/knowledge.shshare/schemas/majordomus/knowledgeshare/allowshare/sections.ai/repo/knowledge/candidates/README.mdshare/skeleton/ai/repo/knowledgeand 4 more- Evidence
- 1 of 1
- Started
- 2026-10-14 23:32:49Z
- Verified
- 2026-10-14 23:32:56Z
- Completed
- 2026-10-14 23:33: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.