pi-session-mcp 0.6.2 → 0.6.3

package/.pi-session-mcp-cli/doctor.js

@@ -104,8 +104,15 @@ export async function runDoctor(dependencies = {}) {
             const packageMtime = (await fs.stat(join(root, "package.json"))).mtimeMs;
             const lockMtime = await lockfileMtime(fs, root);
             const inputMtimes = [packageMtime, lockMtime].filter((value) => value !== undefined);
-            if (!dependencies.fileSystem)
-                inputMtimes.push(...await productionBuildInputMtimes(root));
+            if (!dependencies.fileSystem) {
+                const buildInputMtimes = await productionBuildInputMtimes(root);
+                // npm writes an installed package at extraction time in archive order, so without
+                // build inputs the manifest times say nothing about the freshness of the build.
+                if (buildInputMtimes.length === 0)
+                    inputMtimes.length = 0;
+                else
+                    inputMtimes.push(...buildInputMtimes);
+            }
             if (inputMtimes.some((mtime) => mtime > buildMtime))
                 checks.push(warning("build_stale", "build output", "run the production build"));
             else

package/CHANGELOG.md

@@ -2,6 +2,17 @@
 
 ## Unreleased
 
+## 0.6.3 — 2026-10-10
+
+- Doctor no longer reports a false `build_stale` warning right after
+  `npm install` with npm 12. npm 12 writes extracted files with the extraction
+  time, and the package lists `dist/` before `package.json`, so the installed
+  manifest was always newer than the build. An installation without build
+  configuration or TypeScript sources no longer compares manifest times; a
+  source checkout still does.
+- `setup` was re-recorded against Claude Code `2.1.296`; its `mcp` command
+  contract is unchanged.
+
 ## 0.6.2 — 2026-10-09
 
 - The server now shuts down when the MCP client closes its stdin. Previously

package/README.md

@@ -29,7 +29,7 @@ It is not the right tool when:
 
 ## Status
 
-The package version is **0.6.2**.
+The package version is **0.6.3**.
 
 - **Pre-1.0.** The public tool contract is stable within a minor line: a change to tools, fields, states or error codes needs a new minor release.
 - **Linux only**, Node.js 22.19.0 or newer.

package/dist/doctor.js

@@ -104,8 +104,15 @@ export async function runDoctor(dependencies = {}) {
             const packageMtime = (await fs.stat(join(root, "package.json"))).mtimeMs;
             const lockMtime = await lockfileMtime(fs, root);
             const inputMtimes = [packageMtime, lockMtime].filter((value) => value !== undefined);
-            if (!dependencies.fileSystem)
-                inputMtimes.push(...await productionBuildInputMtimes(root));
+            if (!dependencies.fileSystem) {
+                const buildInputMtimes = await productionBuildInputMtimes(root);
+                // npm writes an installed package at extraction time in archive order, so without
+                // build inputs the manifest times say nothing about the freshness of the build.
+                if (buildInputMtimes.length === 0)
+                    inputMtimes.length = 0;
+                else
+                    inputMtimes.push(...buildInputMtimes);
+            }
             if (inputMtimes.some((mtime) => mtime > buildMtime))
                 checks.push(warning("build_stale", "build output", "run the production build"));
             else

package/docs/acceptance.md

@@ -225,3 +225,18 @@ Release notes state which levels were run for a release and what was not
 covered. Pi Session MCP has passed all three levels in earlier private cycles. The
 live two-client acceptance has not yet been repeated on a build with Pi SDK
 `1.x`.
+
+`v0.6.2` passed Level 1 on a fresh clone of its tag. It passed Level 2 in all
+three variants: working tree, published release, and published npm package.
+The clients were Codex CLI `0.162.0` (`user`) and Claude Code `2.1.295`
+(`user`, `project`, `local`), on 2026-10-09 and 2026-10-10. It had no Level 3
+cycle.
+
+Before its release, `v0.6.3` passed Level 1 and the working-tree Level 2 on its
+release candidate, with Claude Code `2.1.296`. On 2026-10-10 the same candidate
+also passed a narrower live check:
+- Scope: Claude Code `2.1.296` as the only client, with Pi SDK `1.1.0` on a
+  local `qwen3.6-35b-a3b-splash` model served by LM Studio.
+- All five tasks of the matrix reached their intended outcome in three
+  sequential invocations, and every pre-registered check passed.
+- It covered no Codex task and does not count as a ten-task cycle.

package/docs/doctor-design.md

@@ -20,7 +20,7 @@ and owners are:
 | `node_version_unsupported` | Runtime does not satisfy `package.json#engines.node` | `Node.js` |
 | `package_metadata_unreadable` | Package metadata is missing, unreadable or malformed, or a lockfile is present but malformed | `package metadata` |
 | `build_missing` | `dist/main.js` is absent, inaccessible, or not a regular file | `build output` |
-| `build_stale` | Package, lock, build configuration, or production TypeScript input is newer than the build output, or freshness cannot be established. Inputs that an npm installation does not contain are skipped | `build output` |
+| `build_stale` | Package, lock, build configuration, or production TypeScript input is newer than the build output, or freshness cannot be established. Inputs that an npm installation does not contain are skipped. Without any build configuration or TypeScript input, as in an npm installation, the package and lock times are not compared either, because npm writes extracted files with the extraction time | `build output` |
 | `version_mismatch` | Package and lock versions differ; this is a warning and does not apply to an npm installation, which has no lockfile | `package version` |
 | `config_missing` | `PI_SESSION_MCP_CONFIG` is not set, or the file it names is absent | `configuration` |
 | `config_unreadable` | The supported configuration path cannot be read | `configuration` |

package/docs/installation.md

@@ -47,7 +47,7 @@ the same arguments.
 - Codex CLI or Claude Code. `setup` does not pin client versions. It accepts a
   client whose public `mcp` command output matches the expected contract and
   reports `unsupported` otherwise. The contract was last recorded with Codex CLI
-  `0.162.0` and Claude Code `2.1.295`. Manual registration, described in the
+  `0.162.0` and Claude Code `2.1.296`. Manual registration, described in the
   [client setup reference](client-setup.md), works independently of `setup`.
 - For real prompts only: local Pi authentication and a provider and model pair
   that the local Pi configuration knows. Installation, Doctor and `setup` need

package/docs/tool-contracts.md

@@ -22,7 +22,7 @@ There are exactly eight tools. No `pi_turn_wait` tool or live provider/model inv
 ```json
 {
   "ok": true,
-  "server": { "name": "pi-session-mcp", "version": "0.6.2" },
+  "server": { "name": "pi-session-mcp", "version": "0.6.3" },
   "configuration": {
     "fingerprint": "sha256:0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef",
     "reloadPolicy": "restart-required"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pi-session-mcp",
-  "version": "0.6.2",
+  "version": "0.6.3",
   "description": "Local stdio MCP server for controlled Pi coding-agent sessions",
   "license": "MIT",
   "keywords": [