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.
I2147 · mcp-transports-are-reliable · p2 · wave 0
The MCP transports bound what they read and follow the Streamable HTTP rules they claim
Apply one declared message bound to stdin lines, request bodies and every response the bridge reads, validate MCP-Protocol-Version, issue unpredictable session ids, and never reap a session whose request is still running.
- Depends on
- none
- Blocked by
- none
- Unblocks
- none
- Serves
- none
- Scope
apps/majordomus-cli/src/mcp/stdio.rsapps/majordomus-cli/src/mcp/bridge.rsapps/majordomus-cli/src/http/mcp.rsapps/majordomus-cli/src/http/server.rsapps/majordomus-cli/tests/mcp_conformance.rsapps/majordomus-cli/tests/mcp_conformance_http.rsand 1 more- Evidence
- 3 of 3
- Started
- 2026-10-14 23:26:13Z
- Verified
- 2026-10-14 23:26:24Z
- Completed
- 2026-10-14 23:26:47Z
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.