refactor: delete dead GET_ADOPTION_MATERIAL/COMPLETE_PAIRING handlers (v4.8.5) Follow-up to the 2026-08-04 Codex Security fixes (v4.8.2): the two handlers had zero legitimate senders anywhere in the repo — adoption runs entirely in-background via relay-adoption-bg.ts (direct vault/paired-devices imports), and the Message union made any leftover reference a compile error (tsc clean). Deletion safety verified: - Revocation-lift semantics remain live via repairPairedRevocationOverlaps(), which runs at service-worker boot (entry.ts) and is pinned by paired-devices.test.ts — same 'fresh direct pair clears stale revocation' contract the old handler implemented. - Sync/pairing/mesh regression suites: 11 files / 128 tests green (coordinator, runner, trigger, vault-adapter, static, alarm, settings, mesh-relay-listener, relay-adoption-bg, device-identity, duress-adoption). Removed: both router cases, MessageTypes entries, the handler-only computeVaultId/clearDeviceRevocation imports, and the test that dispatched COMPLETE_PAIRING. PRIVILEGED_MESSAGE_TYPES retains the four destructive types + COMPLETE_FIREFOX_PASSKEY_CREATE.
$ koh steal kepr.uk/peach-browser@41b6448ed641
·
parent: 04d0a0603b19
discussion
log in to leave a comment.