@wirecat/cli-base 0.46.0 → 0.47.1

package/CHANGELOG.md

@@ -8,6 +8,28 @@ Versions before 0.8.0 are in the [git tags](https://github.com/WireCatLabs/cli-b
 Every entry says what changed as a caller sees it, why, and what to watch for — the rules are
 [`docs/dev/CONVENTIONS.md`](docs/dev/CONVENTIONS.md#the-changelog).
 
+## 0.47.1 — 19.10.2026
+
+### Added
+
+- **`--alias <name>` is a vocabulary flag** (role `query`): another name of the thing, searched as its own
+  alternative beside its name, repeatable. memo's `projects evidence` takes extra project names with it; before,
+  a CLI that wanted the option failed `option-role`.
+
+## 0.47.0 — 18.10.2026
+
+### Added
+
+- **A command step may carry `line`, the whole command to type** (`nextStepSchema`): `tg personal mcp config`, with
+  the profile, where `command` stays the bare path the MCP router takes. A CLI fills it, since only it knows the
+  profile; `renderError` prints `line` when it is there.
+
+### Fixed
+
+- **The permissions page says wa's `listen` is on main, not released**: WC-PERM-12's "Who follows these rules
+  today" said wa pins cli-core 0.341.0 with no `listen`. whatsapp-cli#136 moved wa's main branch to 0.343.0 with
+  `listen`, so its one-shot commands save incoming history there; wa 0.1.0, the newest release, still does not.
+
 ## 0.46.0 — 18.10.2026
 
 ### Added

package/dist/failure.d.ts

@@ -72,6 +72,7 @@ export declare const mcpErrorResult: (object: ErrorObject) => {
                 args: {
                     [x: string]: unknown;
                 };
+                line?: string | undefined;
                 why: string;
                 safe_to_auto_execute: boolean;
             } | {

package/dist/failure.js

@@ -150,7 +150,7 @@ export const renderError = (object, options) => {
     return [
         `✗ ${visibleControls(message)}`,
         ...(step?.kind === "command"
-            ? [`→ ${visibleControls(step.why)}: ${visibleControls(commandLine(options.cli, step))}`]
+            ? [`→ ${visibleControls(step.why)}: ${visibleControls(step.line ?? commandLine(options.cli, step))}`]
             : step
                 ? [`→ ${visibleControls(step.why)}`]
                 : []),

package/dist/standards/errors.d.ts

@@ -19,6 +19,7 @@ export declare const errorObjectSchema: v.StrictObjectSchema<{
             readonly step: v.SchemaWithPipe<readonly [v.StringSchema<undefined>, v.RegexAction<string, "dotted lower-case words, such as `page.next`">]>;
             readonly command: v.SchemaWithPipe<readonly [v.StringSchema<undefined>, v.RegexAction<string, "must not be empty">]>;
             readonly args: v.RecordSchema<v.StringSchema<undefined>, v.UnknownSchema, undefined>;
+            readonly line: v.OptionalSchema<v.SchemaWithPipe<readonly [v.StringSchema<undefined>, v.RegexAction<string, "must not be empty">]>, undefined>;
             readonly why: v.SchemaWithPipe<readonly [v.StringSchema<undefined>, v.RegexAction<string, "must not be empty">]>;
             readonly safe_to_auto_execute: v.BooleanSchema<undefined>;
         }, undefined>, v.StrictObjectSchema<{
@@ -33,6 +34,7 @@ export declare const errorObjectSchema: v.StrictObjectSchema<{
             args: {
                 [x: string]: unknown;
             };
+            line?: string | undefined;
             why: string;
             safe_to_auto_execute: boolean;
         } | {

package/dist/standards/flags-what.js

@@ -13,6 +13,13 @@ export const WHAT_FLAGS = [
         type: "string",
         meaning: "literal words to find within the communications selected for preparation",
     },
+    {
+        name: "--alias",
+        value: "<name>",
+        role: "query",
+        type: "string",
+        meaning: "another name of the thing, searched as its own alternative beside its name; repeat for more",
+    },
     {
         name: "--context-since-time",
         value: "<time>",

package/dist/standards/output.d.ts

@@ -10,6 +10,11 @@ export declare const nextStepSchema: v.VariantSchema<"kind", [v.StrictObjectSche
     /** The command path as one string, `messages list` — what the MCP router tools take as `command`. */
     readonly command: v.SchemaWithPipe<readonly [v.StringSchema<undefined>, v.RegexAction<string, "must not be empty">]>;
     readonly args: v.RecordSchema<v.StringSchema<undefined>, v.UnknownSchema, undefined>;
+    /**
+     * The whole line to type, with the tool and the profile it ran with: `tg personal mcp config`. Only the CLI
+     * knows the profile, so it fills this; MCP answers leave it out.
+     */
+    readonly line: v.OptionalSchema<v.SchemaWithPipe<readonly [v.StringSchema<undefined>, v.RegexAction<string, "must not be empty">]>, undefined>;
     readonly why: v.SchemaWithPipe<readonly [v.StringSchema<undefined>, v.RegexAction<string, "must not be empty">]>;
     /** True only when the target command is known to write nothing, here or at the provider. */
     readonly safe_to_auto_execute: v.BooleanSchema<undefined>;
@@ -80,6 +85,11 @@ export declare const listEnvelopeSchema: <T extends v.GenericSchema>(item: T) =>
         /** The command path as one string, `messages list` — what the MCP router tools take as `command`. */
         readonly command: v.SchemaWithPipe<readonly [v.StringSchema<undefined>, v.RegexAction<string, "must not be empty">]>;
         readonly args: v.RecordSchema<v.StringSchema<undefined>, v.UnknownSchema, undefined>;
+        /**
+         * The whole line to type, with the tool and the profile it ran with: `tg personal mcp config`. Only the CLI
+         * knows the profile, so it fills this; MCP answers leave it out.
+         */
+        readonly line: v.OptionalSchema<v.SchemaWithPipe<readonly [v.StringSchema<undefined>, v.RegexAction<string, "must not be empty">]>, undefined>;
         readonly why: v.SchemaWithPipe<readonly [v.StringSchema<undefined>, v.RegexAction<string, "must not be empty">]>;
         /** True only when the target command is known to write nothing, here or at the provider. */
         readonly safe_to_auto_execute: v.BooleanSchema<undefined>;
@@ -95,6 +105,7 @@ export declare const listEnvelopeSchema: <T extends v.GenericSchema>(item: T) =>
         args: {
             [x: string]: unknown;
         };
+        line?: string | undefined;
         why: string;
         safe_to_auto_execute: boolean;
     } | {
@@ -131,6 +142,11 @@ export declare const itemEnvelopeSchema: <T extends v.GenericSchema>(item: T) =>
         /** The command path as one string, `messages list` — what the MCP router tools take as `command`. */
         readonly command: v.SchemaWithPipe<readonly [v.StringSchema<undefined>, v.RegexAction<string, "must not be empty">]>;
         readonly args: v.RecordSchema<v.StringSchema<undefined>, v.UnknownSchema, undefined>;
+        /**
+         * The whole line to type, with the tool and the profile it ran with: `tg personal mcp config`. Only the CLI
+         * knows the profile, so it fills this; MCP answers leave it out.
+         */
+        readonly line: v.OptionalSchema<v.SchemaWithPipe<readonly [v.StringSchema<undefined>, v.RegexAction<string, "must not be empty">]>, undefined>;
         readonly why: v.SchemaWithPipe<readonly [v.StringSchema<undefined>, v.RegexAction<string, "must not be empty">]>;
         /** True only when the target command is known to write nothing, here or at the provider. */
         readonly safe_to_auto_execute: v.BooleanSchema<undefined>;
@@ -146,6 +162,7 @@ export declare const itemEnvelopeSchema: <T extends v.GenericSchema>(item: T) =>
         args: {
             [x: string]: unknown;
         };
+        line?: string | undefined;
         why: string;
         safe_to_auto_execute: boolean;
     } | {

package/dist/standards/output.js

@@ -13,6 +13,11 @@ export const nextStepSchema = v.variant("kind", [
         /** The command path as one string, `messages list` — what the MCP router tools take as `command`. */
         command: text,
         args: v.record(v.string(), v.unknown()),
+        /**
+         * The whole line to type, with the tool and the profile it ran with: `tg personal mcp config`. Only the CLI
+         * knows the profile, so it fills this; MCP answers leave it out.
+         */
+        line: v.optional(text),
         why: text,
         /** True only when the target command is known to write nothing, here or at the provider. */
         safe_to_auto_execute: v.boolean(),

package/docs/standards/output.md

@@ -102,9 +102,11 @@ JSON Schema 2020-12.
 - **Example:** `next` holds the step to take, then one alternative. Each has `kind` (`command`, or `user_action` with
   no command) and `safe_to_auto_execute`. A step that reads the service and writes only the local store (a sync) is
   safe. A step that reads nothing remotely and writes locally (`store reindex`) is not: it waits to be asked. A step
-  is built from ids, counts and cursors the CLI holds, never from text a message, mail or document carried.
+  is built from ids, counts and cursors the CLI holds, never from text a message, mail or document carried. A CLI
+  answer's command step also has `line`, the whole command with the profile (`tg personal mcp config`), because
+  `command` is the bare path an MCP router takes and a copied path without the profile fails.
 - **Exceptions:** none.
-- **Applies to:** all CLIs. **Since:** cli-base 0.41.0. **Rulings:** none.
+- **Applies to:** all CLIs. **Since:** cli-base 0.41.0 (`line`: next release). **Rulings:** none.
 
 ### WC-OUT-10 · Answer a write with what it did and its `operation_id`
 

package/docs/standards/permissions.md

@@ -24,7 +24,8 @@ writes", drive is a known gap.
 WC-PERM-10 and WC-PERM-11 need cli-core 0.321.0, which tg, max and wa pin. WC-PERM-12 as written needs cli-core
 0.337.0; before it, the lock let through some local writes that overwrite what the owner saved. A command other
 than `serve` and `watch` saves incoming history only from cli-core 0.343.0, and only when the messenger's adapter has
-`listen`. wa is the one messenger whose history lives in the store; it pins 0.341.0 and has no `listen` yet.
+`listen`. wa is the one messenger whose history lives in the store. Its main branch pins 0.343.0 and has `listen`
+(whatsapp-cli#136), but no release carries it yet: the newest, wa 0.1.0, pins 0.326.0 and has no `listen`.
 
 ## Rules
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wirecat/cli-base",
-  "version": "0.46.0",
+  "version": "0.47.1",
   "description": "The parts every command line tool needs: output modes, terminal rendering, error model, exit codes, credentials, clocks",
   "license": "Apache-2.0",
   "author": "Viacheslav Ptsarev",