Skip to content

fix(federation): ignore retired clock keys during causal replay - #149

Merged
Fail-Safe merged 1 commit into
mainfrom
fix/federation-legacy-clock-replay
Aug 22, 2026
Merged

fix(federation): ignore retired clock keys during causal replay#149
Fail-Safe merged 1 commit into
mainfrom
fix/federation-legacy-clock-replay

Conversation

@Fail-Safe

Copy link
Copy Markdown
Owner

Summary

  • prevent false divergence detection when a post-migration event is causally newer on every stable Cortex ID but an older event retains a retired name-key clock component
  • preserve genuine stable-ID concurrency and ambiguous legacy-clock cases
  • leave historical event clocks and signatures unchanged
  • bump the patch version to 0.21.2

Validation

  • cargo fmt --check
  • cargo clippy --all-targets -- -D warnings
  • cargo test --all-targets --locked
  • make release-check

The regression suite covers ordered stable clocks with a retired key, genuine stable-ID concurrency, legacy-only ambiguity, end-to-end replay materialization, and preservation of the stored historical clock.

@Fail-Safe
Fail-Safe merged commit ae34320 into main Aug 22, 2026
2 checks passed
@Fail-Safe
Fail-Safe deleted the fix/federation-legacy-clock-replay branch August 22, 2026 23:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant