entry.ts

4.7 KB · raw

1import { setupMessageHandler, setRestoreReady } from "./messages";2import { setupAutoLock } from "./alarms";3import { setupSyncAlarm } from "./sync-alarm";4import { setupPasskeyProxy } from "./passkey";5import { setupCommands } from "./commands";6import { setupClipboardClearAlarm } from "./clipboard";7import { restoreFromSession, isUnlocked, lock } from "./vault";8import { ensureSettingsLoaded } from "./vault";9import { isRecoveryConfirmPending } from "./recovery-pending";10import { denyAllPendingPasskeyRequests } from "./passkey";11import {12  hydratePersistedSyncState,13  setSyncDialTargetSelector,14  setSyncRunner,15  triggerSyncIfReachable,16} from "./sync-trigger";17import { productionSyncRunner } from "./sync-runner";18import { repairPairedRevocationOverlaps } from "./paired-devices";19import {20  requestMeshRelayReconcile,21  selectProductionDialTargets,22  setupMeshRelayListener,23} from "./mesh-relay-listener";2425// Keep alive for MV3 service worker26chrome.runtime.onInstalled.addListener(() => {});2728// The chrome.idle.onStateChanged listener lives in ./alarms (the architectural29// home for auto-lock timing). Keeping it in only one place avoids drift.3031// Lock-on-close via port disconnect. The popup opens a nonce'd port32// ("popup-<uuid>"); when that port disconnects (popup closed), lock if33// lockOnClose is enabled. Previously also declared in the never-bundled34// index.ts (deleted in LV-5) — this is now the single registration.35//36// LV-5: the lock port name carries a per-popup-open random suffix. Another37// extension cannot open ports INTO this extension (onConnectExternal is not38// registered), so the nonce is defense-in-depth — a port named exactly39// "popup" from anything that isn't our popup no longer reliably triggers40// deny-all + lock once the legacy window closes.41const POPUP_PORT_PREFIX = "popup-";4243chrome.runtime.onConnect.addListener((port) => {44  // Accept legacy bare "popup" for one release so an in-flight popup from the45  // previous version straddling the update doesn't lose lock-on-close.46  // TODO(2026-Q3): drop the bare "popup" acceptance once v3.8.0 has rolled out.47  if (port.name !== "popup" && !port.name.startsWith(POPUP_PORT_PREFIX)) return;48  port.onDisconnect.addListener(async () => {49    await denyAllPendingPasskeyRequests();50    const s = await ensureSettingsLoaded();51    if (!isUnlocked() || s.lockOnClose === false) return;52    if (await isRecoveryConfirmPending()) return;53    lock();54  });55});5657export function start(): void {58  // MV3: the chrome.runtime.onMessage listener MUST be registered during the59  // worker's initial SYNCHRONOUS evaluation. If registration is deferred behind60  // an await, a popup/content message that wakes a cold worker is dispatched61  // before the listener exists → "receiving end does not exist", and the popup62  // misreads the failed HAS_VAULT as "no vault" and shows onboarding.63  //64  // So: kick off session-restore, hand its promise to the message layer as a65  // gate, and register the handler synchronously. Unlock-dependent handlers66  // await the gate (see handleMessage), which preserves the SEV-3-B fix — no67  // spurious lock screen — without delaying listener registration.68  const restored = restoreFromSession();69  setRestoreReady(restored);70  setupMessageHandler();71  void setupAutoLock();72  setupCommands();73  // HV-2: clipboard auto-clear backstop must survive worker eviction; the74  // listener has to be registered during initial synchronous evaluation so75  // a cold worker woken BY the alarm still handles it.76  setupClipboardClearAlarm();77  void setupPasskeyProxy();78  // Wire the sync production runner into the dispatcher. Without this79  // `triggerSyncIfReachable` is a no-op (the runner slot starts null) — the80  // pairing/transport/coordinator stack ships dormant until this assignment.81  setSyncRunner(productionSyncRunner);82  setSyncDialTargetSelector(selectProductionDialTargets);83  setupMeshRelayListener();84  // 10-minute background sync. Must be registered during initial synchronous85  // evaluation for the same reason as the clipboard alarm: a cold worker86  // woken BY the sync alarm needs the listener already attached. Setup is87  // idempotent — calling it after a SW revival is safe.88  setupSyncAlarm();89  // First dial without waiting for the alarm tick. The runner is wired and90  // the vault is unlocked enough that listPairedDevices works — the in-flight91  // guard inside triggerSyncIfReachable handles the case where another path92  // (e.g. a fresh pairing completing on the same wake) is already running.93  void restored94    .then(() => requestMeshRelayReconcile())95    .then(() => repairPairedRevocationOverlaps())96    .then(() => hydratePersistedSyncState())97    .then(() => triggerSyncIfReachable({ reason: "startup" }))98    .catch(() => undefined);99}100101start();