@wirecat/cli-base 0.51.0 → 0.51.1

package/CHANGELOG.md

@@ -8,6 +8,16 @@ 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.51.1 — 24.10.2026
+
+### Fixed
+
+- The shared vocabulary recognizes `--draft` as a switch that saves text for review without sending. Enabling an adapter’s draft capability no longer creates an unknown-option-role lint failure.
+
+### Removed
+
+- **No wait between releases and no weekly limit on breaking changes** (`WC-REL-8`, [Releases](docs/standards/releases.md)). A messenger CLI no longer waits two hours after its last version, and a shared library may ship a change that makes the CLIs change their code at any time. `WC-REL-9` is merged into `WC-REL-8`. The release lock stays. Nothing changes in code.
+
 ## 0.51.0 — 24.10.2026
 
 ### Added

package/dist/standards/flags-how.js

@@ -291,6 +291,12 @@ export const HOW_FLAGS = [
         type: "duration",
         meaning: "how old a stored snapshot may be and still count as fresh",
     },
+    {
+        name: "--draft",
+        role: "mode",
+        type: "switch",
+        meaning: "save text for the owner to review and send, without sending a message",
+    },
     { name: "--md", role: "mode", type: "switch", meaning: "the text is the messenger's Markdown" },
     { name: "--no-backup", role: "mode", type: "switch", meaning: "do not back the file up before deleting it" },
     { name: "--no-input", role: "mode", type: "switch", meaning: "never prompt or open an interactive login" },

package/docs/standards/README.md

@@ -39,7 +39,7 @@ rules it keeps. A new CLI is ready for its first release when every check under
 | [Security](security.md) | `SECR` | 20 | Secrets, logs, keyring, argv, error text, untrusted text, scanners, workflow hardening, reporting |
 | [Documents](docs.md) | `DOC` | 20 | User pages and developer pages, generated pages, current facts, changelog |
 | [Comparisons](comparisons.md) | `CMP` | 11 | Which tools a comparison page lists, rows as user tasks, agents and safety, where others are better, proof of marks |
-| [Releases](releases.md) | `REL` | 16 | `bin/release`, the release lock, versions, release reports, trusted publishing |
+| [Releases](releases.md) | `REL` | 15 | `bin/release`, the release lock, versions, release reports, trusted publishing |
 | [CI](ci.md) | `CI` | 12 | Hooks, the pull request budget, full validation, monthly runs |
 | [Time](time.md) | `TIME` | 6 | UTC in the store and in answers, the zone at input and display edges, date-only filters, tests in another zone |
 | [Style](style.md) | `STYLE` | 10 | Comments, TypeScript habits, commit messages |

package/docs/standards/new-cli.md

@@ -92,8 +92,8 @@ whatsapp-cli is the worked example: it has every file below. Compare with it whe
 8. **`SECURITY.md`**: how to report a vulnerability, linking cli-testing's security method. See
    [Security](security.md).
 9. **`bin/release`**, **`release.yml`** and a release skill, copied from the nearest CLI. `bin/release` takes the
-   release lock (WC-REL-3) and npm's trusted publisher settings name `release.yml`. A messenger CLI also waits two
-   hours between releases and checks a signed release report (WC-REL-8, WC-REL-10). See [Releases](releases.md).
+   release lock (WC-REL-3) and npm's trusted publisher settings name `release.yml`. A messenger CLI also checks a signed
+   release report (WC-REL-10). See [Releases](releases.md).
 10. **`src/version.ts`** kept in step with `package.json`. Proved by: `pnpm version:check`.
 
 ## Done when

package/docs/standards/releases.md

@@ -88,29 +88,17 @@ on the [CI](ci.md) page.
 - **Exceptions:** a pre-release version (`0.41.0-rc.1`) is chosen by hand.
 - **Applies to:** all CLIs and shared libraries. **Since:** cli-base 0.41.0. **Rulings:** none.
 
-### WC-REL-8 · A messenger CLI waits two hours between releases; a shared library does not wait
+### WC-REL-8 · Any package may release at any time
 
-- **Why:** a broken CLI release must be noticed before the next one lands on top of it. Every CLI waits for a library
-  release, so a gap there only delays them.
-- **Enforced by:** `<app>: bin/release`.
-- **Example:** tg-cli, max-cli and whatsapp-cli's `bin/release` refuse to start within two hours of the last version
-  on npm. cli-base and cli-core release one after another with no gap.
-- **Exceptions:** memo, drive and zoom have no gap in their `bin/release` today.
-- **Applies to:** messenger CLIs (gap); shared libraries (no gap). **Since:** cli-base 0.41.0. **Rulings:** NEED-854.
-
-### WC-REL-9 · A change to a stable shared-library export that makes a CLI change its code ships at most once a week
-
-- **Why:** the limit keeps the CLIs from chasing versions; a change that no CLI has to follow gives them nothing to
-  chase.
-- **Enforced by:** `cli-core: parity.yml` (it decides which changes count; review keeps the week).
-- **Example:** cli-core's parity jobs build tg-cli, max-cli and whatsapp-cli from their `main` against every pull
-  request. A change to a stable export counts unless all three jobs pass with each CLI's `main` unchanged; its
-  changelog still lists it under "Changed — may break callers" for outside users. It counts when a job fails, when it
-  passes only against a CLI branch made for the change, and when it compiles but changes behaviour that any CLI must
-  adapt to. Parity cannot see that last case, so when in doubt the change counts. Gather the changes that count into
-  one release a week, and bump the library in every CLI that uses it on the same day.
-- **Exceptions:** none.
-- **Applies to:** shared libraries. **Since:** cli-base 0.41.0. **Rulings:** NEED-473, NEED-1552.
+- **Why:** a wait between releases or a weekly limit on breaking changes only delays a fix; the owner removed both
+  limits on 2026-10-24.
+- **Enforced by:** review only.
+- **Example:** tg-cli can release an hour after its last version, and cli-core can ship a breaking change on the same
+  day as the previous one. Bump the library in every CLI that uses it on the day it ships.
+- **Exceptions:** none. The release lock (WC-REL-3) still keeps two releases on one machine from running at once.
+- **Applies to:** all CLIs and shared libraries. **Since:** cli-base 0.52.0. **Rulings:** NEED-1741.
+
+### WC-REL-9 · Merged into [WC-REL-8](#wc-rel-8--any-package-may-release-at-any-time)
 
 ### WC-REL-10 · A messenger CLI is released only with a release report the owner signed for that commit
 

package/package.json

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