The 07/16 22:09 B3 gate run FALSE-FAILed the one-shot oracle: the naive
POSITIONAL compare ignored that correlate2D_inter assigns corr rows via
atomicAdd - row ORDER is legitimately nondeterministic between runs (the
rung-1 'order-independent corr compare by packed index' rule); all 497
poses stayed BYTE-IDENTICAL to the B4 record while the run was driven by
batched cycles, proving the chain end-to-end. Fixes:
- oracle compares per packed corr index (HashMap row lookup): index SETS
  must match and every index-matched 8-float peak row must be bit-exact;
- REAL oracle FAIL now disables the batched path for the run (fail-safe:
  a divergence must never drive production);
- B3_CHAIN profile stage attributed from the pre-gpuTaskBuild timestamp
  (was a fresh start AFTER the chain -> recorded ~0 and leaked ~2 ms/
  cycle into 'leanMeasure other') and printed in the profile summary
  (printSummary never printed the new stage).

mvn PASS. Oracle PASS line expected on the next routine run.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>