feat(corpus): require retrievable visual review evidence

docs/AUTOMATION_LIVE_SCAN.md

@@ -370,9 +370,11 @@ npm run eval:review-candidates -- --limit=80
 ```
 
 Read `outputs/review-eval-candidates/review-eval-candidates.md`. It is a review
-worklist, not ground truth. Only after expected fields are confirmed or
-corrected against the real artifact should a case move into
-`src/eval/corpus/confirmedReviewCorpus.ts`.
+worklist, not ground truth. Only choose a candidate marked
+`visualEvidence: available`: it had a retrievable local PNG at export time.
+The export exposes only safe capture/run references, never the local crop path.
+After expected fields are confirmed or corrected against the real artifact, a
+case may move into `src/eval/corpus/confirmedReviewCorpus.ts`.
 
 For a manually checked candidate, generate a paste-ready confirmed-case snippet:
 
@@ -380,6 +382,10 @@ For a manually checked candidate, generate a paste-ready confirmed-case snippet:
 npm run eval:prepare-confirmed -- --candidate=<candidate-id> --expect-file=.\path\to\expect.json
 ```
 
+The preparer refuses candidates without explicit labels or retrievable visual
+evidence. Re-export after retaining a crop rather than promoting an OCR-only
+legacy record.
+
 ## Anti-Cheat And Safety Boundary
 
 Do not describe the implementation as bypassing anti-cheat. The app does not