Repository navigation
Prism id on stitch again, with QR linking and apps that hear removals - #79
Merged
Merged
Conversation
This reverts commit 7b5fbbc.
Restores prism/identity/4 (reverting the containment revert 7b5fbbc, whose PR named no defect) and re-pins stitch's Prism id to 7c0cceb: - the link offer shows its QR code (stitch's linkQr), drawn as one SVG path with its quiet zone, dark on white in both themes; - every share also publishes the id's public log (publishLog), and verifySession, sign-in and recovery merge it (heardLog, verifyAction's bus), so a session from a device removed elsewhere is refused even when that device never synced; - the relay bus reads what the relay holds with retained(), stitch's bus contract. identity/test.mjs also checks the QR code. npm run test:identity: 16/16, three runs. frame.lock re-locked. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013Asa3NdLCxdzL1iQw9rg5T
afflom
enabled auto-merge
November 14, 2026 06:49
afflom
disabled auto-merge
November 14, 2026 07:07
afflom
enabled auto-merge
November 14, 2026 07:07
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.
Re-lands prism/identity/4, which #76 rolled back "for containment". Neither that PR nor foundry#189 names a defect: CI on #73 and #75 was green, and no issue or review is linked. The account owner asked to continue. The rollback changed only one thing for users: existing passkey sessions keep working until they expire. With this re-land they end, and the visitor creates or joins a Prism id. Nothing in Foundry or the template keys data by account, and no stored data is deleted.
On top of #73, this pins stitch's Prism id to 7c0cceb (afflom/stitch#2):
linkQr), drawn as one SVG path with a quiet zone, dark on white in both themes.publishLog).verifySession, sign-in and recovery merge it (heardLog,verifyActionwithbus). A session from a device removed elsewhere is refused, even when that device never synced.retained(), stitch's bus contract.PROTOCOL.md and README.md are updated. Still open in stitch: a replayed old kit forks the recovery chain (every frame that hears the public log refuses it; ordering the two needs stitch's witnessed time), and the relay keeps messages for 30 minutes.
Tests:
npm run test:identitypasses 16/16 in three consecutive runs, including the new QR check.frame-sync --checkmatches 18 of 18 files after--lock.Generated by Claude Code