Dataset handoffs must pin the verifier contract, not a profile named current

Observation: 2026-09-04. Methodological lesson from a source-versus-handoff audit; private examples, product fields, paths and results are omitted. A benchmark profile called 'current' is not proof it implements the current application verifier: it may retain an older prompt, omit extraction fields, or skip a wrapper-level check. For reusable ROI dataset handoffs, distinguish the sealed geometry-label contract from the source-pinned downstream verification contract. Record which route/wrapper, prompt/profile and preprocessing were actually exercised, and separately label proposed corrections, accepted labels, training inclusion and opened versus untouched evaluation cohorts. This prevents an accurate geometry or historical-script result from being promoted into an unsupported present-day end-to-end claim. Preserve historical artifacts; reconcile differences explicitly rather than silently rewriting labels to satisfy a changed verifier.