@wirecat/cli-base 0.69.0 → 0.71.0

package/CHANGELOG.md

@@ -8,6 +8,39 @@ 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
+
+- **Mail words in the vocabulary: the `drafts` resource and `--cc`, `--bcc`, `--reply-all`.** mail-cli saves drafts
+  in a mailbox's Drafts folder (`mail <profile> drafts list|create|update|delete`) and addresses e-mail with copies;
+  the command lint reported each as a word it did not know.
+- **`--to` takes a chat or an e-mail address, `--subject` takes a reference or a subject line.** The owner ruled
+  that mail shares these two words with the messengers and notes instead of renaming them. `--to` is now
+  `<chat|address>`, a `string` (was an `id`); `--subject` is `<ref|text>`. The meaning per domain is in each flag's
+  text, so `flag-two-meanings` stops reporting mail's use. Mail-cli can drop its overrides for both.
+
+### Fixed
+
+- **mail is compared in its own parity group, `mail-shared`, which leaves out `search`.** mail's `search messages` is
+  cli-core's mail search, a different command from the messengers' under the same path, and `audit --complete` took
+  its twenty-odd differences as inherited. mail is compared on every other shared root, and moves back into `all`
+  once its search is aligned with the messengers' or renamed.
+
 ## 0.69.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/audit.js

@@ -68,19 +68,35 @@ export const defineParityGroups = (input) => parseRegistry("parity groups", v.ar
             .map((entry) => `${group.name}: "${entry.target}" has \`absent\`, which measures the values itself; drop \`expected\``),
     ]),
 ]);
+const MEMO_HAS_NO_PROFILES = [
+    "mcp serve",
+    "mcp revoke",
+    "mcp server start",
+    "mcp server status",
+    "mcp server stop",
+].map((path) => ({
+    rule: "same-path-contract",
+    target: `${path} --profiles`,
+    absent: "memo",
+    reason: "memo has no profiles: it reads other CLIs' stores and selects their accounts with --source and --account " +
+        "(https://github.com/WireCatLabs/cli-base/issues/390)",
+}));
 export const PARITY_GROUPS = defineParityGroups([
     { name: "messengers", members: ["tg", "max"], covers: "tree", differences: [] },
     {
         name: "all",
-        members: ["tg", "max", "memo", "drive", "zm", "wa", "mail"],
+        members: ["tg", "max", "memo", "drive", "zm", "wa"],
         covers: ["commands", "doctor", "skill", "mcp", "upgrade", "search", "notes", "meetings"],
-        differences: ["mcp serve", "mcp revoke", "mcp server start", "mcp server status", "mcp server stop"].map((path) => ({
-            rule: "same-path-contract",
-            target: `${path} --profiles`,
-            absent: "memo",
-            reason: "memo has no profiles: it reads other CLIs' stores and selects their accounts with --source and --account " +
-                "(https://github.com/WireCatLabs/cli-base/issues/390)",
-        })),
+        differences: MEMO_HAS_NO_PROFILES,
+    },
+    // mail's `search messages` is cli-core's mail search, not the messengers' command: --complete took their 20-odd
+    // differences as inherited (https://github.com/WireCatLabs/cli-base/issues/390). mail is compared everywhere else
+    // and moves back into "all" once its search is aligned with the messengers' or renamed.
+    {
+        name: "mail-shared",
+        members: ["tg", "max", "memo", "drive", "zm", "wa", "mail"],
+        covers: ["commands", "doctor", "skill", "mcp", "upgrade", "notes", "meetings"],
+        differences: MEMO_HAS_NO_PROFILES,
     },
     // gcal is compared on what it already shares with every CLI; doctor, mcp, search and skill wait until the published
     // CLIs agree there (https://github.com/WireCatLabs/cli-base/issues/390), then gcal moves back into "all".

package/dist/standards/flags-mail.d.ts

@@ -0,0 +1,2 @@
+import type { VocabularyFlag } from "./vocabulary.js";
+export declare const MAIL_FLAGS: VocabularyFlag[];

package/dist/standards/flags-mail.js

@@ -0,0 +1,22 @@
+export const MAIL_FLAGS = [
+    {
+        name: "--cc",
+        value: "<address>",
+        role: "value",
+        type: "string",
+        meaning: "an e-mail address that gets a copy; repeat it for more",
+    },
+    {
+        name: "--bcc",
+        value: "<address>",
+        role: "value",
+        type: "string",
+        meaning: "an e-mail address that gets a blind copy; repeat it for more",
+    },
+    {
+        name: "--reply-all",
+        role: "value",
+        type: "switch",
+        meaning: "with --reply-to, an e-mail reply also goes to everyone the message went to",
+    },
+];

package/dist/standards/flags-what.js

@@ -442,7 +442,14 @@ export const WHAT_FLAGS = [
         meaning: "keep a token an operation returns only in this bot profile's keyring; never print it",
     },
     { name: "--task", value: "<id>", role: "target", type: "id", meaning: "a task, by id" },
-    { name: "--to", value: "<chat>", role: "target", type: "id", meaning: "the chat it goes to" },
+    {
+        name: "--to",
+        value: "<chat>",
+        role: "target",
+        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",
         value: "<name>",
@@ -892,7 +899,8 @@ export const WHAT_FLAGS = [
         value: "<ref>",
         role: "value",
         type: "string",
-        meaning: "what it is about, as a reference",
+        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

@@ -1,6 +1,7 @@
 import * as v from "valibot";
 import { CALENDAR_FLAGS } from "./flags-calendar.js";
 import { HOW_FLAGS } from "./flags-how.js";
+import { MAIL_FLAGS } from "./flags-mail.js";
 import { WHAT_FLAGS } from "./flags-what.js";
 import { duplicates, parseRegistry, text, word } from "./registry.js";
 export const FLAG_TYPES = [
@@ -48,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")))),
@@ -212,6 +218,7 @@ const collections = [
     ["chats", "conversations in a messenger"],
     ["contacts", "identities in a messenger's contact list"],
     ["messages", "posts in a messenger chat, or emails"],
+    ["drafts", "e-mails saved in a mailbox's Drafts folder, written and not sent"],
     ["polls", "polls in a chat"],
     ["reactions", "reactions to a message"],
     ["recipients", "who a message goes to"],
@@ -359,5 +366,5 @@ export const VOCABULARY = defineVocabulary({
     ],
     views: views.map(([entry, meaning]) => ({ word: entry, meaning })),
     roots: roots.map(([entry, meaning]) => ({ word: entry, meaning })),
-    flags: [...HOW_FLAGS, ...WHAT_FLAGS, ...CALENDAR_FLAGS],
+    flags: [...HOW_FLAGS, ...WHAT_FLAGS, ...CALENDAR_FLAGS, ...MAIL_FLAGS],
 });

package/package.json

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