@farmslot/adapter-web 0.6.5 → 0.6.6

package/CHANGELOG.md

@@ -6,6 +6,12 @@ All notable changes to `@farmslot/adapter-web` are tracked here.
 
 - Active-development baseline; add user-facing changes here before release or package publication.
 
+## 0.6.6 - 2026-10-09
+
+- Fix: Chrome for Testing (`load-extension` mode) now launches with `--enable-unsafe-extension-debugging`, as branded Chrome already did. When the loaded extension called `chrome.runtime.reload()` (the MetaMask webpack dev server does on every background rebuild), Chrome 147 re-registered it as an unpacked extension and disabled it (`DISABLE_UNSUPPORTED_DEVELOPER_EXTENSION`) because developer mode was off. The disable was saved in the slot profile, so every later launch showed `<id> is blocked` (`ERR_BLOCKED_BY_CLIENT`). The flag only prevents this. A profile that is already disabled stays disabled when relaunched with it.
+- Fix: every fresh launch drops the profile's stored extension service worker registration (`Default/Service Worker/Database`, `ScriptCache`), so Chrome runs the background from the loaded build instead of whichever build first registered it. Extension storage and Cache Storage are kept.
+- Publish with adapter-sdk 0.8.2 and recipe-runner 0.28.2 so consumers share one adapter-sdk and one recipe-runner copy.
+
 ## 0.6.5 - 2026-10-09
 
 - A test now pins the web HUD limits that untrusted recipe sources rely on, now that `run` shows the HUD for them: recipe text capped at 180 characters and drawn as text in the closed shadow root, beside the RUN badge and the `step n/m` label. No behavior change.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@farmslot/adapter-web",
-  "version": "0.6.5",
+  "version": "0.6.6",
   "description": "Web platform adapter for Farmslot recipes: resolve and launch an isolated Chromium, own its CDP port, load unpacked extensions, and keep macOS focus.",
   "type": "commonjs",
   "exports": {
@@ -83,8 +83,8 @@
     "prepublishOnly": "node ../../scripts/quality/check-farmslot-package-readiness.mjs --publish --packages @farmslot/adapter-web"
   },
   "dependencies": {
-    "@farmslot/adapter-sdk": "0.8.1",
-    "@farmslot/recipe-runner": "0.28.1",
+    "@farmslot/adapter-sdk": "0.8.2",
+    "@farmslot/recipe-runner": "0.28.2",
     "ws": "^8.18.0"
   },
   "devDependencies": {

package/src/browser-resolver.cjs

@@ -309,7 +309,14 @@ function extensionLaunchArgs(extensionDir, extensionLoading) {
     // line: runtime ownership checks match the loaded dist by this flag.
     return [...BRANDED_CHROME_ARGS, `--load-extension=${extensionDir}`];
   }
-  return [`--disable-extensions-except=${extensionDir}`, `--load-extension=${extensionDir}`];
+  return [
+    // chrome.runtime.reload() re-registers the extension as kUnpacked, which
+    // Chrome 147+ disables (DISABLE_UNSUPPORTED_DEVELOPER_EXTENSION, persisted in
+    // the profile) unless developer mode is on or this flag is set.
+    '--enable-unsafe-extension-debugging',
+    `--disable-extensions-except=${extensionDir}`,
+    `--load-extension=${extensionDir}`,
+  ];
 }
 
 function browserMode(env = process.env) {

package/src/launch-browser.cjs

@@ -187,6 +187,15 @@ function runLaunch(opts, acquireLock) {
   // the profile (fixture prefill into LevelDB) needs it unlocked first; a prior
   // run's Chrome would hold the lock and the write fails.
   if (opts.stopOnly) return { stopped: true };
+  try {
+    removeExtensionWorkerRegistrations(profile);
+  } catch (error) {
+    const detail = error instanceof Error ? error.message : String(error);
+    throw new Error(
+      `Failed to drop stale extension worker registrations under ${profile}: ${detail}. ` +
+        `Next: fix owner permissions, then ${rerun}`,
+    );
+  }
 
   const requestedProfileQuarantined = hasDetachedLaunchUnproven(profile);
   const portQuarantine = readValidationPortQuarantine(cdpPort);
@@ -708,6 +717,19 @@ function removeProfileSingletonLocks(profile) {
   }
 }
 
+// A preserved profile keeps the extension's service worker registration,
+// scripts included. Registering the same script URL again is a no-op, so after
+// a rebuild or a version bump Chrome kept running the background of whatever
+// build first registered it. Every fresh launch drops the stored registrations
+// and Chrome registers the worker from the loaded files. Extension storage and
+// Cache Storage live elsewhere and are kept.
+function removeExtensionWorkerRegistrations(profile) {
+  const workerDir = path.join(profile, 'Default', 'Service Worker');
+  for (const name of ['Database', 'ScriptCache']) {
+    fs.rmSync(path.join(workerDir, name), { recursive: true, force: true });
+  }
+}
+
 function extensionPageUrl(extensionDir, page) {
   if (!page) return '';
   const id = extensionIdFromExtensionDir(extensionDir);