@extension.dev/mcp 9.0.0 → 10.0.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": "9.0.0",
+      "version": "10.0.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": "9.0.0",
+  "version": "10.0.0",
   "author": {
     "name": "Cezar Augusto",
     "email": "hello@extension.dev",

package/CHANGELOG.md

@@ -1,5 +1,52 @@
 # Changelog
 
+## 10.0.0
+
+Every tool now returns the same frame. Before this, 28 tools hand-built 142
+different JSON shapes: `ok` appeared on 71 of them, `error` on 67, `hint` on 60,
+`message` on 49, `status` on 46, and five more keys carried the same meaning
+under different names. An agent could not tell success from failure without
+knowing which tool it had called.
+
+The frame is schema 1, the same one the Extension.js CLI emits under
+`--output json`:
+
+```json
+{
+  "schema": 1,
+  "ok": false,
+  "command": "extension_dev",
+  "status": "compile-failed",
+  "value": null,
+  "error": { "code": "E_FIRST_COMPILE", "message": "…" },
+  "hint": "…",
+  "warnings": []
+}
+```
+
+`command` names the tool. `status` is a kebab-case word from that tool's own
+vocabulary. `error.code` is stable and worth branching on; `error.message` is
+free copy and is not. The payload moved under `value`, and every advisory note
+that used to have its own key is now an entry in `warnings`.
+
+**Breaking.** Every payload key moved one level down. `build.success` is now
+`ok`, `doctor.healthy` is now `ok`, `manifest_validate.valid` is now
+`value.valid`, and `wait` gained the `ok` it never had. The ready contract's own
+`command` is carried as `value.sessionCommand`, because the envelope claims that
+key. `authorization_pending` became `authorization-pending`, with the old
+spelling echoed as `value.legacyStatus` for one minor.
+
+`extension_dev` and `extension_start` also stopped reading the dev server's
+prose to decide whether the first compile failed. They poll its `ready.json`
+contract instead, which splits a locked profile out of a dead browser and
+returns the compile errors as a list. The output scrape survives only as a
+fallback for a project whose own CLI predates the contract, is confined to one
+`@deprecated` module, and says so in `warnings` whenever it is used. The choice
+is a capability probe, never a version check: a project-local `extension` binary
+wins over this package's pin, so the version is not knowable in advance. The
+contract's own error stamps are read whatever the engine's age, so a locked
+profile is named as one the moment the engine records it.
+
 ## 9.0.0
 
 Every client pays for this server's tool list at the start of every session,

package/claude/rules/mcp-tools.md

@@ -154,7 +154,7 @@ These map directly to existing programmatic APIs and provide immediate value.
 ```json
 {
   "name": "extension_build",
-  "description": "Build a browser extension for production. Outputs to dist/<browser>/. Optionally creates .zip for store submission.",
+  "description": "Build a browser extension for production. The output lands in dist/<browser>/. Pass zip:true to also package a .zip for store submission. The build refuses a manifest with build-blocking errors unless you pass skipValidation:true, because such a manifest yields a broken bundle the bundler itself never flags.",
   "inputSchema": {
     "type": "object",
     "properties": {
@@ -610,22 +610,34 @@ The `similarTemplates` field lists templates from the catalog with similar surfa
 }
 ```
 
-**Returns:** The `ready.json` contract:
+**Returns:** The schema-1 envelope, carrying the `ready.json` contract under `value`:
 
 ```json
 {
+  "schema": 1,
+  "ok": true,
+  "command": "extension_wait",
   "status": "ready",
-  "command": "dev",
-  "browser": "chrome",
-  "port": 8080,
-  "pid": 12345,
-  "distPath": "/path/to/dist/chrome",
-  "manifestPath": "/path/to/dist/chrome/manifest.json",
-  "compiledAt": "2026-04-14T10:30:00.000Z",
-  "startedAt": "2026-04-14T10:29:55.000Z"
+  "value": {
+    "compiled": true,
+    "browserAttached": true,
+    "sessionCommand": "dev",
+    "browser": "chrome",
+    "port": 8080,
+    "pid": 12345,
+    "distPath": "/path/to/dist/chrome",
+    "manifestPath": "/path/to/dist/chrome/manifest.json",
+    "compiledAt": "2026-04-14T10:30:00.000Z",
+    "startedAt": "2026-04-14T10:29:55.000Z"
+  },
+  "error": null,
+  "warnings": []
 }
 ```
 
+The envelope's `command` names the tool, so the ready contract's own `command`
+is carried as `value.sessionCommand`.
+
 **Why this matters for MCP:** When Claude starts a dev session via `extension_dev`, it needs to know when the extension is actually loaded and ready before calling `extension_inspect`. This tool provides that gate.
 
 ---