test(automation): record fresh single-user installation verification

automation/reports/single-user/packaging.json

@@ -0,0 +1,20 @@
+{
+  "configuration": "PASS",
+  "mode": "single-user-local",
+  "executionPolicy": "operator-controlled",
+  "runtimeReady": false,
+  "executionEnabled": false,
+  "sourceGaps": [],
+  "unqualifiedAdapters": [
+    "qualified-provider-browser-python-pdf-security-preservation"
+  ],
+  "checkpoints": 49,
+  "phase10": "NO-GO",
+  "note": "Read-only planning; no model, Git mutation, network, service, signing or scheduling action",
+  "checkedCommit": "1e6c80f708b2cc7c3dfa497e082e8a498045c751",
+  "sameWindowsIdentity": true,
+  "statePreservedOnRepeatedSetup": true,
+  "authenticationProfileEmpty": true,
+  "realSessions": 0,
+  "scope": "Fresh committed local clone; source and installed setup, disabled dry-run; no model or real roadmap"
+}

docs/automation/SINGLE_USER_ACCEPTANCE.md

@@ -30,6 +30,7 @@ Source: `codex/autonomous-roadmap-single-user`, based on `c1663df`, in the exist
 - `setup-results.json`: same Windows identity, empty dedicated authentication, zero sessions, disabled queue and Task Scheduler refusal before registration.
 - `capabilities.json`: actual CLI feature-state verification and zero effective MCP servers.
 - `format-check.json`: packaging removed one trailing space in the new test file after the full run; its Python AST is identical to the tested bytes. The original full-run hash remains recorded, with the packaged hash separately identified. No extra test count is added for formatting.
+- `packaging.json`: a fresh committed clone at `1e6c80f` installed the mode successfully; repeated setup through the installed wrapper preserved state, the auth profile stayed empty, all prompt sources validated, and zero real sessions were launched.
 
 The first new MXC probe could not start because the old subprocess environment omitted SystemDrive. Only that non-secret OS variable was added to the existing allowlist; no unrestricted environment or sandbox fallback was enabled. Explicit MXC startup and the subsequent real canary probes passed. The previous legacy CryptUnprotectData result remains historical evidence; the user's normal saved sandbox selection was not changed.