feat(cloud-connection): unbind keeps an identity residual for re-bind continuity#1797
Merged
Conversation
… continuity
Disconnect clears the credential (revoking cloud-side first) but keeps
{runtimeId} in the store — a later re-bind to the same org claims and
revives the same registration (cloud claim rule reactivates the revoked
row) instead of minting a new device per disconnect cycle. Same shape
as an iCloud device record surviving sign-out.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
github-actions
Bot
added
documentation
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
2 participants
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.
Phase 2 of the cloud runtime-identity-binding ADR: Disconnect clears the credential but keeps the identity.
{runtimeId}to the store instead of deleting itConnectionCredentialStore.read()accepts token-less residuals;credential()already treats the empty token as "no credential", so status correctly reads as unbound while surfacing the runtimeIdPairs with the cloud-side Connected Runtimes governance PR (rename / revoke / remove list actions).
+2 tests; 42/42 green.
🤖 Generated with Claude Code