@mercury-fw/cli-engine 0.31.1 → 0.32.0

package/CHANGELOG.md

@@ -1,5 +1,11 @@
 # @mercury-fw/cli-engine
 
+## 0.32.0
+
+### Patch Changes
+
+- @mercury-fw/plugin-types@0.32.0
+
 ## 0.31.1
 
 ### Patch Changes

package/cli-tool.ts

@@ -16,10 +16,9 @@
  * which can appear before the subcommand) consumed generically by
  * `stripGlobalFlags` — no more hand-written per-CLI stripping function.
  *
- * Used by: `src/index.ts` (wiring), which builds the `Record<string,
- * CliConfig>` (via `cli-config-loader.ts`) from whichever CLIs are
- * enabled on a given instance and passes it into `createCliTool`
- * alongside the real `runCli`.
+ * Used by: each CLI plugin's `build()`, which validates its own allowlist
+ * (via `cli-config-loader.ts`) into the `Record<string, CliConfig>` and
+ * passes it into `createCliTool` alongside the real `runCli`.
  */
 import { tool, type JSONValue } from "ai";
 import { z } from "zod";
@@ -166,7 +165,7 @@ export function createCliTool(
     stashDisplay?: (artifact: string) => string;
   },
 ): { runCommand: ExecutableTool } {
-  // Anchor the example on a binary actually enabled on this instance rather than
+  // Anchor the example on a binary this tool actually runs rather than
   // a hardcoded one: a fixed `jira …` example misleads the model on an instance
   // without Jira. The concrete, CLI-specific example (real subcommand + flags)
   // belongs to that CLI's own skill, not to this plugin-agnostic tool.

package/cli-version-check.ts

@@ -1,11 +1,9 @@
 /**
  * Checks an installed CLI binary's version against a maintainer-declared
  * `minVersion` (from an externally-configured CLI config file, see
- * `src/tools/cli-config-loader.ts`). No version-check convention existed
- * anywhere in this codebase before this — confirmed by searching
- * `scripts/install-clis.sh` (only resolves GitHub release *tags* to pick
- * a download asset, never validates an already-installed binary) and the
- * rest of `src/`.
+ * `src/tools/cli-config-loader.ts`). Nothing else validates an
+ * already-installed binary: provisioning downloads a pinned version and
+ * never checks it again.
  *
  * Assumes `--version` is the right flag to invoke — the CLIs are
  * Rust/clap-based, and `--version` is clap's near-universal default, but

package/dist/cli-version-check.d.ts

@@ -1,11 +1,9 @@
 /**
  * Checks an installed CLI binary's version against a maintainer-declared
  * `minVersion` (from an externally-configured CLI config file, see
- * `src/tools/cli-config-loader.ts`). No version-check convention existed
- * anywhere in this codebase before this — confirmed by searching
- * `scripts/install-clis.sh` (only resolves GitHub release *tags* to pick
- * a download asset, never validates an already-installed binary) and the
- * rest of `src/`.
+ * `src/tools/cli-config-loader.ts`). Nothing else validates an
+ * already-installed binary: provisioning downloads a pinned version and
+ * never checks it again.
  *
  * Assumes `--version` is the right flag to invoke — the CLIs are
  * Rust/clap-based, and `--version` is clap's near-universal default, but

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mercury-fw/cli-engine",
-  "version": "0.31.1",
+  "version": "0.32.0",
   "license": "MIT",
   "repository": {
     "type": "git",
@@ -23,7 +23,7 @@
     }
   },
   "dependencies": {
-    "@mercury-fw/plugin-types": "0.31.1",
+    "@mercury-fw/plugin-types": "0.32.0",
     "ai": "^7.0.126",
     "shell-quote": "^1.11.0",
     "zod": "^4.6.5"