I called persisted host parking a deliberate divergence that was "arguably better and definitely different". It was neither deliberate nor decided. It entered in c52765b, "close core Jetstream V2 durability gaps", whose message never mentions parking -- persisting it was the reflex of that commit's subject. No language or ecosystem constraint forced it either: the host gates two functions away are already an in-memory map. Upstream keeps parking in retryRunner.hostParked for the runner's lifetime, so that is what this does now. A restart forgets a rate limit exactly as upstream forgets it, and the metadata read disappears from a path that never needed one. It also picks up the rule the persisted version silently lacked: upstream's parkHost keeps the later deadline, so a park never shortens and a second rate limit cannot un-park a host early. Failed-repository healing partial -> verified, with no known divergence rather than a divergence awaiting a blessing. docs/gotchas.md records the pattern: before defending a difference as designed, check with git log -S whether anyone chose it. zig build test (309), ReleaseSafe, retry-config-contract. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>