entry.ts

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 { applyStorageHardening, 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 {19  drainAndRefreshLockedSyncSpool,20  refreshLockedSyncSpool,21} from "./sync-vault-adapter";22import { setLockedSyncHooks } from "./vault";23import { repairPairedRevocationOverlaps } from "./paired-devices";24import {25  requestMeshRelayReconcile,26  selectProductionDialTargets,27  setupMeshRelayListener,28} from "./mesh-relay-listener";29import { hardenExtensionStorage } from "./storage-access";3031// Keep alive for MV3 service worker32chrome.runtime.onInstalled.addListener(() => {});3334// The chrome.idle.onStateChanged listener lives in ./alarms (the architectural35// home for auto-lock timing). Keeping it in only one place avoids drift.3637// Lock-on-close via port disconnect. The popup opens a nonce'd port38// ("popup-<uuid>"); when that port disconnects (popup closed), lock if39// lockOnClose is enabled. Previously also declared in the never-bundled40// index.ts (deleted in LV-5) — this is now the single registration.41//42// LV-5: the lock port name carries a per-popup-open random suffix. Another43// extension cannot open ports INTO this extension (onConnectExternal is not44// registered), so the nonce is defense-in-depth — a port named exactly45// "popup" from anything that isn't our popup no longer reliably triggers46// deny-all + lock once the legacy window closes.47const POPUP_PORT_PREFIX = "popup-";4849chrome.runtime.onConnect.addListener((port) => {50  if (!port.name.startsWith(POPUP_PORT_PREFIX)) return;51  port.onDisconnect.addListener(async () => {52    await denyAllPendingPasskeyRequests();53    const s = await ensureSettingsLoaded();54    if (!isUnlocked() || s.lockOnClose !== true) return;55    if (await isRecoveryConfirmPending()) return;56    await lock();57  });58});5960export function start(): void {61  // PB-26-203: establish the storage trust boundary first, then decide62  // whether the session escrow may operate, then restore. The composed63  // promise is handed to the message layer as a gate; the handler itself is64  // still registered synchronously below (MV3 requirement).65  const hardening = hardenExtensionStorage();66  setLockedSyncHooks({67    refresh: refreshLockedSyncSpool,68    afterUnlock: drainAndRefreshLockedSyncSpool,69  });70  // MV3: the chrome.runtime.onMessage listener MUST be registered during the71  // worker's initial SYNCHRONOUS evaluation. If registration is deferred behind72  // an await, a popup/content message that wakes a cold worker is dispatched73  // before the listener exists → "receiving end does not exist", and the popup74  // misreads the failed HAS_VAULT as "no vault" and shows onboarding.75  //76  // So: kick off session-restore, hand its promise to the message layer as a77  // gate, and register the handler synchronously. Unlock-dependent handlers78  // await the gate (see handleMessage), which preserves the SEV-3-B fix — no79  // spurious lock screen — without delaying listener registration.80  const restored = hardening81    .then((h) => applyStorageHardening(h.sessionEscrowAvailable))82    .then(() => restoreFromSession());83  setRestoreReady(restored);84  setupMessageHandler();85  void setupAutoLock();86  setupCommands();87  // HV-2: clipboard auto-clear backstop must survive worker eviction; the88  // listener has to be registered during initial synchronous evaluation so89  // a cold worker woken BY the alarm still handles it.90  setupClipboardClearAlarm();91  void setupPasskeyProxy();92  // Wire the sync production runner into the dispatcher. Without this93  // `triggerSyncIfReachable` is a no-op (the runner slot starts null) — the94  // pairing/transport/coordinator stack ships dormant until this assignment.95  setSyncRunner(productionSyncRunner);96  setSyncDialTargetSelector(selectProductionDialTargets);97  setupMeshRelayListener();98  // 10-minute background sync. Must be registered during initial synchronous99  // evaluation for the same reason as the clipboard alarm: a cold worker100  // woken BY the sync alarm needs the listener already attached. Setup is101  // idempotent — calling it after a SW revival is safe.102  setupSyncAlarm();103  // First dial without waiting for the alarm tick. The runner is wired and104  // the vault is unlocked enough that listPairedDevices works — the in-flight105  // guard inside triggerSyncIfReachable handles the case where another path106  // (e.g. a fresh pairing completing on the same wake) is already running.107  void restored108    .then(() => requestMeshRelayReconcile())109    .then(() => repairPairedRevocationOverlaps())110    .then(() => hydratePersistedSyncState())111    .then(() => triggerSyncIfReachable({ reason: "startup" }))112    .catch(() => undefined);113}114115start();