Skip to content

feat(daemon): persist and manage local browser pairings - #425

Open
iuyo5678 wants to merge 2 commits into
feat/local-pairing-01-protocolfrom
feat/local-pairing-02-store
Open

iuyo5678 wants to merge 2 commits into
feat/local-pairing-01-protocolfrom
feat/local-pairing-02-store

Conversation

@iuyo5678

@iuyo5678 iuyo5678 commented Oct 13, 2026 •

Copy link
Copy Markdown
Collaborator

Add durable local pairing records and maintenance commands for pairing, replacement, devices, revocation, rotation and explicit trust policy. Pairing is optional by default.

bsk daemon pair now reuses or starts a reachable daemon before printing its link, honoring BSK_AUTO_START=0 for managed hosts. Other maintenance commands keep lifecycle-lock-protected offline operations. Atomic private writes, in-process serialization and deterministic startup/contention coverage remain; redundant per-file locks are omitted.

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 2/9; base: #424. Review order: #424 → #425 → #426 → #427 → #428 → #429 → #430 → #431 → #432.

@iuyo5678
iuyo5678 force-pushed the feat/local-pairing-02-store branch from 10cc0f3 to e67761c Compare November 2, 2026 10:18

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