@gempack/squad-mcp 0.8.0 → 0.8.2

package/.claude-plugin/marketplace.json

@@ -12,7 +12,7 @@
         "repo": "ggemba/squad-mcp"
       },
       "description": "Squad-dev workflow: deterministic classification, risk scoring, agent selection, advisory orchestration over MCP, native subagents, plus /squad:implement and /squad:review slash commands.",
-      "version": "0.8.0",
+      "version": "0.8.2",
       "license": "Apache-2.0",
       "homepage": "https://github.com/ggemba/squad-mcp"
     }

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "squad",
-  "version": "0.8.0",
+  "version": "0.8.2",
   "description": "Squad-dev workflow as a Claude Code plugin: classification, risk scoring, agent selection, advisory orchestration. Bundles an MCP server, native subagents, and the /squad:implement and /squad:review slash commands.",
   "license": "Apache-2.0",
   "author": {
@@ -36,7 +36,7 @@
   "mcpServers": {
     "squad": {
       "command": "npx",
-      "args": ["-y", "@gempack/squad-mcp@0.8.0"]
+      "args": ["-y", "@gempack/squad-mcp@0.8.2"]
     }
   }
 }

package/CHANGELOG.md

@@ -7,6 +7,25 @@ this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.htm
 
 ## [Unreleased]
 
+## [0.8.2] - 2026-05-10
+
+Second patch for the release pipeline. v0.8.0 / v0.8.1 on npm are functional — this release exists to actually verify the smoke job (v0.8.1's smoke fix was insufficient).
+
+### Fixed
+
+- **Real root cause: `dist/index.js` was published with mode `644` (not executable).** When npm installed the published tarball, the bin symlink `node_modules/.bin/squad-mcp` pointed at a non-executable target. The shell then reported `sh: 1: squad-mcp: not found` (which dash uses for both "missing on PATH" and "found but cannot exec"). Every release since v0.7.0 hit this. Fixed by appending `chmod +x dist/index.js` to the `build` script in `package.json` so the file is executable when packaged.
+- **Smoke job no longer routes through npx for invocation.** Previously the smoke spawned `npx -y @scope/pkg` (and v0.8.1 tried the `--package=` long form) — both relied on npx to wire the bin onto PATH, which has been unreliable for scoped packages on Ubuntu CI. New approach: `npm install --no-save` into a temp dir, then `spawn("node", [absPath])` directly on `dist/index.js`. No PATH lookup, no npx, no shell-resolved bin name. Strictly proves the published tarball boots end-to-end and speaks JSON-RPC over stdio.
+- Smoke timeout lowered from 90s to 30s — without the npx fetch+spawn ladder, the only cost is the server's own startup (~1-2s).
+
+## [0.8.1] - 2026-05-10
+
+Patch release for the release pipeline. The 0.8.0 package on npm is functionally identical — this release exists to validate the smoke job.
+
+### Fixed
+
+- **`release.yml` smoke job: `sh: 1: squad-mcp: not found`.** The post-publish smoke step spawned `npx -y @gempack/squad-mcp@<tag>` with no explicit bin name. In npm 10+ on Ubuntu CI, that short form has been unreliable for scoped packages — npx fails to wire the bin onto PATH and falls back to running the unscoped name as a shell command, which is not found. Switched both the warm-cache step and the smoke step to the long form `npx -y --package=@gempack/squad-mcp@<tag> squad-mcp`, which gives npm an explicit (package, bin) tuple to resolve.
+- **Warm-cache step no longer silently masks failure.** The previous `|| true` at the end of the warm step had been hiding the same npx-bin-resolution failure for every release since v0.7.0. Removed — if the warm step fails now, the run aborts before wasting 90s on the smoke timeout.
+
 ## [0.8.0] - 2026-05-10
 
 Three themes: **execution depth** (the user can size each run), **command surface cleanup** (no more stuttering `/squad:squad`), and **fast code Q&A** (new `code-explorer` subagent + `/squad:question` skill).

package/dist/index.js

@@ -7,7 +7,7 @@ import { listResources, readResource } from "./resources/registry.js";
 import { listPrompts, getPrompt } from "./prompts/registry.js";
 import { logger, setupProcessHandlers } from "./observability/logger.js";
 setupProcessHandlers();
-const SERVER_VERSION = "0.8.0";
+const SERVER_VERSION = "0.8.2";
 const server = new Server({
     name: "squad-mcp",
     version: SERVER_VERSION,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@gempack/squad-mcp",
-  "version": "0.8.0",
+  "version": "0.8.2",
   "description": "MCP server for the squad-dev workflow: classification, risk scoring, agent selection, advisory orchestration",
   "type": "module",
   "license": "Apache-2.0",
@@ -31,7 +31,7 @@
   },
   "main": "dist/index.js",
   "scripts": {
-    "build": "tsc",
+    "build": "tsc && chmod +x dist/index.js",
     "watch": "tsc --watch",
     "start": "node dist/index.js",
     "dev": "tsx src/index.ts",