fix(coordinator): preserve acknowledged state across access changes

[Mathieu2301]

Summary

• Preserve relay-acknowledged coordinator state across ACL/event/function re-declarations and reconnects, instead of replaying initial configuration values.
• Keep explicit state replacement authoritative; do not replay rejected or outcome-unknown mutations or application calls. Handle pending ACK races without blocking access revocation.
• Restore acknowledged deletions after activation and document the protocol-limited transient value window.
• Make the starter binary regression build its own prerequisite (independently reproduced missing-dist failure in a fresh checkout).
• Prepare miakapi@4.0.0-alpha.1; CLI stays at alpha.9.

Evidence

• Original owner/guest integration: acknowledged temperature 22 reverted to 21 after guest access withdrawal, with the owner view incorrectly marked current.
• 20 focused regression tests, root 429 tests, 11 pinned coordinator contracts and Node/browser/pack checks passed independently before version preparation.
• Actual local Go relay + pinned browser SDK + trusted shell + isolated app: two device/language groups, each with owner, guest and outsider, now pass state projection, owner-only synthetic action, dynamic withdrawal/re-grant, same-socket reauthentication, identity switch and sign-out.
• Fixture-only lease corrected from 30s to 31s client maximum to cover the relay fixture clock offset; no SDK assertion weakened. No production credential or actual resident identity used.
• Final root and all-package checks run before merge; CI required.

Limits / deployment

• No live home, device, real account, coordinator deployment or platform/browser bundle changed by this PR.
• STATE_SYNC cannot encode an owned path without a value; an acknowledged deletion is restored just after activation. A brief declared-value window remains and is documented.
• Unknown outcomes fall back to last acknowledged state, not inferred success. Real authenticated resident acceptance remains open.