@mercury-fw/cli-engine 0.38.0 → 0.39.0

package/CHANGELOG.md

@@ -1,5 +1,30 @@
 # @mercury-fw/cli-engine
 
+## 0.39.0
+
+### Minor Changes
+
+- 881835c: A CLI's login is set up inside the app's container, no longer carried in the env file.
+
+  - A plugin declares in `mercury.cliCredentials` the commands that set its CLI's login up (`setup`, required), check it (`check`) and log an identity out (`logout`), each a binary followed by its arguments.
+  - `mfw credentials setup <plugin>` runs the declared setup in a one-off container on your terminal, so the CLI writes its login straight onto the credentials volume; `mfw credentials check <plugin>` runs the declared check.
+  - `mfw credentials reset <plugin> [--user <key>]` runs the declared logout, of the identity Mercury runs as or of one person, instead of deleting the CLI's folder.
+  - `mfw credentials set` is removed, and the core no longer unpacks `*_CONFIG_TAR_B64` variables at startup: it reports a declared login that isn't set up yet, and still links a login kept outside `~/.config` to the volume.
+  - A command the model writes with `--user` is refused: which person a CLI acts as is never the model's to pick.
+  - `cliUserId` (`@mercury-fw/utils`) maps a user key to the id a CLI knows a person by.
+  - plugin-jira and plugin-bitbucket pin their CLIs at 2.1.0, which keep the service identity and each person apart and refuse the old login folder. After updating, remove the plugin's `*_CONFIG_TAR_B64` line from the env file and run `mfw credentials setup` once; on Jira, Mercury now runs as an Atlassian Service Account.
+  - plugin-atlassian-admin keeps its CLI at 0.1.2, whose `init` doesn't prompt for the organization key: until it does, write the key from `mfw shell` with `atlassian-admin init --api-key <KEY> --org-id <ORG_ID>` (the plugin's README says so).
+
+### Patch Changes
+
+- @mercury-fw/plugin-types@0.39.0
+
+## 0.38.1
+
+### Patch Changes
+
+- @mercury-fw/plugin-types@0.38.1
+
 ## 0.38.0
 
 ### Patch Changes

package/cli-tool.ts

@@ -128,8 +128,8 @@ export function omitDisplayForModel(output: unknown): unknown {
 /**
  * Builds the `runCommand` tool: the model writes a whole CLI invocation as
  * one string, `execute` parses it (`parseCommand`), checks the binary
- * against `configs`, then classifies the argv via `matchCommand` — each
- * failure mode (unparseable / unknown binary / confirm-required /
+ * against `configs`, refuses an identity flag (`--user`), then classifies the argv via `matchCommand` — each
+ * failure mode (unparseable / identity flag / unknown binary / confirm-required /
  * not-allowed) gets a distinct, self-correctable error message — before
  * ever calling `runCliFn`. `runCliFn` is injected (defaulting to the real
  * `runCli` in production) so tests can supply a fake without spawning a
@@ -181,6 +181,16 @@ export function createCliTool(
         return { ok: false, error: `could not parse "${command}": ${parsed.error}` };
       }
 
+      // The CLIs act as whoever `--user <id>` names: which identity a command
+      // runs as is Mercury's decision, never something the model writes.
+      if (parsed.args.some((a) => a === "--user" || a.startsWith("--user="))) {
+        return {
+          ok: false,
+          error:
+            "--user is not allowed: Mercury decides whose account a command runs as, never the command itself. Run it again without --user.",
+        };
+      }
+
       const config = configs[parsed.binary];
       if (!config) {
         const known = Object.keys(configs).join(", ") || "(none configured)";

package/dist/cli-tool.d.ts

@@ -70,8 +70,8 @@ export declare function omitDisplayForModel(output: unknown): unknown;
 /**
  * Builds the `runCommand` tool: the model writes a whole CLI invocation as
  * one string, `execute` parses it (`parseCommand`), checks the binary
- * against `configs`, then classifies the argv via `matchCommand` — each
- * failure mode (unparseable / unknown binary / confirm-required /
+ * against `configs`, refuses an identity flag (`--user`), then classifies the argv via `matchCommand` — each
+ * failure mode (unparseable / identity flag / unknown binary / confirm-required /
  * not-allowed) gets a distinct, self-correctable error message — before
  * ever calling `runCliFn`. `runCliFn` is injected (defaulting to the real
  * `runCli` in production) so tests can supply a fake without spawning a

package/package.json

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