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.
I2489 · development-runtime · p1 · wave 2
A screen over its budget fails the build: the UI's latency budgets are benchmark policy, and bench --check holds them
Make the owner's UI latency budget something CI enforces: the benchmark policy declares absolute bounds, bench --check holds them with or without a baseline and on every host, and the ui job runs that check on every change that can slow a screen.
- Depends on
I2486- Blocked by
- none
- Serves
- none
- Scope
apps/majordomus-cli/src/bench/baseline.rsapps/majordomus-cli/src/ui/command.rsapps/majordomus-cli/tests/bench_units.rs.ai/repo/benchmarks/rust/policy.yaml.ai/repo/ci/gates.yaml.github/workflows/validate.ymland 4 more- Evidence
- 3 of 3
- Started
- 2026-10-13 12:50:07Z
- Verified
- 2026-10-13 12:50:24Z
- Completed
- 2026-10-13 12:50:44Z
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.