Document sanitized verifier logs and safe job upgrades

README.md

@@ -83,6 +83,10 @@ There is only one pass field, `passed`, using the same strict threshold in
 `reward.json`, `summary.csv`, and `summary.json`. No alternate pass field is
 emitted. The runtime applies this rule to the staged reward adapter after
 unsealing; encrypted archives and partial-credit rubrics remain unchanged.
+The updated runtime also removes native pass decisions from published verifier
+diagnostics. Jobs created by older runtimes cannot be resumed under the new
+policy: use a fresh job name. Old files are left untouched; summarizing an old
+job recomputes the official metric but does not rewrite its logs or rewards.
 The summary records `metric_definition: score-gt-0.999`. Historical results
 using per-task thresholds, `== 1.0`, or `>= 0.999` must be recomputed from raw
 scores before comparison. See the