@extension.dev/mcp 5.3.1 → 5.5.0

package/.claude-plugin/marketplace.json

@@ -10,7 +10,7 @@
       "name": "extension-mcp",
       "source": "./",
       "description": "MCP tools for browser extension development: scaffold from 60+ templates, run the dev server with HMR, inspect the live DOM and logs, and publish store-ready builds for Chrome, Edge, and Firefox.",
-      "version": "5.3.1",
+      "version": "5.5.0",
       "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 60+ 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": "5.3.1",
+  "version": "5.5.0",
   "author": {
     "name": "Cezar Augusto",
     "email": "boss@cezaraugusto.net",

package/CHANGELOG.md

@@ -1,5 +1,94 @@
 # Changelog
 
+## 5.5.0
+
+The debug surfaces learn to point at things: tabs are targetable by
+URL, extensions in lists have names, and eval works on the default
+template by default.
+
+### Added
+
+- `extension_dom_inspect` targets tabs by `tabUrl` (case-insensitive
+  URL substring, title as fallback). Exactly one match inspects it and
+  the result names the resolved target; zero or multiple matches return
+  the candidate targets instead of guessing. `listTargets: true` lists
+  the browser's live CDP page targets (targetId, url, title, type) with
+  the standing warning that a CDP targetId is NOT a chrome.tabs id.
+- `extension_list_extensions` names its entries. The dev session's own
+  extension resolves to `name`, `version`, and `ownExtension: true`
+  (identified by recomputing Chrome's unpacked-extension id from the
+  ready contract's distPath) and sorts first; entries that cannot be
+  resolved carry a note saying why instead of a silent bare id. Other
+  extensions' contexts are never attached to or evaluated in.
+
+### Fixed
+
+- `extension_eval` works on the default template by default. On
+  Chromium with an MV3 manifest the default context is now `page` (the
+  MV3 service worker CSP blocks background eval), disclosed in the
+  result as `defaultedContext` with the reason; explicit
+  `context: "background"` is unchanged and keeps its CSP explanation.
+  Firefox and MV2 defaults are untouched. A defaulted eval that lands
+  on an unreachable active tab returns a hint to navigate or pass
+  `url`/`tab`.
+- Error remedies speak tool arguments, never CLI flags: the engine's
+  `--context page --tab <id>` prose is rewritten into `context:`/
+  `tab:`/`url:` vocabulary, with guards so ordinary prose is never
+  garbled by the rewriting.
+- The debugging documentation's headline example now runs on the
+  default template (page-context eval); the background variant is
+  labeled MV2/Firefox, and the cross-browser matrix states per-context
+  eval support honestly with the MV3 CSP footnote.
+
+## 5.4.0
+
+The DevX swarm's non-blocker friction clusters, cleared: waiting is
+narrated, ports tell the truth, artifacts say where they are, and error
+prose explains the extension instead of the engine.
+
+### Added
+
+- `extension_wait` narrates its budget. `timeoutMs` is a documented
+  argument (default 45000, clamped 1000 to 50000; the legacy `timeout`
+  spelling stays as a deprecated alias), every result carries `budgetMs`
+  and `elapsedMs`, and a timeout says what WAS observed plus a
+  call-again hint instead of an opaque failure. The status splits
+  `compiled` from `browserAttached`, and a `noBrowser` build-only
+  session returns immediately with `buildOnly: true` and a plain
+  statement that no browser will ever attach.
+- `extension_build` with `zip: true` returns `zipPath`, the absolute
+  path of the file the engine actually wrote (its name sanitizer strips
+  punctuation, so the filename rarely matches the project name), and
+  `zipSourcePath` for `zipSource: true`. When a zip cannot be located
+  after a successful build the result says so in `zipPathNote` instead
+  of omitting the field silently.
+
+### Fixed
+
+- `extension_dev` reports the actually-bound port. The engine's
+  ready.json carries the bound port from its first stamp, so dev reads
+  it after the health window and re-registers the session with the true
+  port; when the stamp has not landed yet, dev claims no port at all
+  and says `extension_wait` reports the bound one. dev and wait now
+  share one source of truth and cannot disagree about the same session.
+- `extension_build` warns when it writes over a live dev session's
+  dist: the dev browser may serve the production artifact until the
+  next recompile. The build is never blocked; the clobber is named.
+- `extension_inspect` classifies `.zip` files as archives and excludes
+  them from `shippableSize` and the 10MB store gate (the package is not
+  payload), with an `archiveNote` explaining the exclusion.
+- `extension_whoami` anchors its identity to the stored token that
+  `extension_login` minted: it does not follow the current working
+  directory, and the wording now says so.
+- `extension_open` explains a popup-less extension instead of relaying
+  the engine error: a manifest pre-check reports that nothing sets
+  `action.default_popup`, lists the surfaces the manifest DOES declare,
+  and points at the right next verb. Headless popup errors state the
+  exact headed path (`extension_dev` with `replace: true` and
+  `EXTENSION_HEADLESS=0`).
+- `extension_dev`'s `earlyOutput` drops V8 asm.js verdict lines (pure
+  noise); real errors are preserved.
+
 ## 5.3.1
 
 ### Added