@wirecat/cli-base 0.70.0 → 0.71.0

package/CHANGELOG.md

@@ -8,6 +8,20 @@ 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.71.0 — 01.11.2026
+
+### Added
+
+- **A vocabulary flag can list the value names other domains give it (`otherValues`).** `--to` stays `<chat>` and also
+  takes `<address>` (mail); `--subject` stays `<ref>` and also takes `<text>`. `flag-two-meanings` accepts those and
+  reports any other value name. A CLI that declares `--to <address>` or `--subject <text>` needs no override.
+
+### Fixed
+
+- **0.70.0 made every messenger CLI fail `flag-two-meanings`.** It wrote `--to` as `<chat|address>` and `--subject`
+  as `<ref|text>`, and the lint compares the value name as written, so `--to <chat>` was reported. Both go back to
+  the original value name, and mail's names are listed beside them. Do not use 0.70.0.
+
 ## 0.70.0 — 01.11.2026
 
 ### Added

package/dist/dev/lint.js

@@ -229,7 +229,10 @@ const CHECKS = {
         }));
     },
     "flag-two-meanings": (document, vocabulary) => {
-        const registered = new Map(vocabulary.flags.map((flag) => [flag.name, flag.value?.slice(1, -1).toLowerCase() ?? "switch"]));
+        const registered = new Map(vocabulary.flags.map((flag) => [
+            flag.name,
+            [flag.value?.slice(1, -1).toLowerCase() ?? "switch", ...(flag.otherValues ?? [])],
+        ]));
         const uses = new Map();
         const note = (option, where) => {
             const name = longName(option.flags);
@@ -246,8 +249,8 @@ const CHECKS = {
         const found = [];
         for (const [name, kinds] of [...uses].sort(([a], [b]) => byText(a, b))) {
             const expected = registered.get(name);
-            const off = expected === undefined ? [] : [...kinds.keys()].filter((kind) => kind !== expected);
-            if (kinds.size < 2 && off.length === 0)
+            const off = expected === undefined ? [] : [...kinds.keys()].filter((kind) => !expected.includes(kind));
+            if (expected === undefined ? kinds.size < 2 : off.length === 0)
                 continue;
             const described = [...kinds]
                 .map(([kind, where]) => `${kind === "switch" ? "a switch" : `<${kind}>`} in ${where.slice(0, 3).join(", ")}`)
@@ -256,7 +259,7 @@ const CHECKS = {
                 target: name,
                 message: expected === undefined
                     ? `${name} has ${kinds.size} meanings: ${described}`
-                    : `${name} is ${expected === "switch" ? "a switch" : `<${expected}>`} in the vocabulary, but: ${described}`,
+                    : `${name} is ${expected[0] === "switch" ? "a switch" : expected.map((kind) => `<${kind}>`).join(" or ")} in the vocabulary, but: ${described}`,
             });
         }
         return found;

package/dist/standards/flags-what.js

@@ -444,10 +444,11 @@ export const WHAT_FLAGS = [
     { name: "--task", value: "<id>", role: "target", type: "id", meaning: "a task, by id" },
     {
         name: "--to",
-        value: "<chat|address>",
+        value: "<chat>",
         role: "target",
-        type: "string",
-        meaning: "who it goes to: a chat in a messenger, an e-mail address in mail; repeat it for more addresses",
+        type: "id",
+        otherValues: ["address"],
+        meaning: "who it goes to: a chat in a messenger (<chat>), an e-mail address in mail (<address>, repeated for more)",
     },
     {
         name: "--topic-name",
@@ -895,10 +896,11 @@ export const WHAT_FLAGS = [
     { name: "--sticker", value: "<id>", role: "value", type: "id", meaning: "send this sticker, alone" },
     {
         name: "--subject",
-        value: "<ref|text>",
+        value: "<ref>",
         role: "value",
         type: "string",
-        meaning: "what it is about: a reference in a note or task, the subject line in mail",
+        otherValues: ["text"],
+        meaning: "what it is about: a reference in a note or task (<ref>), the subject line in mail (<text>)",
         replaces: ["--about"],
     },
     {

package/dist/standards/vocabulary.d.ts

@@ -43,6 +43,11 @@ export declare const vocabularySchema: v.StrictObjectSchema<{
         readonly type: v.PicklistSchema<readonly ["switch", "count", "number", "string", "id", "time", "duration", "choice", "list", "path", "cursor"], undefined>;
         readonly role: v.PicklistSchema<["action" | "budget" | "mode" | "output" | "paging" | "query" | "scope" | "sort" | "target" | "value", ...("action" | "budget" | "mode" | "output" | "paging" | "query" | "scope" | "sort" | "target" | "value")[]], undefined>;
         readonly meaning: v.SchemaWithPipe<readonly [v.StringSchema<undefined>, v.RegexAction<string, "must not be empty">]>;
+        /**
+         * Value names a domain other than the main one gives the flag, such as mail's `--to <address>` beside the
+         * messengers' `<chat>`. The meaning for each says which is which. `flag-two-meanings` accepts these and no others.
+         */
+        readonly otherValues: v.OptionalSchema<v.ArraySchema<v.SchemaWithPipe<readonly [v.StringSchema<undefined>, v.RegexAction<string, "a value name such as address">]>, undefined>, undefined>;
         readonly unit: v.OptionalSchema<v.SchemaWithPipe<readonly [v.StringSchema<undefined>, v.RegexAction<string, "must not be empty">]>, undefined>;
         /** Other names for the same flag, which `flag-synonym` refuses. */
         readonly replaces: v.OptionalSchema<v.ArraySchema<v.SchemaWithPipe<readonly [v.StringSchema<undefined>, v.RegexAction<string, "a long flag">]>, undefined>, undefined>;

package/dist/standards/vocabulary.js

@@ -49,6 +49,11 @@ const flagSchema = v.strictObject({
     type: v.picklist(FLAG_TYPES),
     role: v.picklist(Object.keys(FLAG_ROLES)),
     meaning: text,
+    /**
+     * Value names a domain other than the main one gives the flag, such as mail's `--to <address>` beside the
+     * messengers' `<chat>`. The meaning for each says which is which. `flag-two-meanings` accepts these and no others.
+     */
+    otherValues: v.optional(v.array(v.pipe(v.string(), v.regex(/^[a-z][a-z0-9-]*$/, "a value name such as address")))),
     unit: v.optional(text),
     /** Other names for the same flag, which `flag-synonym` refuses. */
     replaces: v.optional(v.array(v.pipe(v.string(), v.regex(/^--[a-z][a-z0-9]*(-[a-z0-9]+)*$/, "a long flag")))),

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wirecat/cli-base",
-  "version": "0.70.0",
+  "version": "0.71.0",
   "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",