AWS host automatic solver deployment

Deployed September 12, 2026 Pacific (September 13 UTC), on existing production parent i-0de9795ee9d3ce090. No additional EC2 instance was launched.

The new attested-relay-host-solvers.service polls the local public-artifact index every 30 seconds, verifies exact-PCR0 archived evidence, and starts up to eight native single-chain recovery jobs. It runs at nice 19 on parent CPUs 0 and 25–31, with a 24 GiB ceiling. The production enclave's CPUs are excluded. The service is enabled at boot and configured to restart on failure.

Validation:

• SDK and ARM native 0.2.0a4 wheels matched the previously published SHA256 proof.
• New isolated Python 3.11 venv passed dependency checking and native CLI launch. installed.txt records the resolved dependency versions.
• systemd-analyze verify accepted the unit; its only warning concerned an unrelated pre-existing acpid socket using /var/run.
• The actual service account verified production bundle 797ddd66a68247e108cf6c41a3403358a36fd8ce0ce3dfb08b24296064be7861.bundle.json.
• Native PID 110822 started puzzle 35a5f9545bbd48db64604657242b79cb16879aec5611d9c46aa0a83bd9b51acc.
• One deliberate restart of only the new follower launched PID 110964, which resumed at iteration 40,000 and progressed to 70,000. Process affinity, nice value, enabled status and other service states are in restart-proof-final.json.
• Old host recovery, parent relay, credentials bridge and Cloudflare tunnel remained active. The same production enclave remained ready with Mullvad up.

The initial evidence parser failed on the native journal's intentional blank restart separator. Correcting the parser confirmed the already-successful resume; no second restart was needed.

This is host solving, not automatic publication of recovered keys/plaintext. The existing Hetzner solver continues independently. See the deployment/configuration and AWS guarantee boundaries.