Repository navigation
Add durable owner binary draft operations and recovery - #97
Merged
Merged
Conversation
11 of 25 tasks
vanedaltro
marked this pull request as ready for review
November 2, 2026 03:19
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
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.
Owner binary views now have durable private draft operations: status/preparation, atomic expected-byte patches, undo/redo/discard, paged byte review, receipt lookup, discovery and explicit recovery. Every request refreshes Session/Location/read authority; mutations retain prepared edit authority, native/workspace/path ownership and actual-worker lifetime. Read-only launches reach immutable server admission, and Session deletion refuses dirty or unresolved retained work.
The SDK preserves exact offsets and original mutation revisions, rejects superseded page responses and requires explicit recovery after binary POST transport failure. Binary responses bypass generic HTTP response caching. Native hardening retains parent pins, checks replacement bytes before intent, refuses stale reads after uncertain journal publication and never allocates missing recovery IDs. README, roadmap, feature guide, OpenAPI and SDK sources reflect the delivered scope.
Validation:
Production save/restore, shared snapshot/FileChanged integration, the model binary tool, terminal editing and remaining acceptance continue under #94. Source installation is not exposed by this increment.
Refs #94.