release: bump version to 0.74.2

docs/HARNESS.md

@@ -135,11 +135,18 @@ PLANET_HARNESS_FRONTEND_SMOKE_PORT=4174 scripts/harness/validate.sh
 - Treat user-provided screenshots and images as primary visual evidence. If a
   screenshot contradicts written text, inspect the image first and explicitly
   call out the mismatch before deciding what to change.
-- If a referenced screenshot path cannot be opened, do not infer image content
-  from the filename, alt text, surrounding prose, or memory. Search the current
-  thread attachments, repository, and obvious local attachment/download
-  locations; if the image still cannot be found, ask for the file or report the
-  blocker instead of guessing.
+- Path resolution is part of visual evidence handling. If a referenced
+  screenshot path cannot be opened, try reasonable local equivalents first:
+  WSL/Windows path conversion, workspace-relative paths, absolute paths, current
+  thread attachments, repository files, and obvious local attachment/download
+  locations.
+- If the image still cannot be found or opened, report the exact path/access
+  blocker instead of guessing. Do not infer image content from the filename, alt
+  text, surrounding prose, logs, or memory.
+- OCR is acceptable evidence for text-only questions or non-multimodal
+  environments; state when OCR was the fallback. Layout, color, spacing, pixel,
+  and rendering issues still require a real visual inspection or an explicit
+  "could not verify visually" note.
 - Same-category UI surfaces must use one visual system per product area. Badges,
   chips, pills, tags, status labels, small buttons, cards, panels, and toolbar
   controls should reuse the shared component, shared token, or established CSS