Skip to content

docs: explain optional local pairing and independent upgrades - #430

Open
iuyo5678 wants to merge 1 commit into
feat/local-pairing-06-popupfrom
feat/local-pairing-07-docs
Open

iuyo5678 wants to merge 1 commit into
feat/local-pairing-06-popupfrom
feat/local-pairing-07-docs

Conversation

@iuyo5678

@iuyo5678 iuyo5678 commented Oct 13, 2026 •

Copy link
Copy Markdown
Collaborator

Document optional local pairing for fresh installs, existing profiles and independent CLI/extension upgrades. Installation no longer requires pairing; the CLI starts or reuses the daemon when the user chooses to pair. Explain why paired connections never automatically downgrade after verification failure.

Update installation instructions, both READMEs, privacy notices, architecture, changelog and host/remote guidance. Add a Chinese pairing guide. The UI links the existing official security overview; this PR contains the detailed pairing explanation in repository documentation.

Extension 0.4.2 introduces optional pairing and 0.4.3 removes obsolete migration code. Neither release imposes an enforcement deadline. Unpaired connections retain impersonation risk; this is optional identity verification, not a claim that unpaired access has been secured.

Validation across the final stack:

  • Rust workspace: 1,020 passed, one existing ignored; formatting and strict Clippy.
  • Extension: 3,570 passed, 363 environment-dependent skips; TypeScript, Biome and production build.
  • Five real-daemon tests using the current CLI and published 0.4.1; real Chrome for Testing pairing/navigation smoke.
  • The 0.4.2 stage independently passed 131 focused tests, three real-daemon tests, typecheck and Biome.

Stack 7/9; base: #429. Review order: #424 → #425 → #426 → #427 → #428 → #429 → #430 → #431 → #432.

@iuyo5678
iuyo5678 force-pushed the feat/local-pairing-07-docs branch from c2ea835 to 541b977 Compare November 2, 2026 10:18
@iuyo5678 iuyo5678 changed the title docs: document local pairing and staged rollout docs: explain optional local pairing and independent upgrades Nov 2, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants