@extension.dev/mcp 10.10.10 → 10.10.12

package/.claude-plugin/marketplace.json

@@ -10,7 +10,7 @@
       "name": "extension-mcp",
       "source": "./",
       "description": "MCP tools for browser extension development: scaffold from 50+ templates, run the dev server with HMR, inspect the live DOM and logs, and publish store-ready builds for Chrome, Edge, and Firefox.",
-      "version": "10.10.10",
+      "version": "10.10.12",
       "category": "development",
       "author": {
         "name": "Cezar Augusto"

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "extension-mcp",
   "description": "MCP tools for browser extension development: scaffold from 50+ templates, run the dev server with HMR, inspect the live DOM and logs, and publish store-ready builds for Chrome, Edge, and Firefox. Ships /extension, /extension-add, /extension-debug, and /extension-publish commands.",
-  "version": "10.10.10",
+  "version": "10.10.12",
   "author": {
     "name": "Cezar Augusto",
     "email": "hello@extension.dev",

package/CHANGELOG.md

@@ -1,5 +1,49 @@
 # Changelog
 
+## 10.10.12
+
+- `extension_stop` on Windows reads the Windows process table to find what
+  is left of a session, so a stop that ended the whole tree says
+  `stopped` instead of "survivors were not verified". Before this, every
+  Windows stop answered `stopped: false`, and `extension_dev` with
+  `replace: true` refused every time. A stop still says unverified when
+  the table cannot be read. Measured on a Windows runner.
+- The lockfile raises `proxy-addr`, `source-map-js` and Vue past their
+  open advisories.
+
+## 10.10.11
+
+The rest of the 2026-10-05 audit ledger, apart from the Safari WebDriver
+fields that wait on the engine (entry 110h, Extension.js BUGS_TO_FIX 905).
+
+- `extension_eval` says where it ran and what came back: the tab's url and
+  title on Firefox, a note when the value was not serializable, only real
+  background targets as the background, and `eval-lost` or
+  `eval-unsupported` when the answer never arrived. A woken worker is no
+  longer said to have idled when it may never have started.
+- `extension_logs` and `extension_assert` report a cut stream: a follow
+  that closed early is a partial read, dropped-line markers are not
+  counted as events, and console-errors-empty is inconclusive when lines
+  were dropped. An unknown console `context` is refused as a bad request
+  instead of failing the whole call.
+- `extension_wait` and `extension_start` report only what they observed:
+  a start session is `build-ready`, a build contract or a stopped session
+  is `no-session`, and start refuses Safari and preview-path hosts it
+  cannot serve.
+- `extension_open` names the DevTools panel frame that appeared, and says
+  when the panel registry could not be read or the target was inferred.
+- Platform answers of the wrong shape (channels, build index, shares,
+  login config) are unreadable, never empty, and an unpinned publish
+  matches the build the platform named.
+- `extension_stop` counts a process as reaped only once it is gone, and
+  ends a Windows session through `taskkill /T /F`. A session marker that
+  could not be written is a warning on the started answer, and the
+  `release promote` command exits non-zero on an answer it cannot read.
+- `extension_list_extensions` on Firefox marks a lone temporary add-on as
+  an inferred match.
+- The scheduled test tier builds through the real pinned engine with
+  `--output json` and checks the fixtures against what it writes.
+
 ## 10.10.10
 
 Every sentence the server says is now backed by something it read

package/README.md

@@ -151,7 +151,7 @@ Two flags (or environment variables) narrow the server before an agent sees it:
 
 A refused call answers `E_TOOL_DISABLED` with the flag to change.
 
-A real store submission, a promotion to stable and a share revoke also wait for a person by default: the first call answers `approval-required` with a link on extension.dev, a workspace member approves exactly that action, and the same call with the returned `approvalId` runs it once. `EXTENSION_DEV_APPROVAL_GATE=1` extends this to every promotion; `EXTENSION_DEV_APPROVAL_GATE=0` turns it off.
+A real store submission, a promotion to stable and a share revoke also wait for a person by default: the first call answers `approval-required` with a link on extension.dev, a workspace member approves exactly that action (a store submission needs a workspace owner), and the same call with the returned `approvalId` runs it once. `EXTENSION_DEV_APPROVAL_GATE=1` extends this to every promotion; `EXTENSION_DEV_APPROVAL_GATE=0` turns it off.
 
 Every tool also carries MCP annotations (`readOnlyHint`, `destructiveHint`, `idempotentHint`, `openWorldHint`), so clients can auto-approve reads and ask before the rest.
 
@@ -304,7 +304,7 @@ Extension.js release records one, and that leg reads `skip`.
 
 ## Sharing a build in progress
 
-An unpacked extension is unusually hard to hand to someone: the only way to look at a colleague's work-in-progress has been to take their zip and run untrusted code with real browser permissions on your own machine. `extension_preview_web` with `share: true` uploads the `dist/` it just built and returns a link that renders those exact bytes in the emulator. Whoever opens it installs nothing and signs in to nothing, which is what lets a designer, a PM, or a reviewer into the loop at all. Those bytes run in an isolated sandbox origin or they do not run at all: preview refuses a shared build rather than serving it in its own renderer. Sharing needs auth (`extension_auth` or `EXTENSION_DEV_TOKEN`), the link lives 30 days, and `DELETE`ing the returned `revokeUrl` with the same token kills it early. Re-sharing an unchanged build returns that same link rather than a second one, and only a revoked link is replaced by a different one, because revocation is permanent: the address is burned and never resolves again. That makes `revokeUrl` the handle to the link you just made, so every share is also appended to `.extension.dev/shared-previews.json` in the project (gitignored) so it survives losing the tool output. The upload holds up to 2,000 files and about 64MB of text, or roughly 48MB when the build is mostly images, fonts or wasm, which travel base64-encoded. Without `share`, the tool returns a local-only deep link and uploads nothing.
+An unpacked extension is unusually hard to hand to someone: the only way to look at a colleague's work-in-progress has been to take their zip and run untrusted code with real browser permissions on your own machine. `extension_preview_web` with `share: true` uploads the `dist/` it just built and returns a link that renders those exact bytes in the emulator. Whoever opens it installs nothing and signs in to nothing, which is what lets a designer, a PM, or a reviewer into the loop at all. Those bytes run in an isolated sandbox origin or they do not run at all: preview refuses a shared build rather than serving it in its own renderer. Sharing needs auth (`extension_auth` or `EXTENSION_DEV_TOKEN`), the link lives for the workspace plan's share window (30 days on Free, longer on Pro) and the answer carries its exact `expiresAt`, and `DELETE`ing the returned `revokeUrl` with the same token kills it early. Re-sharing an unchanged build returns that same link rather than a second one, and only a revoked link is replaced by a different one, because revocation is permanent: the address is burned and never resolves again. That makes `revokeUrl` the handle to the link you just made, so every share is also appended to `.extension.dev/shared-previews.json` in the project (gitignored) so it survives losing the tool output. The upload holds up to 2,000 files and about 64MB of text, or roughly 48MB when the build is mostly images, fonts or wasm, which travel base64-encoded. Without `share`, the tool returns a local-only deep link and uploads nothing.
 
 `extension_shares` is the other half of that: it lists every link the token has shared, live and dead, with the `previewUrl` and `revokeUrl` of each, and revokes one by `artifactId` or by pasting any of its URLs. Pass `projectPath` and it reconciles the platform's answer with the project's own record, so a link shared from another machine shows up as `remoteOnly` and a record with nothing behind it any more shows up under `localOnly`. It never rewrites the local file.
 

package/claude/rules/mcp-tools.md

@@ -33,7 +33,7 @@ Run a test stage against a live dev session: state expectations and read one ver
 | `projectPath` | string | yes |  | Extension project root (needs a live dev session) |
 | `expect` | array of object | yes |  | One object per expectation, each { assert: <check id>, ...args }. background-worker-booted: no args. surface-rendered: surface (popup, options, sidebar, newtab, history, bookmarks), optional selector and minNodes. content-script-injected: url. storage-key-present: key, optional area (default local), equals, context. console-errors-empty: optional context (array), since (seq cursor), ignore (substrings). |
 | `browser` | string | no |  | Session browser; defaults to this project's live session |
-| `timeout` | number | no |  | Command timeout in ms (default 5000) |
+| `timeout` | number | no |  | Command timeout in ms. When omitted, the default depends on the route: 30000 through the dev session's control channel, 10000 over the Firefox debugger protocol, and 15000 per command over the Chromium debug port. |
 
 ## extension_auth
 
@@ -148,11 +148,11 @@ Take a shallow structured DOM snapshot of one chosen surface through the agent b
 | `maxBytes` | number | no | `262144` |  |
 | `withConsole` | number \| boolean | no |  | Also include recent console lines. A number is how many; true means 50. |
 | `browser` | string | no |  | Session browser; defaults to this project's live session |
-| `timeout` | number | no |  | Command timeout in ms (default 5000) |
+| `timeout` | number | no |  | Command timeout in ms. When omitted, the default depends on the route: 30000 through the dev session's control channel, 10000 over the Firefox debugger protocol, and 15000 per command over the Chromium debug port. |
 
 ## extension_eval
 
-Evaluate an expression in a running extension context. Start the session with allowEval:true (extension_dev), which writes a 0600 session token; without that token every route of this tool, the debug port included, answers eval-disabled. Context defaults to 'background', except on a Chromium MV3 session (the default template) where it defaults to 'page', the active tab, because the MV3 service worker CSP blocks eval; pass context:'background' to target the worker anyway and get that explanation back. For content and page, pass `url` to pick the tab, or omit both `url` and `tab` for the active tab; a numeric `tab` only disambiguates. Extension surfaces (popup, options, sidebar, devtools) and override pages (newtab, history, bookmarks) need no tab id but must already be open: open one with extension_open first, because a closed one returns an explicit error. On a Chromium MV3 session those pages, and context:'page' with a chrome-extension:// url, evaluate over CDP, the inspector path the extension page CSP does not govern; elsewhere they evaluate over the in-bundle relay. On Firefox a document whose content security policy forbids eval (the extension's own pages, or a site's) is evaluated over the debugger protocol instead, which takes one expression; a page inside the extension that is no declared surface (pages/*) is reached the same way by context:'page' and its moz-extension:// url once a tab shows it. Call extension_dom_snapshot with listTabs:true to enumerate {tabId, url, title}.
+Evaluate an expression in a running extension context. Start the session with allowEval:true (extension_dev), which writes a 0600 session token; without that token every route of this tool, the debug port included, answers eval-disabled. Context defaults to 'background', except on a Chromium MV3 session (the default template) where it defaults to 'page', the active tab; pass context:'background' to evaluate in the service worker, which on Chromium goes over the debug port. Debug-port evaluates run with a user gesture, so gesture-gated APIs (permissions.request, sidePanel.open) can succeed here and still fail when the extension's own code calls them. For content and page, pass `url` to pick the tab, or omit both `url` and `tab` for the active tab; a numeric `tab` only disambiguates. Extension surfaces (popup, options, sidebar, devtools) and override pages (newtab, history, bookmarks) need no tab id but must already be open: open one with extension_open first, because a closed one returns an explicit error. On a Chromium MV3 session those pages, and context:'page' with a chrome-extension:// url, evaluate over CDP, the inspector path the extension page CSP does not govern; elsewhere they evaluate over the in-bundle relay. On Firefox a document whose content security policy forbids eval (the extension's own pages, or a site's) is evaluated over the debugger protocol instead, which takes one expression; a page inside the extension that is no declared surface (pages/*) is reached the same way by context:'page' and its moz-extension:// url once a tab shows it. Call extension_dom_snapshot with listTabs:true to enumerate {tabId, url, title}.
 
 | input | type | required | default | description |
 | --- | --- | --- | --- | --- |
@@ -162,7 +162,7 @@ Evaluate an expression in a running extension context. Start the session with al
 | `url` | string | no |  | content/page: pick the tab by url (match pattern, then substring). Preferred over `tab`. |
 | `tab` | number | no |  | Numeric chrome.tabs id, only to disambiguate when several tabs match. |
 | `browser` | string | no |  | Session browser; defaults to this project's live session |
-| `timeout` | number | no |  | Command timeout in ms (default 5000) |
+| `timeout` | number | no |  | Command timeout in ms. When omitted, the default depends on the route: 30000 through the dev session's control channel, 10000 over the Firefox debugger protocol, and 15000 per command over the Chromium debug port. |
 
 ## extension_inspect
 
@@ -232,7 +232,7 @@ Open an extension surface, or replay an event, in a running session. Pass surfac
 | `tab` | number | no |  | With `url`: navigate this chrome.tabs id in place instead of opening a new tab (rides the engine's navigate verb, so the session needs allowControl: true). Without it an existing page is never taken over. |
 | `asTab` | boolean | no | `false` | popup/options/sidebar: render the surface's document in a real tab instead of a popup window. This is how you inspect a surface HEADLESSLY, and it is applied automatically when a headless session refuses to open one. Same page and APIs, but no popup sizing and window.close() closes the tab. |
 | `browser` | string | no |  | Session browser; defaults to this project's live session |
-| `timeout` | number | no |  | Command timeout in ms (default 5000) |
+| `timeout` | number | no |  | Command timeout in ms. When omitted, the default depends on the route: 30000 through the dev session's control channel, 10000 over the Firefox debugger protocol, and 15000 per command over the Chromium debug port. |
 
 ## extension_preview_web
 
@@ -319,7 +319,7 @@ Reload a running extension's background context, or a tab. Start the session wit
 | `context` | "background" \| "content" \| "page" | no | `"background"` |  |
 | `tab` | number | no |  | For content/page: a specific tab id |
 | `browser` | string | no |  | Session browser; defaults to this project's live session |
-| `timeout` | number | no |  | Command timeout in ms (default 5000) |
+| `timeout` | number | no |  | Command timeout in ms. When omitted, the default depends on the route: 30000 through the dev session's control channel, 10000 over the Firefox debugger protocol, and 15000 per command over the Chromium debug port. |
 
 ## extension_shares
 
@@ -347,8 +347,8 @@ Run the PRODUCTION build in a browser: build the project, serve it, and launch.
 | `browser` | "chrome" \| "chromium" \| "edge" \| "brave" \| "opera" \| "vivaldi" \| "yandex" \| "firefox" \| "waterfox" \| "librewolf" \| "zen" \| "floorp" \| "safari" \| "chromium-based" \| "gecko-based" \| "firefox-based" \| "webkit-based" | no | `"chrome"` |  |
 | `build` | boolean | no | `true` | Build before serving. false serves the existing dist/<browser> as-is and fails when there is none. |
 | `polyfill` | boolean | no | `true` | Apply cross-browser polyfill (build only) |
-| `port` | number | no |  | Server port (0 for auto-assign) |
-| `noBrowser` | boolean | no | `false` | Serve without launching a browser |
+| `port` | number | no |  | Passed to the engine as --port (0 for auto-assign). A production start serves nothing over it today; it matters only to a toolchain that reads it. |
+| `noBrowser` | boolean | no | `false` | Build (or, with build:false, check the dist) without launching a browser. A production start serves nothing, so with no browser the engine process ends once the build does; read the result with extension_build rather than a session. |
 | `outputPath` | string | no |  | An existing unpacked extension directory to launch as it is (a manifest.json at its root), for an artifact built by another toolchain or an exact release candidate. Implies build:false; projectPath still names the project the session belongs to. Relative paths resolve against projectPath. |
 | `profile` | string | no |  | Profile path, or "false" to reuse the real user profile. Omit for a throwaway one. |
 | `startingUrl` | string | no |  | URL the browser opens on launch |
@@ -381,7 +381,7 @@ Read or write chrome.storage in a running extension. Every call runs in the exte
 | `key` | string | no |  | Key to get or set |
 | `value` | any | no |  | Value to set (any JSON value); required for action=set |
 | `browser` | string | no |  | Session browser; defaults to this project's live session |
-| `timeout` | number | no |  | Command timeout in ms (default 5000) |
+| `timeout` | number | no |  | Command timeout in ms. When omitted, the default depends on the route: 30000 through the dev session's control channel, 10000 over the Firefox debugger protocol, and 15000 per command over the Chromium debug port. |
 
 ## extension_submit