Brummel
c5eca7e91d
Re-baseline bench/baseline_compile.json, last ratified 2026-05-15 (20add51, mut.4-tidy). check_ms shifted +35..47% uniformly across all 12 fixtures (~1.8-3.3ms -> ~2.4-4.7ms); build_O0_ms rose ~10% (90->100ms) but stayed inside its 20% tolerance and so never tripped. RATIFY, not a regression. The decisive signal is that the check_ms drift is *uniform* across every fixture regardless of complexity (hello +35%, nested_pat +35%). Fixture-independent drift means the cost lives in shared per-invocation work, not in any fixture-specific checker path. Two concrete shared-cost growths fully account for it: - examples/prelude.ail grew 116 -> 153 lines (+32%); every `ail check` parses and typechecks the full prelude. - the kernel_stub module is now injected alongside prelude on every check (landed in raw-buf prep.3,9339279, #33) — a whole extra module parsed + typechecked per invocation. Both are real modules added by wanted features, not a quadratic blow-up. There is no fixable type-checker regression hiding here; the +0.8ms is the parse+typecheck cost of more shared source. The throughput baseline (bench/baseline.json) was already re-ratified 2026-05-28 (de4399d); this brings the compile baseline back in sync. Corrects the record: the #44 cycle-close audit body (7321826) wrongly attributed the compile_check exit-1 to transient machine load. main is sacrosanct so7321826cannot be amended; #45 and this commit are the forward correction. Verified: compile_check.py -n5 -> 24 metrics, 0 regressed, 24 stable.