Conversation
# Conflicts: # README.md # src/channel/src/catch-up.test.ts # src/channel/src/catch-up.ts # src/channel/src/durable-receive.ts
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix deferred media ownership, future-dated tombstone retention, cross-facade capacity coordination (including partial admissions), catch-up cursor monotonicity and backward-clock query bounds, restart-safe reply reconciliation, and WebSocket reconnect backoff. Enforce a shared 24-hour provider future-skew policy across webhook, WebSocket, REST catch-up, and durable completion boundaries while keeping invalid timestamps admissible without cursor advancement. Simplify duplicated journal/cursor handling and add focused regressions plus migration and attachment-contract documentation. Validation: all 183 tests, build, manifest check, and OpenClaw host validation pass.