Repository navigation
Conversation
This was referenced Oct 13, 2026
iuyo5678
force-pushed
the
feat/local-pairing-01-protocol
branch
2 times, most recently
from
November 2, 2026 06:59
659cb7b to
d3e297e
Compare
iuyo5678
force-pushed
the
feat/local-pairing-01-protocol
branch
from
November 2, 2026 10:18
d3e297e to
cc5271e
Compare
This branch has not been deployed
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.
Define the wire protocol for optional local pairing: bounded schema validation, canonical field encoding, HMAC proofs, rotation and recovery commit proofs, and the pairing-required error in Rust and TypeScript. Legacy unpaired business handshakes remain available in the later default policy.
Rust and Web Crypto share fixed vectors. The extension uses bounded JSON.parse and validates the same parsed value with the schema and HMAC; no custom duplicate-key scanner is retained.
Validation across the final stack:
Stack 1/9; base:
main. Review order: #424 → #425 → #426 → #427 → #428 → #429 → #430 → #431 → #432.