Formalize daily Windows service with autonomous startup and SCM supervision #156

Context

The physical Windows execution path in Test Mode passed three fresh campaigns on the RTX 2060 host, but two remaining boundaries prevent classifying this installation as standard autonomous production Windows software:

1. The package currently relies on test-signing; Test Mode is incompatible with Secure Boot and anti-cheat requirements.
2. The SCM service requires an external broker on 127.0.0.1:7700, which is not yet packaged and supervised as a standard Windows dependency.

Closed Evidence

• exhaustive-20260724-224946: PASS
• exhaustive-20260724-225047: PASS
• exhaustive-20260724-225124: PASS
• Nine SHA matches, three direct measurements, three graceful teardowns.
• Zero residual LUN/Win32/PnP artifacts and zero minidumps.

Closure Criteria

• Package signed via Microsoft Attestation / WHQL or a trusted production code-signing certificate.
• Clean InfVerif and SignTool verify /pa /all validation with Test Mode disabled.
• Control plane and broker packaged, configured, and supervised as a native Windows service dependency.
• Deterministic boot, start, stop, and disaster recovery ordering documented.
• Three consecutive cold boots demonstrating Online state, data integrity, lease release, CUDA memory restoration, and clean terminal state.