Classify wine-access CTest baseline anomaly

docs/testing/wine-proton.md

@@ -258,11 +258,17 @@ Cthulhu `go test ./...` passes in full when run unsandboxed
 (the sandbox-only Unix-socket failures seen during Phases 1–3 do
 not occur), `go vet ./...` is clean, the parity ledger validates,
 and the brlapi-tagged wine/config/preferences suites pass.
-Wine-access builds clean; its CTest suite ran 5/7 with
-`review-capture64` and `review-capture32` failing at one
-stale-status check on source unchanged since they last passed —
-recorded as an unexplained baseline anomaly to re-run on a quiet
-desktop during this phase, not yet classified.
+Wine-access builds clean. Its CTest suite initially ran 5/7 on
+the live desktop, with `review-capture64/32` failing at one
+stale-status/clipping check on source unchanged since they last
+passed; follow-up classification on 2026-11-02 identified
+display-environment sensitivity, not a code regression: under a
+private Xvfb screen the review-capture pair passes while
+`foreground-focus` fails for want of real window-manager focus
+semantics, and on the live desktop the pattern inverts. Every
+test passes in at least one environment; one single-environment
+7/7 run (live desktop while it is quiet) is still owed before
+this phase closes.
 
 - Diablo IV (Proton app 2344520), 2026-11-02 — **passed so far.**
   Exclusion-list-only configuration, global controller-only switch