feat(client): recover reserved create operations explicitly - #6
Draft
rrrodzilla wants to merge 1 commit into
Draft
feat(client): recover reserved create operations explicitly#6rrrodzilla wants to merge 1 commit into
rrrodzilla wants to merge 1 commit into
Conversation
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.
Adds an additive create-recovery client for the
create-intent-v1protocol. Preparation returns a frozen submitted snapshot; explicit submission and receipt lookup recover the same operation after a lost response. Mutations never automatically refresh, retry, or reserve a replacement.Current credential/program checks prevent a context change during receipt preflight from dispatching a commit. Typed outcomes distinguish pending, currently readable commitment, and deleted commitment; malformed successful responses remain uncertain. Documentation explains host draft scoping, server deadlines, authorization and external-effect limits.
Validation: 31 built-client tests pass, including existing record/file regressions. Client, React, console and Storybook builds and type checks pass. A minor changeset and packaged guide are included. Backend integration is under separate upstream development; no registry release is claimed.
Stacked on conditional-record client PR #5. Existing ForgeClient implementations remain compatible.