From cb98e9a1e46916fae2985491d459fae99f7de185 Mon Sep 17 00:00:00 2001 From: Dmitrii Vasilev Date: Sun, 18 Oct 2026 00:01:51 +0700 Subject: [PATCH] ci(dupe): bless the two deliberate put copies in the NMSE run harness (Closes #10025) #10021 landed specs/benchmarks/gf16_bfloat16_nmse_run.t27 without moving the duplicate-body ledger. Its put_lit and put_range repeat put_msg and put_range in specs/policy/own_language.t27, so the Duplicate Body Ratchet has been red on master since cc80a305d. The copies are deliberate. The harness lowers through t27c gen-c into one C file, and the committed manifest records the spec's own sha256 as x_extension.harness_sha256. Editing the spec to reuse the existing functions would leave that manifest pointing at a file that is no longer in the tree. So the ledger moves instead, written by `python3 tools/dupe_scan.py --bless` on the Railway lab at cc80a305d: two added lines, put_lit 2 and put_range 2. No spec changes. Verified on the lab: dupe_scan exits 1 before the bless and 0 after; --self-test exits 0. Co-Authored-By: Claude Opus 5.5 --- tools/duplicate_bodies_baseline.txt | 2 ++ 1 file changed, 2 insertions(+) diff --git a/tools/duplicate_bodies_baseline.txt b/tools/duplicate_bodies_baseline.txt index d67c1c8eec..bd22fecd73 100644 --- a/tools/duplicate_bodies_baseline.txt +++ b/tools/duplicate_bodies_baseline.txt @@ -160,6 +160,8 @@ perturb_rtl_minimally 2 price_tokens 2 prm_scored_pipeline 2 put 2 +put_lit 2 +put_range 2 reject_resample 2 reject_resample_for_sacred 2 reject_resample_for_sacred_inner 2