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.
I2156 · failure-is-visible · p1 · wave 0
A slow or silent HTTP client cannot hold a server worker
Put a declared deadline on reading each request's head and body, close and count a connection that misses it, and keep handler time off the workers the probe needs.
- Depends on
- none
- Blocked by
- none
- Unblocks
- none
- Serves
- none
- Scope
apps/majordomus-cli/src/http/server.rsapps/majordomus-cli/src/lease.rsapps/majordomus-cli/src/policy.rs.ai/repo/policy.yamlshare/schemas/majordomus/policyapps/majordomus-cli/tests/http_serve.rsand 1 more- Evidence
- 1 of 1
- Started
- 2026-10-14 08:01:59Z
- Verified
- not yet
- Completed
- 2026-10-14 08:02:05Z
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.