e078b2fe7c
Post-review hardening on the attempt-ownership commit: - Write-time re-validation: the entry staleness check in _restore_compressor_attempt_state runs before the durable-cooldown DB I/O, so a fallback could claim the compressor in that window and the stale setattr loop would still clobber its state. The in-memory writes now re-validate AND execute under _COMPRESSOR_ATTEMPT_LOCK — the same lock claims are taken under. The DB rollback stays outside the lock (safe: the dangerous direction requires a prior claim, which the entry check rejects). Both the quality reviewer and the lead's independent pre-verification converged on this window. New deterministic test: TestMidRestoreClaimRace (claim injected between entry check and write via instrumented deepcopy). - Documented gen-0 semantics on _claim_compressor_attempt: per-compressor all-or-nothing, never mixed with gen>0 on one instance (reviewer finding 2, verified unreachable — comment hardens against future confusion). Dropped after verification (reviewer finding 3): resetting _SUMMARY_ROUTE_CONSUMED on pin_summary_route exit — the echo lives in the worker thread's COPIED context (propagate_context_to_thread) and dies with it; a probe confirmed the next attempt's context is clean. Resetting it would break digests running after the with-block.