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.
I2073 · a-session-leaves-what-it-observed · p1 · wave 0
A worker records an observation in one command
Register observation.recorded in share/events.yaml (emitted_by knowledge; requires task_id, kind, subject, statement, evidence) and add `knowledge observe --kind <friction|workaround|defect|drift|repetition> --subject <ref> [--evidence <ref>]... <statement>` to lib/knowledge.sh, writing one ledger line, refusing malformed input without writing, inside or outside a task, and only inside an open episode; write ADR 0118.
- Depends on
- none
- Blocked by
- none
- Unblocks
I2074- Scope
lib/knowledge.shshare/events.yamlshare/commands.yamldocs/CLI.mddocs/KNOWLEDGE.mddocs/SCHEMAS.mdand 5 more- Evidence
- 1 of 1
- Started
- 2026-10-14 08:01:27Z
- Verified
- not yet
- Completed
- 2026-10-14 08:01:33Z
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.