docs: update scanner roadmap after merge

docs/AUTOMATION_LIVE_SCAN.md

@@ -223,9 +223,8 @@ Latest live timing evidence on 2026-07-08:
   `elapsedMs: 63616` because 50 single-record writes produced
   `writeFlushMs: 8163`.
 - Current source replaces that experiment with batch persist and quiet
-  auto-scan UI captures. This is code-validated, but the batch version still
-  needs a fresh elevated live run; the follow-up restart was blocked because the
-  admin runtime did not become reachable after shutdown/UAC.
+  auto-scan UI captures. Later direct-GDI live runs validated the batch/quiet
+  path at limits 20, 45, and 100 with 0 misses in the current environment.
 - Direct GDI hot-path validation:
   after skipping `desktopCapturer.getSources()` in auto-scan artifact captures,
   the 20-artifact iteration baseline improved to `20/20` parsed, `19` stored,
@@ -248,6 +247,14 @@ Latest live timing evidence on 2026-07-08:
 - OCR/parser eval after this speed pass: `npm run eval` passed with `23/23`
   exact-match cases, `100%` field accuracy, and `100%` critical fields. This is
   a regression gate, not a substitute for manually checking live artifact values.
+- Ownership and lock proof on 2026-07-09:
+  `/scanner/start?entry=visible-inventory&limit=20&engine=current` completed
+  `20/20` verified and parsed, `19` stored, `1` duplicate, `0` review, and
+  `0` misses in `8047 ms`. Smart Capture parsed equipped footers for `Citlali`
+  and `Linnea`, reported an unlocked artifact as `locked: false`, then reported
+  a visibly locked artifact as `locked: true` with `lockSignal.ratio:
+  0.14797913950456323` over threshold `0.06`. A follow-up bounded scan
+  persisted that locked artifact with `equipped: "Citlali"` and `locked: true`.
 - 3 artifacts/second preparation:
   auto-scan artifact captures now also omit the detail-preview payload and
   expose `averageCaptureRoundTripMs` plus