No rerun forgiveness, no ambient-load allowance

The user’s audit decisions of 2026-10-07 (PLAN.md, “USER DECISIONS (2026-10-07, audit)”):

Flaky-rerun forgiveness is DELETED. Each flaky test is fixed at its cause, and the checks are deterministic. A new failure that the flaky memory already holds is a regression like any other: nothing is re-run alone to pass. A suspect leaves the reds only through FLAKE-REPRO, or is owned by a shrink-only burn-down entry: nothing ages out (there is no window, and a failing row the run history trims moves to its never-trimmed suspect archive, round 13).
The budget-level forgiveness is DELETED too (round 12, the user’s decision #2 of 2026-10-08). A CPU budget breach once passed until three consecutive runs breached (overCapRunsBeforeRed) and inside a “recorded, not red” spread band; both are deleted: one judged run over the cap fails (UR-24-BUDGETS).
The ~12% ambient-load allowance is REMOVED (built 2026-10-22 with NO-LOAD-BLOCK’s measurement half). It was a slope of 5% per unit of recorded 5-minute load per CPU, capped at 12%. The envelope (ambientInflationFraction in engine/src/shared/budget-verdict.ts), its configuration keys (webUiSuiteCpuBudget.ambientInflation*) and its signals are deleted: no cap moves with host load, and the load legs are printed beside every verdict as recorded signals (D-17, UR-24-BUDGETS).