test: cover cursor decoding and script integrity metrics

docs/implementation-plan.v1.md

@@ -1157,8 +1157,10 @@ Use one declared test matrix and the same harness entry points everywhere:
   native Windows integration suites, plus `smoke`, `idempotency`, `reconnect`,
   and `retention` E2E scenarios;
 - release candidates run every E2E scenario, including the resettable
-  interactive Windows VM matrix, Server Core smoke, destructive fault cases,
-  upgrade/recovery, and soak.
+  interactive Windows 10 VM matrix, destructive fault cases, upgrade/recovery,
+  and soak. Server Core, older-build, and ambiguous-multi-session smoke lanes
+  run when their dedicated fixtures are provisioned; they are explicitly
+  deferred compatibility work and do not block the Windows 10 v1 baseline.
 
 CI allocates a run ID per job, always invokes `collect` after failure, and invokes
 `reset` in an unconditional finalizer. Upload only the bounded redacted report,

docs/testing.md

@@ -286,6 +286,8 @@ execution context. The normal `rvboxtest` console session remains the subject
 of active-user and elevation tests. See [testing-vm.md](testing-vm.md) for the
 exact fixture contract.
 
-The VM is the minimum smoke lane, so native multi-session/ambiguous-session,
-Server Core, and older-build entries remain explicitly blocked until their own
-fixtures exist. Their pure selector tests remain mandatory.
+The VM is the current Windows 10 v1 smoke lane. Native
+multi-session/ambiguous-session, Server Core, and older-build entries are
+explicitly deferred compatibility work until their own fixtures exist; they do
+not block the Windows 10 v1 baseline. Their pure selector tests remain
+mandatory.