feat(automation): support qualified single-user Windows operation

docs/automation/README.md

@@ -1,5 +1,7 @@
 # Autonomous Jobjakt backlog controller
 
+**For your normal Windows login and existing ChatGPT account, use [single-user setup](SINGLE_USER.md).** It requires no second Windows account, subscription or VM. The new default is an operator-controlled pause, with explicit MXC qualification before unattended work. The separate-identity instructions below describe the optional legacy `dedicated-runner` mode only. Neither mode activates the roadmap automatically.
+
 This implementation builds the orchestrator only. **The real backlog is disabled. Phase 10 is NO-GO pending its own entry decision.** See [audit](AUDIT.md), [gate register](GATES.md), [security boundary](SECURITY.md), and [acceptance evidence](ACCEPTANCE.md).
 
 ## What is installed
@@ -32,7 +34,7 @@ pwsh -NoProfile -File automation/tests/Test-Approvals.ps1 -Verifier "$PWD\script
 
 Tests create disposable local worker repositories and bare remotes. The subprocess double exercises the real supervision/result/report paths without a model or network. RSA tests use temporary in-memory keys/certificates and do not install an owner key. They do not qualify the Windows sandbox or real application acceptance.
 
-## Provision an actual runner, after approval
+## Optional legacy dedicated-runner provisioning
 
 Use a dedicated development Windows account/VM with no production credentials, mounts, Docker socket, remote admin access or production network routes. Keep the owner's signing identity separate. A source worktree provides edit isolation; it is not a production security boundary. Prefer a **separate clone** for unattended execution, avoiding shared Git metadata/hooks with ongoing human work. The owner must protect main/production refs server-side and grant the publisher only the intended development refs.