pi-mcp-extension 1.10.1 → 1.10.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pi-mcp-extension",
-  "version": "1.10.1",
+  "version": "1.10.2",
   "description": "MCP (Model Context Protocol) client extension for the Pi coding agent — connect Pi to any MCP server",
   "type": "module",
   "keywords": [
@@ -34,7 +34,7 @@
   },
   "dependencies": {
     "@modelcontextprotocol/sdk": "^1.32.1",
-    "zod": "^4.6.5"
+    "zod": "^4.6.7"
   },
   "peerDependencies": {
     "@earendil-works/pi-ai": "*",

package/src/jsonc.ts

@@ -1,15 +1,15 @@
 /**
  * Pure JSON-with-comments (JSONC) text utilities. This module has no `src/`
- * dependencies of its own and is safe for the test tree to import: it does not
- * load `zod`, the MCP error types, or the OAuth/callback modules, so a `tests/`
- * consumer stays free of runtime MCP imports.
+ * dependencies of its own and is safe for `scripts/` and `tests/` to import: it
+ * does not load `zod`, the MCP error types, or the OAuth/callback modules, so
+ * non-runtime consumers stay free of runtime MCP imports.
  *
  * The only behaviour this module performs is `stripJsonComments` — a single-pass
  * character scan that removes `//` line comments and `/* ... *\/` block comments
  * while leaving the rest of the document byte-equivalent. Comments inside
  * double-quoted strings are preserved verbatim, so a JSON value such as
  * `"https://example.com/foo"` is never accidentally truncated. Trailing commas
- * (the other common JSONC extension) are **not** handled here — neither of the
+ * (the other common JSONC extension) are **not** handled here — none of the
  * files this helper feeds today uses them, and an explicit `JSON.parse` failure
  * on a misplaced comma is a more honest signal than silent acceptance.
  */
@@ -22,11 +22,11 @@
  * remain accurate. Unterminated `/*` block comments are left intact so `JSON.parse`
  * fails with a syntax error rather than silently truncating the document.
  *
- * WHY: this module exists so `tests/repo-policy.test.ts` can read
- * `.github/rulesets/default-branch.json` with the same JSONC tolerance the runtime
- * uses for `mcp.json`. A future maintainer can add `// WHY: …` style comments to the
- * ruleset (mirroring the convention used throughout `src/`) without breaking the
- * ruleset-policy tests.
+ * WHY: this module exists so `scripts/ruleset-audit.ts` and `tests/repo-policy.test.ts`
+ * can read `.github/rulesets/*.json` with the same JSONC tolerance the runtime uses
+ * for `mcp.json`. A future maintainer can add `// WHY: …` style comments to the
+ * ruleset files (mirroring the convention used throughout `src/`) without breaking the
+ * ruleset audit or policy tests.
  */
 export function stripJsonComments(text: string): string {
   let out = "";