@wirecat/cli-base 0.72.0 → 0.74.0

package/CHANGELOG.md

@@ -8,6 +8,25 @@ 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.74.0 — 02.11.2026
+
+### Added
+
+- **`--compact`, a shared output switch for one line per item (WC-OUT-24).** The vocabulary lists it with role
+  `output`, and `COMPACT_FLAG` from `@wirecat/cli-base/standards` holds its name, so a CLI builds its option from
+  that one place. The rule says what the text keeps from the JSON answer: the reference first, the text last and cut
+  with `…(+N)`, and `page`, `missing`, `next` and `meta.complete` as lines that start with `# `. cli-core's runner
+  draws it; a CLI on its own `run()` has nothing to change until it offers the switch.
+
+## 0.73.0 — 02.11.2026
+
+### Added
+
+- **The verb `remind`.** It tells the owner once about what starts soon: it prints it, or runs the owner's own
+  program for it. gcal's `events remind` uses it, for a scheduler (cron, a systemd timer) to run every few minutes, as
+  gcalcli's `remind` is run. Before, no verb said "tell me once": `watch` keeps a process running, and `send` writes
+  to a chat.
+
 ## 0.72.0 — 02.11.2026
 
 ### Added

package/dist/standards/flags-how.js

@@ -1,3 +1,4 @@
+import { COMPACT_FLAG } from "./output.js";
 export const HOW_FLAGS = [
     {
         name: "--limit",
@@ -84,6 +85,12 @@ export const HOW_FLAGS = [
         type: "switch",
         meaning: "each item as its reference, title, time and excerpt only",
     },
+    {
+        name: COMPACT_FLAG,
+        role: "output",
+        type: "switch",
+        meaning: "one line per item, built from the same answer as --json, with its paging and next steps as # lines",
+    },
     {
         name: "--chart-kind",
         value: "<messages|active|membership>",

package/dist/standards/index.d.ts

@@ -1,6 +1,6 @@
 export { EFFECT_LEVELS, type EffectLevel, type Effects, effectsSchema, writes } from "./effects.js";
 export { BASE_REASONS, COMMON_DETAILS, CRASH_CODE, CRASH_REASON, defineReasons, type ErrorObject, type ErrorReason, errorObjectSchema, } from "./errors.js";
 export { defineLogEvents, isContentKey, LOG_ATTRIBUTE_KEYS, LOG_EVENTS, LOG_SEVERITIES, type LogEvent, type LogRecord, type LogSeverity, logAttributesJsonSchema, logEventProblems, logRecordSchema, traceIdOf, } from "./log.js";
-export { clockMeta, type Issue, type ItemEnvelope, isoTime, issueSchema, itemEnvelopeSchema, jsonlEndSchema, jsonlItemSchema, jsonlOf, type ListEnvelope, listEnvelopeSchema, localTime, MAX_NEXT_STEPS, type Meta, type Missing, metaSchema, missingSchema, type NextStep, nextStepSchema, type Page, pageSchema, reference, type Total, totalSchema, } from "./output.js";
+export { COMPACT_FLAG, clockMeta, type Issue, type ItemEnvelope, isoTime, issueSchema, itemEnvelopeSchema, jsonlEndSchema, jsonlItemSchema, jsonlOf, type ListEnvelope, listEnvelopeSchema, localTime, MAX_NEXT_STEPS, type Meta, type Missing, metaSchema, missingSchema, type NextStep, nextStepSchema, type Page, pageSchema, reference, type Total, totalSchema, } from "./output.js";
 export { fill, jsonSchemaOf, RegistryError } from "./registry.js";
 export { defineSteps, SAME_COMMAND, STEPS, type StepDefinition, type StepInput, type StepTarget, stepOf, } from "./steps.js";

package/dist/standards/index.js

@@ -1,6 +1,6 @@
 export { EFFECT_LEVELS, effectsSchema, writes } from "./effects.js";
 export { BASE_REASONS, COMMON_DETAILS, CRASH_CODE, CRASH_REASON, defineReasons, errorObjectSchema, } from "./errors.js";
 export { defineLogEvents, isContentKey, LOG_ATTRIBUTE_KEYS, LOG_EVENTS, LOG_SEVERITIES, logAttributesJsonSchema, logEventProblems, logRecordSchema, traceIdOf, } from "./log.js";
-export { clockMeta, isoTime, issueSchema, itemEnvelopeSchema, jsonlEndSchema, jsonlItemSchema, jsonlOf, listEnvelopeSchema, localTime, MAX_NEXT_STEPS, metaSchema, missingSchema, nextStepSchema, pageSchema, reference, totalSchema, } from "./output.js";
+export { COMPACT_FLAG, clockMeta, isoTime, issueSchema, itemEnvelopeSchema, jsonlEndSchema, jsonlItemSchema, jsonlOf, listEnvelopeSchema, localTime, MAX_NEXT_STEPS, metaSchema, missingSchema, nextStepSchema, pageSchema, reference, totalSchema, } from "./output.js";
 export { fill, jsonSchemaOf, RegistryError } from "./registry.js";
 export { defineSteps, SAME_COMMAND, STEPS, stepOf, } from "./steps.js";

package/dist/standards/output.d.ts

@@ -1,6 +1,8 @@
 import * as v from "valibot";
 /** At most two next steps per answer: the one to take, then one alternative. */
 export declare const MAX_NEXT_STEPS = 2;
+/** The switch for one line per item (WC-OUT-24). Its name is still the owner's to settle, so it lives in one place. */
+export declare const COMPACT_FLAG = "--compact";
 export declare const isoTime: v.SchemaWithPipe<readonly [v.StringSchema<undefined>, v.IsoTimestampAction<string, "an ISO 8601 time in UTC">, v.EndsWithAction<string, "Z", "an ISO 8601 time in UTC, ending in `Z`">]>;
 /** The same moment on the wall clock of a zone, with its offset: `2026-11-02T16:03:00.000+01:00` (WC-TIME-2). */
 export declare const localTime: v.SchemaWithPipe<readonly [v.StringSchema<undefined>, v.RegexAction<string, "an ISO 8601 time with its offset">]>;

package/dist/standards/output.js

@@ -3,6 +3,8 @@ import { errorCodes } from "../errors.js";
 import { dottedId, text } from "./registry.js";
 /** At most two next steps per answer: the one to take, then one alternative. */
 export const MAX_NEXT_STEPS = 2;
+/** The switch for one line per item (WC-OUT-24). Its name is still the owner's to settle, so it lives in one place. */
+export const COMPACT_FLAG = "--compact";
 export const isoTime = v.pipe(v.string(), v.isoTimestamp("an ISO 8601 time in UTC"), v.endsWith("Z", "an ISO 8601 time in UTC, ending in `Z`"));
 /** The same moment on the wall clock of a zone, with its offset: `2026-11-02T16:03:00.000+01:00` (WC-TIME-2). */
 export const localTime = v.pipe(v.string(), v.regex(/^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}\.\d{3}[+-]\d{2}:\d{2}$/, "an ISO 8601 time with its offset"));

package/dist/standards/vocabulary.js

@@ -164,6 +164,7 @@ const verbs = [
     ["vote", "answer a poll"],
     ["answer", "reply to a button someone pressed under a bot's message"],
     ["respond", "answer an invitation: accept, tentatively accept or decline it"],
+    ["remind", "tell the owner once about what starts soon: print it, or run the owner's own program for it"],
     ["press", "press a button under a bot's message; the bot sees who pressed it"],
     ["action", "show what a bot is doing in a chat, such as typing, for a few seconds"],
     ["watch", "follow new events as they come, and keep them"],

package/docs/standards/README.md

@@ -30,7 +30,7 @@ the four steps that need a person. A new CLI is ready for its first release when
 | [Toolchain](toolchain.md) | `TOOL` | 20 | TypeScript, Biome, grit plugins, size caps, import cycles, spelling, Markdown, Go |
 | [Layout](layout.md) | `LAY` | 10 | Repository layout, entry points, exports, file size, one job per file, splitting a unit, the bundled bin |
 | [Commands](commands.md) | `CMD` | 29 | Paths, vocabulary, flags, arguments, effects, lifetime, query, help, external references, joining `wcat` |
-| [Output](output.md) | `OUT` | 23 | Data on stdout only, envelopes, errors, exit codes, partial answers, projection |
+| [Output](output.md) | `OUT` | 24 | Data on stdout only, envelopes, errors, exit codes, partial answers, projection |
 | [MCP](mcp.md) | `MCP` | 13 | The MCP tools, how they come from commands, what each permission shows |
 | [Accounts](accounts.md) | `ACCT` | 12 | The explicit profile, reads across accounts, scope flags, linked identities, sign-in commands |
 | [Permissions](permissions.md) | `PERM` | 22 | Levels, keys, defaults, hard limits, the write guard and its journal |

package/docs/standards/commands.md

@@ -165,8 +165,9 @@ catalogue and parity manifest stay in cli-core
 
 - **Why:** a script that works with one CLI works with the next.
 - **Enforced by:** review only.
-- **Example:** `--json` and `--jsonl` choose machine output. `--quiet` turns diagnostics off, but a failure is still
-  said. `-v` and `-vv` add detail, `-V` prints the version, `--trace` writes request diagnostics, `--debug` adds the
+- **Example:** `--json` and `--jsonl` choose machine output, `--compact` one line per item
+  ([WC-OUT-24](output.md#wc-out-24--offer-a-compact-text-form-built-from-the-same-answer)). `--quiet` turns
+  diagnostics off, but a failure is still said. `-v` and `-vv` add detail, `-V` prints the version, `--trace` writes request diagnostics, `--debug` adds the
   whole failure record. `--timeout <duration>` bounds the command. `--no-input` never prompts. `--dry-run` previews.
   `--yes` answers the question an `ask` permission level puts before a write.
 - **Exceptions:** none.
@@ -176,8 +177,8 @@ catalogue and parity manifest stay in cli-core
 
 - **Why:** a prompt in a pipe or under an agent waits for ever.
 - **Enforced by:** review only.
-- **Example:** `--no-input`, `--json`, `--jsonl`, a `CI` variable or a stdout that is not a terminal each switch prompts
-  and browser logins off. Data piped on stdin for an explicit command still works. Buffered stdin stops at
+- **Example:** `--no-input`, `--json`, `--jsonl`, `--compact`, a `CI` variable or a stdout that is not a terminal
+  each switch prompts and browser logins off. Data piped on stdin for an explicit command still works. Buffered stdin stops at
   `--max-input-bytes` (16 MiB by default).
 - **Exceptions:** none. `--yes` confirms a write; it never lifts a `deny`
   ([WC-PERM-10](permissions.md#wc-perm-10--a-flag-confirms-it-never-grants)).

package/docs/standards/output.md

@@ -288,6 +288,21 @@ Three things follow from it:
 - **Exceptions:** none.
 - **Applies to:** all CLIs. **Since:** cli-base 0.43.1. **Rulings:** none.
 
+### WC-OUT-24 · Offer a compact text form built from the same answer
+
+- **Why:** an agent pays for every key, quote and repeated chat reference it reads. One line per item says the same
+  thing in about half the bytes, with no script to format it.
+- **Enforced by:** `cli-core: src/cli/compact.test.ts`.
+- **Example:** `tg personal messages list 111 --compact` prints one line per item, columns joined by ` · `, the
+  reference first and the free text last. When every reference shares a prefix, a header line names it once and the
+  rows print only the tail. Text is kept on one line, with control and direction characters made visible, and cut at
+  400 characters with `…(+N)`; `--full` keeps it whole. What JSON says beside the items is kept as lines that start
+  with `# `: `# more:` from `page`, `# missing:` per `missing` entry, `# next:` per next step and `# complete: false`.
+  A row never starts with `# `, so no message text can pass for one of them. The footer goes to stdout with the
+  rows. `--compact` is refused with `--json`, `--jsonl` and `--brief`, never prompts, and exits as JSON would.
+- **Exceptions:** MCP tools answer JSON.
+- **Applies to:** CLIs that run on cli-core's `run()`. **Since:** cli-base 0.74.0. **Rulings:** NEED-2131.
+
 ## Sources
 
 These documents explain the rules on this page in more detail. Where one of them disagrees with this page, this page

package/package.json

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