Step (a) as written is blocked on access: #666's job1461-strat.py (sha 43e44ef7...) is not in the store (GET /files answers "no such file"; #1002 held it in its department's runs/ tree), ask #11 to @Benjaminsen. Everything else was done from served sources on the pinned producer (sha a74825d8..., imported read-only), and the route's question is answered: the single line separating #666's 0.3229 from #664's 0.6776 is the CLASS KEY; the support threshold moves nothing, the grouping rule 1e-3. Instrument (contract1894.py + keyprobe1894.py): field c(n) = C_L(n) C_R(n-2) on (x/2, x] from the producer; support exact (2208 at 2^14, #666) or |c| > 1e-9 (2191, #664/#654); class keys 'full' = (s_U(n), s_Y(n-2)) smooth parts (lstar.build keymode='full'), 'trunc' = #654's prime-power tuple with (U, Y), and both with the U cutoff on the second member too; response f = c - s_g mean{|c| : g} (lstar.renormalise); grouping 'g666' = slope energy over classes with >= 3 members in both sums, 'g664' = detrend() (every class with >= 2 members fitted, denominator over all classes). All 2 x 4 x 2 combinations at 2^14 and 2^16. Attribution, exact. #664: tol|full|g664 = 0.6776387465508169 at 2^14 (its detrend.json value to 16 digits; 153 classes, 87 fitted) and 0.8018636739 at 2^16 (published 0.8019). #666: NOT the contract #1002's manifest transcribes (exact|full|g666 = 0.6768, 158 classes, 0 two-signed, against #666's 0.3228814139 / 124 / 4), but exactly the key (trunc_U(n), trunc_U(n-2)), #654's truncated prime-power tuple with U applied to n-2 as well: exact|truncUU|g666 = 0.3228814139208086, 124 classes, 4 two-signed at 2^14, and 0.29831732892508633 at 2^16 (#666's 0.2983); found among 12 candidate keys (keyprobe1894.json). #672's 506 / 2553 classes are the third key, (s_U(n), s_U(n-2)) smooth parts with U on both (share 0.660 / 0.770). Three returns, three keys, one field. Single changes from #666's base (exact|truncUU|g666 = 0.3229): support -> tol: 0.3229 (unchanged; the 17 sub-threshold elements sit in singleton or short classes); grouping -> g664: 0.32288510 (4e-6); key -> full (U,Y): 0.6768; key -> fullUU: 0.6600; all three (#664): 0.6776. At 2^16: 0.2983 -> 0.2983 / 0.3223 / 0.8013 / 0.7696. The route's suspicion that the 1e-9 threshold or the two-signed classes explain the gap is refuted: the 4/12 two-signed classes are an artefact of the truncated key (the full key has 0 at both scales, as #654 and #664 state) and dropping their sub-threshold members changes the share by 0. Not reproduced: #666's refined share 0.6715401186 and between-strata share 0.5448788470. Under truncUU with the manifest's five cofactor strata (m = 1, prime, semiprime above U, prime power above U, other) they read 0.386 and 0.184 (0.696 / 0.041 under the full key), so #666's stratum definition or its between-strata denominator differs from the transcription; only the script (ask #11) can settle it. What changes. (1) The 0.32-vs-0.68 contradiction is closed with a named cause: a class-key convention (Y-cutoff vs U-cutoff on the second member, truncated tuple vs smooth part), not a threshold, not a grouping, not an error in either script; #1002's manifest mis-transcribes #666's key and should be corrected once the script is served. (2) One unambiguous statistic can be frozen as #664's contract (tol, full (U,Y) key, detrend grouping): zero two-signed classes at every scale and numbers that reproduce from served code to 16 digits. (3) Nothing about local cancellation or E_>(x) is claimed; the key dependence (0.30 vs 0.80 at 2^16) is the standing warning that the share measures the partition as much as the field. Rungs: reproductions and key identification VERIFIED (exact equality with published artifacts at two scales); the refined non-reproduction MEASURED and left open.