@ai-ecoverse/mcpcat 0.17.0 → 0.17.1

package/README.md

@@ -26,7 +26,7 @@ mcpcat runs natively on macOS, Linux and Windows (Node ≥ 24), and inside Slicc
 
 ## Releases: certified = latest
 
-Every change that alters what mcpcat ships is certified before it reaches `main`. A pull request that touches `src/`, the build, the dependencies or the release workflows gets mcpcat's cert-review on a pack of its head, and again in the merge queue on the exact tree that lands on `main`; a FAIL blocks the merge. Docs-, test- and CI-only changes skip it as "not behaviour". Each merge to `main` is then released to npm as `latest` in one step by semantic-release, with provenance, so `npm install @ai-ecoverse/mcpcat` and the installer always get certified code. The verdict line is a comment on the pull request and the `cert-review` commit status. It reads `certified …`, `cert-ci: FAIL …` when the reviewer or a check in code found a defect (status `failure`), or `cert-ci: INCOMPLETE …` when the review couldn't decide: the review job didn't succeed or was skipped, no verdict could be read, or the artifact or the runner's own `gh` was missing (status `error`). A fork's change to shipped behaviour also reads INCOMPLETE, since it gets no review. INCOMPLETE never certifies; re-run the failed jobs. A run that ends without `record` posting its status (a crashed plan, record or verdict job) still posts one on the head: `error` with its INCOMPLETE line, `failure` for a FAIL, or `pending` while the coordinator approval is missing. So the required `cert-review` check never waits forever, and a label change reuses only a `success` or `failure` verdict, never an INCOMPLETE one. The reviewer's verdict can add defects but never clear one found in code: `record` re-reads the suites' evidence (`stage.json`, `suites.json`), uploaded before the reviewer runs and bound by the artifact id and digest the review job output. A suite or security row that failed on the host or a pinned kernel, a changed test that fails on the head, an import in the kernel bundle or an unexplained rebuild difference is a FAIL. Missing suites, kernels or rows are INCOMPLETE. The NEGATIVE runs each changed test on the base's code: the subject's tests, helpers and fixtures with the base's `dist`, `scripts/` and `.github/workflows/`, all from the base sha, so a test of the cert tooling runs against main's tooling. The record names both shas. A changed test that also passes on the base is named in the line as `gaps: no-negative <file>`. Every artifact a later job reads (the tarball, the verdict, the suites' evidence) is downloaded by the artifact id its producer output, after `bind.mjs` checks the artifact's name, run and digest against that producer's outputs. Any other artifact from this attempt of the run under `mcpcat-tarball-`, `mcpcat-npm-tarball-` or `cert-review-` makes the line INCOMPLETE. An earlier attempt's leftovers, created before this attempt started, are never read.
+Every change that alters what mcpcat ships is certified before it reaches `main`. A pull request that touches `src/`, the build, the dependencies or the release workflows gets mcpcat's cert-review on a pack of its head, and again in the merge queue on the exact tree that lands on `main`; a FAIL blocks the merge. Docs-, test- and CI-only changes skip it as "not behaviour". A draft pull request is not reviewed: its `cert-review` is red with `draft: not reviewed, mark it ready for review`, and marking it ready starts the review (converted_to_draft cancels a running one). Mark ready = reviewed, and merges on green; a pull request held for anything stays a draft. For a PR that needs the coordinator's security read, the order is: the coordinator reads the draft, it is marked ready, the cert runs, then the queue. Each merge to `main` is then released to npm as `latest` in one step by semantic-release, with provenance, so `npm install @ai-ecoverse/mcpcat` and the installer always get certified code. The verdict line is a comment on the pull request and the `cert-review` commit status. It reads `certified …`, `cert-ci: FAIL …` when the reviewer or a check in code found a defect (status `failure`), or `cert-ci: INCOMPLETE …` when the review couldn't decide: the review job didn't succeed or was skipped, no verdict could be read, or the artifact or the runner's own `gh` was missing (status `error`). A fork's change to shipped behaviour also reads INCOMPLETE, since it gets no review. INCOMPLETE never certifies; re-run the failed jobs. A run that ends without `record` posting its status (a crashed plan, record or verdict job) still posts one on the head: `error` with its INCOMPLETE line, `failure` for a FAIL, or `pending` while the coordinator approval is missing. So the required `cert-review` check never waits forever, and a label change reuses only a `success` or `failure` verdict, never an INCOMPLETE one. The reviewer's verdict can add defects but never clear one found in code: `record` re-reads the suites' evidence (`stage.json`, `suites.json`), uploaded before the reviewer runs and bound by the artifact id and digest the review job output. A suite or security row that failed on the host or a pinned kernel, a changed test that fails on the head, an import in the kernel bundle or an unexplained rebuild difference is a FAIL. Missing suites, kernels or rows are INCOMPLETE. The NEGATIVE runs each changed test on the base's code: the subject's tests, helpers and fixtures with the base's `dist`, `scripts/` and `.github/workflows/`, all from the base sha, so a test of the cert tooling runs against main's tooling. The record names both shas. A changed test that also passes on the base is named in the line as `gaps: no-negative <file>`. Every artifact a later job reads (the tarball, the verdict, the suites' evidence) is downloaded by the artifact id its producer output, after `bind.mjs` checks the artifact's name, run and digest against that producer's outputs. Any other artifact from this attempt of the run under `mcpcat-tarball-`, `mcpcat-npm-tarball-` or `cert-review-` makes the line INCOMPLETE. An earlier attempt's leftovers, created before this attempt started, are never read.
 
 After each release, `cert-verify.yml` (on the Release run's success, or dispatched from `main` with a `version`) checks again that npm serves the SLSA subject built by `release.yml` on `main` from the tag, and that every pull request merged since the previous tag carries a green `cert-review` status on its head. Its hosted, write-only `notes` job then puts one line into the GitHub release notes, between `<!-- cert-verify -->` markers: `certified @ai-ecoverse/mcpcat@<version> sha256=<sha> (…; pr-certified since v<prev>: …)`, or `verified …` when some pull request lacks a green cert-review. A re-run with the same bytes leaves the notes as they are. Notes that already name another sha for the version, or npm bytes that don't verify, are a supply-chain alert: nothing is written and an issue is filed. Checks that couldn't run read `cert-ci: INCOMPLETE` and write nothing.
 

package/dist/host/mcpcat.mjs

@@ -15432,11 +15432,15 @@ Client verbs:
   tools <target>             List tools
   call <target> <tool>       Call a tool
   describe <target> [tool]   Tool schema and help
+  resources <target>         List resources
+  read <target> <uri>        Read a resource
+  prompts <target>           List prompts
+  prompt <target> <name>     Get a prompt
 
 Configuration verbs:
   add <name> <url>           Add a server to mcp.json
-  add <name> --bridge -- 
-    Bridge a stdio server to HTTP (kernel only,
+  add <name> --bridge -- <command> [args\u2026]
+                             Bridge a stdio server to HTTP (kernel only,
                              runs in foreground, does not survive reload)
   rm <name>                  Remove a server
   list                       List configured servers
@@ -15452,12 +15456,12 @@ Server and code verbs:
   grep <pattern> [target\u2026]   Search tools by name or description
   discover <url>             Find MCP servers at a URL
   inbox [--json]             List discovery candidates
-  help [verb]                Show help
+  help                       Show this help
   help --skill               Print the agent skill (SKILL.md) for this version
 
 Options:
   --json                     JSON output
-  -H, --header 'N: V'       Extra header
+  -H, --header 'N: V'        Extra header
   -d <json>                  Tool arguments as JSON (or @file, @- for stdin)
   -m, --timeout <s>          Request timeout (default 60)
   --memory <MiB>             Code mode memory limit (default 256, max 1024)
@@ -15471,7 +15475,7 @@ Options:
   -s, --server <name>        Server target (code, repeatable)
   --allow-shell              Enable shell() global (code)
   -v, --verbose              Trace on stderr
-  -s, --silent               Suppress progress
+  --silent                   Suppress progress
   -o, --output <path>        Write result to file
   -V, --version              Print version
   -h, --help                 Show this help
@@ -16988,5 +16992,5 @@ try {
   });
 } catch {
 }
-var code = await run(platform, "0.17.0", args);
+var code = await run(platform, "0.17.1", args);
 process.exit(code);

package/dist/kernel/mcpcat.mjs

@@ -15053,11 +15053,15 @@ Client verbs:
   tools <target>             List tools
   call <target> <tool>       Call a tool
   describe <target> [tool]   Tool schema and help
+  resources <target>         List resources
+  read <target> <uri>        Read a resource
+  prompts <target>           List prompts
+  prompt <target> <name>     Get a prompt
 
 Configuration verbs:
   add <name> <url>           Add a server to mcp.json
-  add <name> --bridge -- 
-    Bridge a stdio server to HTTP (kernel only,
+  add <name> --bridge -- <command> [args\u2026]
+                             Bridge a stdio server to HTTP (kernel only,
                              runs in foreground, does not survive reload)
   rm <name>                  Remove a server
   list                       List configured servers
@@ -15073,12 +15077,12 @@ Server and code verbs:
   grep <pattern> [target\u2026]   Search tools by name or description
   discover <url>             Find MCP servers at a URL
   inbox [--json]             List discovery candidates
-  help [verb]                Show help
+  help                       Show this help
   help --skill               Print the agent skill (SKILL.md) for this version
 
 Options:
   --json                     JSON output
-  -H, --header 'N: V'       Extra header
+  -H, --header 'N: V'        Extra header
   -d <json>                  Tool arguments as JSON (or @file, @- for stdin)
   -m, --timeout <s>          Request timeout (default 60)
   --memory <MiB>             Code mode memory limit (default 256, max 1024)
@@ -15092,7 +15096,7 @@ Options:
   -s, --server <name>        Server target (code, repeatable)
   --allow-shell              Enable shell() global (code)
   -v, --verbose              Trace on stderr
-  -s, --silent               Suppress progress
+  --silent                   Suppress progress
   -o, --output <path>        Write result to file
   -V, --version              Print version
   -h, --help                 Show this help
@@ -16710,7 +16714,7 @@ async function main(ctx) {
     packageDir: "/node_modules/@ai-ecoverse/mcpcat"
   });
   const args = ctx.argv.slice(1);
-  return run(platform2, "0.17.0", args);
+  return run(platform2, "0.17.1", args);
 }
 export {
   main as default

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ai-ecoverse/mcpcat",
-  "version": "0.17.0",
+  "version": "0.17.1",
   "description": "A curl for the Model Context Protocol",
   "type": "module",
   "license": "Apache-2.0",
@@ -61,15 +61,15 @@
     "trust:dry": "npx fledgling sync --dry-run -y --skip-publish"
   },
   "devDependencies": {
-    "@ai-ecoverse/slicc-bios": "1.20.0",
-    "@ai-ecoverse/slicc-kernel": "1.127.1",
+    "@ai-ecoverse/slicc-bios": "1.30.4",
+    "@ai-ecoverse/slicc-kernel": "1.133.3",
     "@ai-ecoverse/slicc-shared-web": "1.23.2",
     "@biomejs/biome": "2.5.15",
     "@earendil-works/pi-codemode": "1.2.0",
     "@earendil-works/pi-mcp": "1.2.0",
     "@types/node": "26.6.5",
     "esbuild": "0.28.2",
-    "kernel-cert-new": "npm:@ai-ecoverse/slicc-kernel@1.127.1",
+    "kernel-cert-new": "npm:@ai-ecoverse/slicc-kernel@1.133.3",
     "monocart-coverage-reports": "2.13.2",
     "proper-lockfile": "4.1.2",
     "quickjs-wasi": "3.6.2",