@wirecat/cli-base 0.76.0 → 0.77.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.77.0 — 05.11.2026
+
+### Added
+
+- **The vocabulary has cli-core's schedule words and memo's `findings`, as the commands name them.** The resource
+  `schedule` (a profile's saved timers; the tool's own background work stays `jobs`), the verbs `agent` and `command`
+  (save a timer that starts an agent, or runs one of the tool's commands) and `exec` (what the timer itself starts;
+  a person uses `run`), and the collection `findings` (what an agent read in mail, staged for the owner; what it
+  proposes to do stays `actions`). The owner ruled to add the words as they are rather than rename the commands,
+  so the command lint checks them instead of skipping them. What to watch for: every CLI that mounts
+  `schedule` (tg, max, gcal, mail, memo, cli-core itself) and memo's `mail findings` has these in
+  `lint/baseline/unknown-verb.json` and `unknown-resource.json`; they are stale after the bump and fail the lint
+  until removed (WC-TOOL-16).
+
 ## 0.76.0 — 04.11.2026
 
 ### Changed — may break callers

package/dist/standards/vocabulary.js

@@ -192,6 +192,10 @@ const verbs = [
     ["move", "move a thing to another place in the source: a file to a folder, an event to a calendar"],
     ["copy", "copy a file in the source"],
     ["run", "run a saved job once, now, as its timer would"],
+    ["exec", "what a timer itself starts: one saved schedule, from its file; a person uses run"],
+    // schedule's creators are named for what the timer starts; the owner kept these names over `create --kind`.
+    ["agent", "save a timer that starts an agent with a prompt, read-only; a verb under schedule, never a resource"],
+    ["command", "save a timer that runs one of this tool's own commands; a verb under schedule"],
     ["claim", "take a thing for a while so no other agent works it at once; the claim lapses by itself"],
     ["release", "give back what claim took, before it lapses"],
     ["merge", "fold a duplicate into the thing that stays; nothing is deleted"],
@@ -262,6 +266,10 @@ const collections = [
     ["recordings", "the files a provider recorded of a meeting"],
     ["jobs", "work this tool runs in the background or on a timer"],
     ["actions", "what an agent proposes to do; the owner confirms or rejects each"],
+    [
+        "findings",
+        "what an agent read in stored mail, staged in batches with citations; nothing is recorded until the owner confirms. What it proposes to do is actions",
+    ],
     ["agents", "the agents whose actions are recorded in the shared store"],
     ["reminders", "scheduled notices about stored work, claimed and acknowledged with delivery receipts"],
     ["key-documents", "selected source documents that a project keeps as its starting references"],
@@ -304,6 +312,10 @@ const singulars = [
     ["privacy", "who may find, see, call or add the account"],
     ["metadata", "a profile's cached source attributes"],
     ["auth", "the credentials a bot profile uses: its token and the secrets beside it"],
+    [
+        "schedule",
+        "a profile's timers the owner saved, each running a command of this tool or an agent; the tool's own background work is jobs",
+    ],
 ];
 const views = [
     ["tree", "the parent and child hierarchy of stored sources"],

package/docs/standards/README.md

@@ -39,7 +39,7 @@ the four steps that need a person. A new CLI is ready for its first release when
 | [Store](store.md) | `STORE` | 14 | Store areas, account scope, migrations, test isolation |
 | [Data model](data-model.md) | `DATA` | 9 | Core entities, entities and source records, `external_id`, field names, links and duplicates, files, calendar entries |
 | [Testing](testing.md) | `TEST` | 17 | Sandbox, no network, no real waits, leak tests, coverage, contracts, test matrix, parity |
-| [Security](security.md) | `SECR` | 23 | Secrets, logs, keyring, argv, error text, untrusted text, scanners, workflow hardening, reporting, OAuth sign-in, meeting secrets, keyring in moved-folder runs |
+| [Security](security.md) | `SECR` | 24 | Secrets, logs, keyring, argv, error text, untrusted text, scanners, workflow hardening, reporting, OAuth sign-in and which app it uses, meeting secrets, keyring in moved-folder runs |
 | [Documents](docs.md) | `DOC` | 21 | User pages and developer pages, generated pages, current facts, changelog, repository page |
 | [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` | 15 | `bin/release`, the release lock, versions, the owner's yes, trusted publishing |

package/docs/standards/commands.md

@@ -22,6 +22,13 @@ A "messenger CLI" below is one of the CLIs that share cli-core's messenger comma
 catalogue and parity manifest stay in cli-core
 [`docs/dev/STANDARD.md`](https://github.com/WireCatLabs/cli-core/blob/main/docs/dev/STANDARD.md).
 
+### Who follows these rules today
+
+WC-CMD-30: cli-core's shared settings declare every shared scalar setting and give `config migrate`, so tg, max, wa,
+mail and gcal follow once they take the cli-core release after 0.561.0. Their own settings (max's `serve` and
+`transcribe_model`, for example) are not declared yet. drive's first-run file holds them all, but drive's own
+`config` has no `migrate` and its writes do not fill the file. zm declares nothing yet.
+
 ## Paths and words
 
 ### WC-CMD-1 · Build every path as resource first, then a verb or a view
@@ -402,11 +409,7 @@ plain read never rewrites the file.
   it as `false (default)`.
 - **Exceptions:** lists and sections that need fields no default can give (accounts, folders, permissions) get no
   placeholder. A secret is never declared, since `config show` prints every value. A setting whose absence means
-  something no value says (no timeout, the terminal decides colour) is not declared either. Known gaps, as of
-  2026-11-03: cli-core's shared settings declare every shared scalar setting and give `config migrate`, so tg, max,
-  wa, mail and gcal follow once they take the cli-core release after 0.561.0; their own settings (max's `serve` and
-  `transcribe_model`, for example) are not declared yet. drive's first-run file holds them all, but drive's own
-  `config` has no `migrate` and its writes do not fill the file. zm declares nothing yet.
+  something no value says (no timeout, the terminal decides colour) is not declared either.
 - **Applies to:** all CLIs. **Since:** cli-base 0.76.0. **Rulings:** none.
 
 ## References

package/docs/standards/permissions.md

@@ -194,8 +194,12 @@ An agent never deletes a message for everyone, and never ends the owner's other
 ### WC-PERM-12 · `<PREFIX>_READ_ONLY` refuses every write
 
 When this variable is set, every write answers `permission_error`, whatever `permissions` or a flag say. So does a
-command that writes only on this machine, unless cli-core marks it `destroysNothing`; a new local write is refused
-until someone marks it. Logging in or out and a change to what a later run may do (a schedule, a setting, the
+command that writes only on this machine, unless cli-core marks it `destroysNothing` or it is of the propose tier; a
+new local write is refused until someone marks it. The propose tier is a closed list, cli-core's `PROPOSE_COMMANDS`:
+`messages acknowledge` and `mail findings add`. A command passes as a proposal only when it is marked `proposesOnly`
+and its path ends with a listed one; it stages something the owner decides, or moves its caller's own processing
+mark, and nothing else. Adding a path widens what a read-only agent can write, so each addition is reviewed on its
+own. Logging in or out and a change to what a later run may do (a schedule, a setting, the
 recipient list) are refused too. A `--dry-run` preview still runs.
 
 - **Why:** an unattended agent needs one switch that the config file and `--permission` cannot undo, and that also
@@ -209,7 +213,8 @@ recipient list) are refused too. A `--dry-run` preview still runs.
   other command, an MCP session included (cli-core 0.343.0). Local writes marked `destroysNothing` run: what the store
   rebuilds (`store reindex`, `mentions rebuild`), a new file (`store backup`, `store export`, `stats charts`), and the
   task writes the follow-ups skill makes on a timer, where `tasks close` only suggests the close to the owner.
-  Embedding and analysis on this machine run; sending text to an outside service for them is refused.
+  A read-only scheduled mail agent stages what it read with `mail findings add` and moves its mark with
+  `messages acknowledge`; nothing it staged is recorded until the owner confirms. Embedding and analysis on this machine run; sending text to an outside service for them is refused.
 - **Applies to:** messenger CLIs. **Since:** cli-base 0.41.0. **Rulings:** none.
 
 ### WC-PERM-13 · Every write passes the write guard before it leaves

package/docs/standards/security.md

@@ -373,6 +373,46 @@ store and runs no search. A CLI declares its provider and may replace any step.
   owner, 2026-10-30 (share the keyring entry, do not multiply it); owner, 2026-10-31 (do not replace it: a test of a
   new session writes a temporary entry and cleans it up).
 
+### WC-SECR-25 · Sign in with WireCat's app by default, and let the owner choose their own
+
+Every provider sign-in uses WireCat's OAuth app unless the owner names another. That app is read from
+`constants.json` ([WC-ARCH-23](architecture.md#wc-arch-23--a-value-that-ships-with-the-package-lives-in-the-layers-constantsjson)):
+cli-core's layer for Google and Microsoft, a tool's own layer for a provider only that tool uses, such as Zoom.
+
+- **Which app, first match wins:**
+  1. `session start --client-file <json>` or `--client-id <id>`;
+  2. `<TOOL>_<PROVIDER>_CLIENT_ID`, plus `<TOOL>_<PROVIDER>_CLIENT_SECRET` where the provider needs a secret. A
+     secret without an id is a `configuration_error`;
+  3. the account's config key `<provider>.client_id`;
+  4. WireCat's app.
+- **Stored with the account.** The app a sign-in used is saved with that account, so refresh and revoke use the same
+  app even after the default changes.
+- **Reported by `doctor`,** per provider: `oauth_client: { client: "wirecat" | "own" | null, source: "flag" | "env" |
+  "config" | "constants" | null }`. A null client comes with a one-line reason.
+- **Desktop.** A sign-in from wirecat-desktop offers WireCat's app, with a "Use my own app" choice that writes the same
+  override as step 2 or 3.
+- **A shipped secret** is allowed only where the provider documents the client as public, and the tool's gitleaks
+  allowlist names it by value ([WC-SECR-17](#wc-secr-17--a-gitleaks-rule-covers-each-secret-shape-a-cli-handles)).
+  Google's token endpoint refuses a Desktop app client without its secret (tested 2026-11-04), although
+  [Google's guide](https://developers.google.com/identity/protocols/oauth2/native-app) calls desktop apps public
+  clients that cannot keep secrets. So a Google app ships its id and secret; a Microsoft public client ships its id
+  only.
+- **A provider with no WireCat app yet** says so in `doctor` (a null client and its reason) and in its docs, and still
+  keeps the order, the stored app and the report above.
+
+- **Why:** an owner should sign in without creating an app first, and still be able to use their own; a token
+  refreshed with a different app than the one that issued it fails.
+- **Enforced by:** `cli-core: src/oauth/client-file.test.ts`.
+- **Example:** `gcal personal session start` uses WireCat's Google app and `doctor` reports
+  `{ client: "wirecat", source: "constants" }`; with `GCAL_GOOGLE_CLIENT_ID` and `GCAL_GOOGLE_CLIENT_SECRET` set it
+  reports `{ client: "own", source: "env" }`.
+- **Exceptions:** known gaps, as of 2026-11-04: mail has no WireCat default for Google; zoom has no WireCat app until
+  Zoom Marketplace approves one; no tool reads the per-account `google.client_id` key yet; mail's Microsoft key is
+  named `microsoft_client_id`; `doctor` reports no `source` yet. gcal's default came from a file CI wrote from a
+  secret; cli-core's `constants.json` replaces it from its next release.
+- **Applies to:** every CLI that signs in with OAuth, and wirecat-desktop. **Since:** cli-base 0.76.1.
+  **Rulings:** owner, 2026-11-04.
+
 ## 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.76.0",
+  "version": "0.77.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",