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.
I2161 · architecture-is-enforced · p1 · wave 0
No answer, log line or mesh frame carries a credential the redactor knows
Pass every response reason, logged request field and replicated mesh text through the one redactor, bound the fields a mesh event may carry, and make the redaction module's documentation name the callers that exist.
- Depends on
- none
- Blocked by
- none
- Unblocks
I2708- Serves
- none
- Scope
apps/majordomus-cli/src/http/router.rsapps/majordomus-cli/src/http/server.rsapps/majordomus-cli/src/logging.rsapps/majordomus-cli/src/redaction.rsapps/majordomus-cli/src/mesh/handover.rsapps/majordomus-cli/src/mesh/journal.rsand 3 more- Evidence
- 1 of 1
- Started
- 2026-10-14 12:16:03Z
- Verified
- not yet
- Completed
- 2026-10-14 12:16:43Z
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.