@extension.dev/mcp 10.4.1 → 10.4.3

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

package/CHANGELOG.md

@@ -1,5 +1,39 @@
 # Changelog
 
+## 10.4.3
+
+Four truths an agent reads got sharper. A share recorded twice is one
+share, a feature map that points at source without the feature is a lie,
+and a stale corpus snapshot makes both worse.
+
+- `extension_shares` dedupes `localOnly` by artifactId and counts distinct
+  shares in its hint; the append-only record file is untouched and
+  `localRecord` reports entries beside shares so both readings stay
+  available.
+- `add_feature` stops pointing options and devtools at a template that
+  carries neither surface, returning the full plan with an honest note
+  instead of a wrong reference; the vue, svelte and preact sidebar rows
+  point at their real in-framework files. A guard test now validates
+  every mapping against the bundled snapshot.
+- The offline template snapshot moves from the July 16 corpus to the
+  current nightly: 52 templates, the renamed sidebar-monorepo-turborepo,
+  sane surface data.
+- `@extension.dev/urls` moves from 0.3.0 to the published 0.6.0, ending
+  the last published-versus-checkout divergence the provenance guard
+  tracked.
+
+## 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

package/README.md

@@ -149,7 +149,7 @@ The platform tools connect agents to [extension.dev](https://extension.dev): `ex
 | Package | Use it to |
 | --- | --- |
 | [`@extension.dev/skill`](https://www.npmjs.com/package/@extension.dev/skill) | Teach AI agents the judgment half: cross-browser rules, gotchas, playbooks |
-| [`@extension.dev/artifact-integrity`](https://www.npmjs.com/package/@extension.dev/artifact-integrity) | Verify extension artifacts and gate CI on tampered bytes before they ship |
+| [`@extension.dev/artifact-integrity`](https://www.npmjs.com/package/@extension.dev/artifact-integrity) | Check an artifact against a declared SHA-256 and gate CI on the result|
 
 All of it rides on [Extension.js](https://github.com/extension-js/extension.js), the open-source cross-browser extension framework.