Skip to content

Read at

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.

I1121 · two-folder-integration · p1 · wave 6

Every surface shows the integration from the one model

blockedPull requests that name itClose

Project the integration state — what is adopted, what is owned, what is generated, what would change — through the CLI, the API and its document, MCP, the Cockpit and the documentation, from the one model and with no parallel definition.

Depends on
I1112
Blocked by
I1112
Unblocks
I1122
Serves
none
Scope
apps/majordomus-cli/src/capability/builtin
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.