@extension.dev/mcp 10.4.0 → 10.4.2

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.4.0",
+      "version": "10.4.2",
       "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.4.0",
+  "version": "10.4.2",
   "author": {
     "name": "Cezar Augusto",
     "email": "hello@extension.dev",

package/CHANGELOG.md

@@ -1,5 +1,36 @@
 # Changelog
 
+## 10.4.2
+
+The engine moved twice in a day and the agent lane has to move with it.
+`extension-develop` 4.0.30 carries the MAIN-world public path fix: a
+content script running in the page's own world now resolves extension
+assets through the isolated-world bridge base instead of falling back to
+the host page, where it 404'd.
+
+- `extension-create`, `extension-develop` and `extension-install` move
+  from 4.0.29 to 4.0.30. The nightly `engine-pin` job added in 10.4.1 is
+  what would have caught this drift; the bump is the first it prompted.
+
+## 10.4.1
+
+The engine this server spawns had drifted nine releases behind the one a
+human gets from `npx extension@latest`. Agents were building on 4.0.20
+while the published CLI was 4.0.29, so every engine fix in that range was
+missing from the agent lane, including both theme-colour conversions
+shipped this week: a `theme.colors` project a human built green still
+failed when an agent built it. Nothing in this repository changed when
+the engine shipped, which is why it went unnoticed until a walk of the
+MCP journey read `extension_doctor` closely.
+
+- `extension-create`, `extension-develop` and `extension-install` move
+  from 4.0.20 to 4.0.29, so the agent lane spawns the engine npm serves.
+- A nightly `engine-pin` job now reads npm rather than the working tree
+  and fails when a pin trails the published engine, when a pin is a range
+  or a dist tag, or when it is missing. It sits beside the existing
+  registry-listing watch, because the event that invalidates both happens
+  in another repository.
+
 ## 10.4.0
 
 Every place a tool named a template, it pointed the caller at GitHub and

package/dist/module.js

@@ -582,7 +582,7 @@ __webpack_require__.d(wait_namespaceObject, {
     handler: ()=>wait_handler,
     schema: ()=>wait_schema
 });
-var package_namespaceObject = JSON.parse('{"rE":"10.4.0","El":{"OP":"4.0.20"}}');
+var package_namespaceObject = JSON.parse('{"rE":"10.4.2","El":{"OP":"4.0.30"}}');
 const ENVELOPE_SCHEMA = 1;
 const collectWarnings = (warnings)=>{
     if (!warnings) return [];
@@ -1330,7 +1330,7 @@ function parseBuildIndex(json) {
 }
 const DEFAULT_MEDIA_ORIGIN = "https://media.extension.land";
 const DEFAULT_CHANNEL = "latest";
-const PINNED_COMMIT = "52c0d871c433d9c54878767175ce8ffc9a951756";
+const PINNED_COMMIT = "f7f4e6efb56a7e5ae08d58dbff3972d94af7d021";
 const CHANNEL_CACHE_TTL_MS = 300000;
 function mediaOrigin() {
     return (process.env.EXTENSION_MEDIA_ORIGIN || "").trim() || DEFAULT_MEDIA_ORIGIN;

package/dist/src/lib/template-artifact-source.d.ts

@@ -1,4 +1,4 @@
-export declare const PINNED_COMMIT = "52c0d871c433d9c54878767175ce8ffc9a951756";
+export declare const PINNED_COMMIT = "f7f4e6efb56a7e5ae08d58dbff3972d94af7d021";
 export type TemplateCatalogUtmSource = "mcp" | "mcp-create";
 export declare function templateCatalogUrl(slug: string, utmSource?: TemplateCatalogUtmSource): string;
 export declare function templateMetaUrls(): Promise<string[]>;

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@extension.dev/mcp",
   "type": "module",
-  "version": "10.4.0",
+  "version": "10.4.2",
   "description": "MCP server that lets AI agents (Claude Code, Claude Desktop, Cursor, Copilot, Codex) build, run, inspect, and publish browser extensions. 28 tools for scaffolding, live DOM inspection, log streaming, and store-ready builds across Chrome, Edge, Firefox, Safari, and every Chromium- or Gecko-based browser (Brave, Opera, Vivaldi, Yandex, Waterfox, LibreWolf). Powered by extension.dev and Extension.js.",
   "mcpName": "io.github.extensiondev/mcp",
   "license": "Apache-2.0",
@@ -89,9 +89,9 @@
     "@modelcontextprotocol/sdk": "^1.12.1",
     "browser-extension-manifest-fields": "^2.2.9",
     "cross-spawn": "^7.0.6",
-    "extension-create": "4.0.20",
-    "extension-develop": "4.0.20",
-    "extension-install": "4.0.20",
+    "extension-create": "4.0.30",
+    "extension-develop": "4.0.30",
+    "extension-install": "4.0.30",
     "ws": "^8.20.0"
   },
   "devDependencies": {

package/server.json

@@ -7,13 +7,13 @@
     "source": "github"
   },
   "websiteUrl": "https://extension.dev",
-  "version": "10.4.0",
+  "version": "10.4.2",
   "packages": [
     {
       "registryType": "npm",
       "registryBaseUrl": "https://registry.npmjs.org",
       "identifier": "@extension.dev/mcp",
-      "version": "10.4.0",
+      "version": "10.4.2",
       "runtimeHint": "npx",
       "transport": {
         "type": "stdio"