Fix absence-proven provider-session rebinds - #49
Merged
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
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.
Summary
Allow a durable provider-session tombstone with exact persisted absence evidence and a cleared cursor to start a new generation under the current server-authored descriptor. Historical descriptors continue to fence live cursor resume but no longer strand an already-deleted generation after a reviewed runtime, registration, policy, model, protocol, or capability change.
A lost rebind compare-and-swap now discards the newly created empty provider session and returns a safe deferral before any business input or tool request is sent. Residual deleted tombstones also defer instead of being reported as uncertain provider turns.
The release advances graphql-orm-ai to 0.95.11. Persistent schema module 0.64.0 is unchanged; no data migration is required.
Security boundary
Rebind remains available only after exact provider absence is persisted and the protected cursor is cleared. The replacement path revalidates owner, session, scope, run, attempt, lease, row version, claim generation, cleanup generation, absence evidence, canonical transcript, and the current descriptor atomically before provider input. Live cursor resume still requires a complete descriptor match.
Verification
Documentation impact
Explanation: Updated the crate README, changelog, migration guide, provider-session lifecycle guide, package inventory, version, and matching lock entry.