feat(corpus): require retrievable visual review evidence

docs/CURRENT_STATUS.md

@@ -45,6 +45,10 @@ The fresh current-build smoke is documented in
   the current corpus work: 128 are explicit 1–4★ entries, six have the same
   exact duplicated-decimal OCR defect, one requires slot-safe name resolution,
   and one incomplete crop intentionally remains `Review`.
+- The review-corpus exporter now exposes only safe capture/run references and
+  prioritizes candidates with a retrievable local crop. The confirmation
+  preparer refuses OCR-only records, so a parser guess cannot become ground
+  truth without retained visual evidence.
 
 ## Verified Evidence
 
@@ -74,6 +78,11 @@ does not certify the current change set by itself:
   `native-scanner-run-timing-v1` record. Request-to-reconciliation was
   `28,022 ms` (`~1.78 Artifacts/s`); that is a functional/safety result, not a
   3/s performance claim.
+- The follow-on review-evidence workflow passed focused exporter/preparer
+  checks plus `npm run lint`, `npm test` (72 files / 446 tests), and
+  `npm run build`. A read-only export of the current local queue found 177
+  records and three retrievable crops; all three are already-confirmed
+  `native-review-approved` cases, so no new label was promoted.
 
 ## What Still Needs Testing
 
@@ -109,9 +118,12 @@ does not certify the current change set by itself:
 
 1. Keep the passing built-renderer acceptance distinct from the optional
    elevated packaged-executable runtime/UAC check.
-2. Clean generated workspace outputs, commit the coherent checkpoint, and push
-   the intended branch; the current-build 50-artifact live gate has passed.
-3. Continue the next quality phase with visually confirmed corpus growth,
-   fail-closed parser behavior, profile-source refreshes, and packaged UI
-   regression coverage. Do not broaden game-category scope or add in-game
-   mutation.
+2. The generated workspace outputs were cleaned and the coherent checkpoint
+   was committed and pushed as `8b9f948` on 2026-07-11. The active admin
+   runtime's locked log was intentionally left untouched.
+3. Re-export future Review cases and only label candidates marked with
+   retrievable visual evidence. No currently retrievable local candidate needs
+   a new corpus label.
+4. Continue the next quality phase with fail-closed parser behavior,
+   profile-source refreshes, and packaged UI regression coverage. Do not
+   broaden game-category scope or add in-game mutation.