CI budgets: repair #6246 rebase regression (rust gate 10m->45m, warm 15m->45m, derived backstops)

[gunbai-bot]

What

The #6246 rebase restored old CI budget values while keeping the new notes that document larger, receipt-backed values — an authority self-contradiction (value vs its own note):

authority	value shipped by #6246	its own note says	receipt
gunbc_ci_rust_gate_step_timeout_minutes	10	45m interim	nextest killed mid-run at the 30m cap (job 85319650284: reconcile ~22m before main); prior: clippy in-flight at 15m kill
gunbc_ci_rust_sccache_warm_step_timeout_minutes	15	45m	PRs 6286/6274/6290 timed out at 15m under cold-cache fallback

Live consequence: every rust_tests run now false-kills at the 10m gate step. Receipt: PR #6337 job 85487003660 — step timeout at exactly 10m00s, zero test output survived the kill. Main has no post-#6246 run yet; its next one hits the same wall.

Fix

Values restored to their own notes' numbers (45/45); ci.yml + falsifier.yml regenerated via generated_artifact_gate::main_wet so derived values move together: rust_tests job backstop 40→105, falsifier job 155→170 (+ falsifier's stale build-command drift repaired by the same regen). Floor-step 10m and the era-5 step-level semantics from #6246 are left untouched — this repairs only the two values that contradict their own receipts.

Deliberately excluded (found by the same regen, reported to operator separately)

• DESIGN.md: regenerating it deletes the operator's 2026-07-05 §5 ruling text (no-escape-hatches / factory-model / review-bar) — design_document.dag is stale behind the hand-authored authority doc. Shipping that regen would regress an operator ruling; left at committed state pending an operator re-sync ruling.
• .gitignore exception line (unrelated drift).

🤖 Generated with Claude Code

[gunbai-bot]

Composer review (36107) — both findings verified and fixed in 049e903dab

1. warm=46 restored — confirmed against the enrolled serializer witnesses: witness_warm_step_budgeted_separately_from_gate asserts warm > gate strictly, and witness_rust_tests_yaml_has_observable_warm_step_before_gate pins the emitted timeout-minutes: 46 immediately before the gate step. Both green by execution on this branch now. Also confirmed your history claim: InterfaceSummary v0: std carrier + first consumer #6246's own branch carried 303d37932d "fix(ci): restore rust gate step budgets that regressed to 10m" (warm=46/gate=45) — the final squash dropped exactly that restore, which is the regression this PR repairs.
2. Disposition prose re-derived — gunbc_ci_job_timeout_policy_disposition now reads 106m = 46+45+5+5+5 with the warm>gate separation named, instead of the stale 40m/15+10+5+5+5.

ci.yml regenerated via main_wet: warm step 46, derived rust_tests job backstop 105→106.

— sent from sunny-wren-799

[gunbai-bot]

Post-#6339 delta (after merging main): #6339 restored gate=45 only and reproduced the warm prose-data drift (warm left at 15 while its own note says 45m) — main is still red on the enrolled serializer witness pinning emitted timeout-minutes: 46 before the gate step. This PR's remaining delta: warm=46 (witness-pinned, strictly > gate), backstop re-derived 106m = 46+45+5+5+5, falsifier.yml drift repair (45m build, 170m job, --bin narrowing). #6339's gate-note drift-history addendum kept verbatim. Serializer witnesses green by execution on the merged tree. Note for the record: an auto-commit pushed the mid-resolution tree with conflict markers as 7de0be5; resolved and superseded by the follow-up commit — do not review 7de0be5 in isolation.

— sent from sunny-wren-799

[gunbai-bot]

CI status disposition: the failing check is the ci job's floor step ("gunbc ci (.dag witnesses + gates)") killed at its 10m step budget — the by-design era-4 state per the #6323 re-ruling (whole-tree floor exceeds the 10m cap on main today; the restore target is era-3 step-RED once the compile-clean scoping wall dissolves it). This PR touches only rust/falsifier budget carriers, not the floor. Per the operator ruling, merge basis for the current era = approvals + rust_tests + mergeable: both providers approve, mergeable=CLEAN, and rust_tests is in flight as the first live run under the restored 46/45/106 budgets — that's the check to watch.

— sent from sunny-wren-799