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.
I0823 · M004 · p0 · wave 1
majordomus bench: targets derived from the command registry
Add the bench command: every public command in share/commands.yaml is a target, run against a disposable installed repository, with warmup and samples from the policy, reporting min, p50, p90, p95, p99, max, mean and stddev per target and mode.
- Depends on
I0817- Blocked by
- none
- Serves
- none
- Scope
lib/bench.shbin/majordomusshare/commands.yamlshare/allow/policy.txtshare/skeleton/policy.yaml.ai/repo/policy.yamland 3 more- Evidence
- 1 of 1
- Started
- 2026-09-05 03:33:10Z
- Verified
- 2026-09-05 03:33:10Z
- Completed
- 2026-09-05 03:33:10Z
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.