Fixes startup after launching Spynel before installing a harness. The primary now reconciles its saved harness selection with the existing worker through the authenticated settings transaction, including custom ACP commands installed at the same path. No ownership-file deletion or provider-turn replay is needed.
New workers also keep configuration reachable after an initial harness handshake failure, reporting the harness unavailable until its installation is corrected. Retained work and unconfirmed cleanup still prevent structural replacement.
Verified with missing, corrected and broken harness fixtures; native adoption of the published 0.14.0 worker; Go tests, vet, build, smoke, npm checks and targeted race tests.
The exact release commit passed the native Linux/macOS amd64/arm64 release gate: https://github.com/agent0ai/spynel/actions/runs/39318695073
Known limitation: a retained 0.14.0 worker can still reject a hand-written partial configuration through its old canonical-reload check. The normal configuration generated by spynel init is unaffected; new 0.14.1 workers also pass the partial-configuration installation/relaunch test.