[ forgesworn/bark ] fix: handle service worker restart and add request timeouts
The content script was permanently marking the extension as stale when
the MV3 service worker was merely asleep, not invalidated. Now retries
up to 3 times with 500ms delays for "does not exist" errors, only
marking stale on genuine "context invalidated". Provider requests get
a 60s timeout so promises never hang forever. A chrome.alarms keepalive
prevents the service worker from dying while a NIP-46 connection is
active.

GitHub
fix: handle service worker restart and add request timeouts · forgesworn/bark@255e122
The content script was permanently marking the extension as stale when
the MV3 service worker was merely asleep, not invalidated. Now retries
up to...