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.
I1902 · intent-planning · p1 · wave 2
The gap and the critique of an intent are typed records the plan is held to
Add the gap and critique kinds, their schemas, and intent_review::review, so intent validate refuses an incomplete gap and execution on an uncritiqued plan.
- Depends on
I1901- Blocked by
I1901milestone:intent-planning- Unblocks
- none
- Scope
apps/majordomus-cli/src/intent_review.rsshare/schemas/majordomus/gapshare/schemas/majordomus/critiqueshare/kinds.yaml.ai/repo/knowledge/sources.yamlshare/skeleton/ai/repo/knowledge/sources.yamland 1 more- Evidence
- 0 of 2
- Started
- not yet
- Verified
- not yet
- 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.