@wirecat/cli-base 0.64.0 → 0.65.1

package/CHANGELOG.md

@@ -8,6 +8,137 @@ 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.65.1 — 29.10.2026
+
+### Fixed
+
+- **`Credentials` with `isolated` no longer writes the system keyring** ([WC-SECR-24](docs/standards/security.md), new:
+  a run with moved folders never writes the owner's keyring). A per-folder keyring service (`<app>:<folder>`) was
+  leaving one copy of a sign-in per temp folder. A secret goes to the private file in the moved config folder
+  instead; one saved in the keyring before is still read, so an existing per-folder sign-in keeps working until its
+  next save moves it to the file. A test passing its own keyring (`memoryKeyring()`) is unchanged.
+- **`cli-dev changelog restore` no longer fails a package's first release.** With no `v<x.y.z>` tag yet it says there
+  is nothing to restore and exits 0; `bin/release` stopped at "no v<x.y.z> tag to compare the changelog with".
+
+## 0.65.0 — 27.10.2026
+
+### Added
+
+- **Calendar words for moving an event and for "this and all following".** Flag `--following` (`target`, switch):
+  this occurrence and every later one of a repeating event (`events update|delete --following`), beside `--series`.
+  `--scope` already means personal or work, so it is not reused. Flag `--to-calendar <id>` (`target`, id): the
+  calendar an event moves to (`events move --to-calendar`); `--calendar` keeps its meaning, the calendar the event is
+  on. The verb `move` now says what moves in general: a file to a folder, an event to a calendar. cli-core's shared
+  calendar commands use all three; gcal-cli carries `lint/overrides.json` entries for them until this release.
+- **Every CLI that signs in has `session start`, `session status`, `session end` and a profile-free `session list`.**
+  [WC-ACCT-12](docs/standards/accounts.md#wc-acct-12--sign-in-is-session-start-status-and-end-and-session-list-names-the-profiles)
+  is the owner's ruling: `status` says whether one profile is signed in, `list` which profiles exist. Each
+  CLI's missing commands are listed as known gaps: tg, max and wa lack `session status` and list profiles with
+  `account list`; drive lacks `session status`; gcal lacks `session list`; zm lacks `session end` and `session list`;
+  memo has no `session` group.
+- **A sync spends a request budget sized to its deadline and says how to continue.**
+  [WC-LIFE-16](docs/standards/lifecycle.md#wc-life-16--a-sync-spends-a-request-budget-sized-to-its-deadline-and-its-answer-says-how-to-continue)
+  describes what cli-core 0.464.0 (cli-core #2118) builds for the calendar sync: `floor((deadline − margin) /
+  requestMs)` requests, one `requestMs` per CLI, `--max-pages` only lowering it, a partial stop that exits 0 with the
+  exact command to continue, and progress in the sync's status command. The other syncs and gcal's own `requestMs`
+  are listed as gaps.
+
+- **The command vocabulary has the verbs `serve` (run a server in this process and answer its clients until stopped)
+  and `revoke` (take back what was granted, so it stops working).** cli-core 0.463.0 names the MCP server
+  `mcp serve` and gives forgetting browser logins its own command, `mcp revoke`; `revoke` also covers
+  `chats link revoke` and the `consents revoke` commands that were baselined as unknown verbs.
+
+### Changed — may break callers
+
+- **A command that reads the service and only saves what it read is a read, also over MCP.**
+  [WC-CMD-17](docs/standards/commands.md#wc-cmd-17--declare-effects-on-every-command) defines a write, and WC-CMD-6,
+  WC-CMD-28, [WC-MCP-4](docs/standards/mcp.md#wc-mcp-4--read-runs-only-reading-commands-and-write-only-writing-ones)
+  and WC-OUT-9 point at it: `{ remote: "read", local: "write" }` (`sync`, `calendars list`) runs through the `read`
+  tool; `{ remote: "none", local: "write" }` (`store reindex`) stays a write. cli-base's `writes()` still counts every
+  local write, so cli-core serves `sync` through `write` until a follow-up changes it; watch for that release, which
+  moves those commands between tools.
+- **Deadlines: 30 s for a one-shot command, 5 min for a cooperative one at a terminal and 45 s over MCP.**
+  [WC-LIFE-5](docs/standards/lifecycle.md#wc-life-5--bound-every-one-shot-command-by-a-deadline) and WC-LIFE-10 say
+  so, as cli-core 0.464.0 builds it, because MCP clients cut a tool call at about 60 s.
+- **A non-messenger CLI allows ordinary writes, asks before deletes, and denies mail to other people and deleting
+  a whole series.**
+  [WC-PERM-22](docs/standards/permissions.md#wc-perm-22--a-cli-that-is-not-a-messenger-declares-its-own-keys-and-defaults-with-commandpermissions)
+  follows the owner's ruling, and a CLI's generic API path must check the shared keys (`events.notify`,
+  `events.delete.series`) too. Its example said sharing a calendar is `deny`; the owner made it `ask`. cli-core's
+  `CALENDAR_WRITE_DEFAULTS` and gcal's `api` defaults do not follow it yet; both are listed as gaps.
+- **Meeting passcodes stay out of command output and agent answers, not only out of the store.**
+  [WC-SECR-23](docs/standards/security.md) covers answers that come straight from the provider: gcal's `api` answers
+  still keep a description's passcode lines, a listed gap.
+- **Each CLI pins the command catalogue behind its MCP tools.** The [MCP](docs/standards/mcp.md) page no longer
+  claims `mcp-tools.json` pins the catalogue: with three tools it does not. `contracts/mcp-catalogue.json` does; tg and
+  max have it, and wa, zm, gcal and drive do not yet.
+
+- **An MCP server serves the profiles it is told, and refuses without them.**
+  [WC-MCP-9](docs/standards/mcp.md#wc-mcp-9--a-server-serves-the-profiles-it-is-told-with-one-connection-for-each)
+  now allows one named profile (`<cli> <profile> mcp serve`), a list (`<cli> mcp serve --profiles work,personal`) or
+  every profile (`<cli> mcp serve --profiles all`), with one messenger connection per served profile. With no profile
+  and no `--profiles`, `mcp serve` fails with `validation_error` and lists the profiles; it never serves every profile
+  by default. With several profiles, each call names its profile. WC-ACCT-1, WC-ACCT-2 and WC-ACCT-5 say how
+  `--profiles` fits the profile rules, and a profile lock refuses `--profiles all`. The flag registry has `--profiles`.
+  The owner ruled it; cli-core does not build `--profiles` yet.
+- **The handbook names the MCP server `mcp serve` and has no `mcp --revoke` exception.** The
+  [MCP](docs/standards/mcp.md) and [Lifecycle](docs/standards/lifecycle.md) pages say `mcp serve`, `mcp serve --http`,
+  `mcp serve --permission`, `bot mcp serve` and `mcp revoke`, as cli-core 0.463.0 builds them.
+  [WC-CMD-6](docs/standards/commands.md#wc-cmd-6--give-one-action-or-one-report-one-leaf-command) no longer lets
+  `--revoke` stay an option: forgetting every browser login is the `mcp revoke` command. A CLI with its own server
+  (drive, memo, zoom) moves to the same shape.
+- **A lint baseline entry for `serve` or `revoke` goes stale, and `cli-dev lint` fails on it.** cli-core lists
+  `bot mcp serve`, `mcp serve`, `mcp revoke` and `replies consents revoke` in `lint/baseline/unknown-verb.json`;
+  tg-cli and max-cli list `replies consents revoke`. Remove those entries in the same change that takes this version.
+- **The HTTP MCP server rule covers every CLI that offers `mcp serve --http`, not only the messenger CLIs.**
+  [WC-MCP-12](docs/standards/mcp.md#wc-mcp-12--an-mcp-server-over-http-follows-the-same-permissions-and-short-lived-logins)
+  now applies to cli-template and every CLI made from it, which have offered `mcp serve --http` with no rule over it.
+  The template already follows it; a CLI that changed its copy of the HTTP server checks it against the rule.
+
+### Fixed
+
+- **`cli-dev audit` compares gcal only on the commands it already shares with every CLI, for now.** cli-base 0.64.0
+  put gcal into the `all` parity group, and gcal's release audit then blocked on 20 `same-path-contract` differences
+  in `doctor`, `mcp`, `search` and `skill` that already exist among the other six published CLIs and that gcal
+  cannot remove alone (gcal-cli#13). gcal leaves `all` and has its own group, `gcal-shared`, with every CLI over
+  `commands`, `upgrade`, `notes` and `meetings`. It rejoins `all` once tg, max, wa, drive, zoom and memo release on
+  cli-core's shared `mcp serve`, `doctor` and `skill` ([#390](https://github.com/WireCatLabs/cli-base/issues/390)).
+  The other CLIs' audits are unchanged: a path is compared across every member of every group that covers it.
+
+- **`cli-dev bundle`'s loader finds a server after a flag: `<cli> personal --read-only mcp serve`.** It looked for
+  `serve`, `watch` or `mcp` in the first three words of the command, and since cli-core 0.463 named the server
+  `mcp serve`, a flag before it pushed `serve` to the fourth word. Such a server loaded no chunks ahead and could fail
+  after an in-place upgrade (measured on drive: 91 of 138 chunks loaded, instead of 138). The loader now skips flags
+  and looks at four words. Rebuild a CLI with this release to take it.
+- **The handbook no longer contradicts itself on gcal's audit findings.**
+  - WC-OUT-8 and WC-OUT-14: an answer with `meta.complete: false` is an answer on stdout, also after a non-zero
+    exit; only a run with no answer prints one JSON error with stdout empty.
+  - WC-CMD-10 names `--max-pages` a `budget` option, not a paging one, and says why the calendar `--id` exists beside
+    `--operation-id`; gcal's `events create`, with `--id` and no `--operation-id`, is a listed gap. WC-CMD-11 lists `--duration-minutes` as a known gap until the vocabulary has
+    `--duration <duration>`.
+  - WC-REL-16 says `packContents` checks the pack against the list it is given, so a check that passes the `files`
+    list itself cannot fail on a wrong list; the fix belongs in cli-template.
+  - WC-TIME-5 matches an all-day event by local dates, not UTC moments; cli-core's event filter is a listed gap.
+  - WC-ARCH-3 counts generated API types as vendor types, WC-ARCH-5 and WC-ARCH-6 cover calendar CLIs, and
+    WC-ARCH-21's example is gcal's real provider entry.
+  - WC-TOOL-16 puts a word waiting for the vocabulary in `lint/overrides.json` with a link and a date, never in the
+    baseline. The [Documents](docs/standards/docs.md#wc-doc-3--every-document-states-current-facts-rewrite-a-wrong-sentence-in-place)
+    rule on current facts sends a false template-owned file to cli-template.
+  - WC-DATA-3 makes a calendar entry's `external_id` unique per calendar, WC-STORE-3 lists the calendar areas as not
+    bound, WC-TEST-12 says what a reason names, and WC-TEST-14 counts the shared store as local state.
+  - The "who follows" lists name gcal.
+
+- **The handbook's pages on the template match cli-template 0.9.0.** The [Kit surface](docs/standards/kit-surface.md)
+  table lists `LOCAL_WRITE` and `revokeAll`, which the template now imports, and counts imports loaded on demand.
+  [New CLI](docs/standards/new-cli.md) says the MCP server has three tools that reach every command, not a tool for
+  every command.
+- **The handbook says where a lint violation that a shared package forces goes, and which cli-core files are not a
+  CLI's local state.** [WC-TOOL-16](docs/standards/toolchain.md) puts such a violation in the CLI's lint baseline
+  until the shared package catches up.
+  [WC-TEST-14](docs/standards/testing.md#wc-test-14--check-the-upgrade-from-the-previous-published-version) names
+  the update check, MCP logins and lock files that only cli-core writes as outside the upgrade contract; tests still
+  keep them in the sandboxed home.
+
 ## 0.64.0 — 27.10.2026
 
 ### Added

package/dist/credentials.d.ts

@@ -19,6 +19,9 @@ export interface CredentialsOptions {
      * not — it overwrites the real secret for that account. In `brazecli` that destroyed two working
      * keys on 2026-09-14, and a keyring entry cannot be read back out. Passing `true` here scopes the
      * service name to the directory, making the isolation people already assume they have real.
+     *
+     * With the system keyring it also keeps new secrets out of it: they go to the file in the moved directory, so a test
+     * or worktree run leaves nothing in the owner's keyring (WC-SECR-24). A secret saved there before is still read.
      */
     isolated?: boolean;
     /** Read before the keyring, for CI. */

package/dist/credentials.js

@@ -21,6 +21,7 @@ export class Credentials {
     #envVar;
     #fileName;
     #warn;
+    #fileFirst;
     #warned = false;
     constructor(options) {
         this.#configDir = options.configDir;
@@ -31,21 +32,30 @@ export class Credentials {
         this.#fileName = options.fileName ?? "credentials.json";
         this.#warn = options.warn ?? ((message) => process.stderr.write(`${message}\n`));
         this.#service = keyringService(options.service, options.configDir, options.isolated);
+        this.#fileFirst = options.isolated === true && this.#keyring === systemKeyring;
     }
     read(account) {
         const fromEnv = this.#envVar ? this.#env[this.#envVar]?.trim() : undefined;
         if (fromEnv)
             return { secret: fromEnv, source: "environment" };
+        const fromFile = () => {
+            const secret = this.#readFile()?.[account]?.secret;
+            return secret ? { secret, source: "file" } : undefined;
+        };
+        if (this.#fileFirst) {
+            const found = fromFile();
+            if (found)
+                return found;
+        }
         if (this.#storage !== "file") {
             const fromKeyring = this.#tryKeyring(() => this.#keyring.get(this.#service, account));
             if (fromKeyring)
                 return { secret: fromKeyring, source: "keyring" };
         }
-        const fromFile = this.#readFile()?.[account]?.secret;
-        return fromFile ? { secret: fromFile, source: "file" } : undefined;
+        return this.#fileFirst ? undefined : fromFile();
     }
     write(account, secret) {
-        if (this.#storage !== "file") {
+        if (this.#storage !== "file" && !this.#fileFirst) {
             const stored = this.#tryKeyring(() => {
                 this.#keyring.set(this.#service, account, secret);
                 return true;

package/dist/dev/bundle.d.ts

@@ -20,6 +20,12 @@ export declare const DEFAULT_EXTERNAL: string[];
 export declare const DEFAULT_ANCHORED: string[];
 export declare const DEFAULT_HARMLESS: string[];
 export declare const LOADER_MARK = "// cli-dev bundle loader\n";
+/**
+ * Whether the loader runs a server: `serve`, `watch` or `mcp serve`, or `mcp` alone as before cli-core 0.463. Flags
+ * are skipped, so `<cli> personal --read-only mcp serve` counts; four words leave room for one flag's value. It is
+ * written into the loader as source, so it uses nothing from outside.
+ */
+export declare const isServer: (words: readonly string[]) => boolean;
 /** The bin that replaces the compiled one: `name` is the bundle's entry, `chunks` what a server preloads. */
 export declare const loaderSource: (name: string, version: string, chunks: readonly string[]) => string;
 export declare const bundle: (options: BundleOptions) => Promise<BundleResult>;

package/dist/dev/bundle.js

@@ -166,6 +166,17 @@ const commonJsNames = {
         });
     },
 };
+/**
+ * Whether the loader runs a server: `serve`, `watch` or `mcp serve`, or `mcp` alone as before cli-core 0.463. Flags
+ * are skipped, so `<cli> personal --read-only mcp serve` counts; four words leave room for one flag's value. It is
+ * written into the loader as source, so it uses nothing from outside.
+ */
+export const isServer = (words) => {
+    const plain = words.filter((word) => !word.startsWith("-"));
+    return plain
+        .slice(0, 4)
+        .some((word, at) => word === "serve" || word === "watch" || (word === "mcp" && plain[at + 1] === undefined));
+};
 /** The bin that replaces the compiled one: `name` is the bundle's entry, `chunks` what a server preloads. */
 export const loaderSource = (name, version, chunks) => `#!/usr/bin/env node
 ${LOADER_MARK}import * as module from "node:module"
@@ -181,9 +192,7 @@ if (
 } else {
   // Before the bundle compiles: the bundle's own call comes after its chunks.
   module.enableCompileCache()
-  const serves = words
-    .slice(0, 3)
-    .some((word, at) => ["serve", "watch"].includes(word) || (word === "mcp" && !/^[^-]/.test(words[at + 1] ?? "")))
+  const serves = (${isServer.toString()})(words)
   if (serves && module.registerHooks) {
     const bundle = new URL("../bundle/", import.meta.url).href
     module.registerHooks({

package/dist/dev/land.d.ts

@@ -39,10 +39,11 @@ export declare const landChange: ({ file, branch, change: changeOf, done, shell,
     log: (text: string) => void;
 }) => string | undefined;
 /**
- * The newest `v<x.y.z>` tag in this commit's history and the changelog at it. Tags are fetched first: a clone made before the
- * last release does not have its tag, and comparing against an older one would hide the newest drift.
+ * The newest `v<x.y.z>` tag in this commit's history and the changelog at it, or `undefined` before the first release. Tags
+ * are fetched first: a clone made before the last release does not have its tag, and comparing against an older one would
+ * hide the newest drift.
  */
 export declare const newestTag: (shell: Shell, path: string) => {
     version: string;
     text: string;
-};
+} | undefined;

package/dist/dev/land.js

@@ -124,8 +124,9 @@ export const landChange = ({ file, branch, change: changeOf, done, shell, log, }
     throw new Error(`main moved under ${branch} twice — run bin/release again`);
 };
 /**
- * The newest `v<x.y.z>` tag in this commit's history and the changelog at it. Tags are fetched first: a clone made before the
- * last release does not have its tag, and comparing against an older one would hide the newest drift.
+ * The newest `v<x.y.z>` tag in this commit's history and the changelog at it, or `undefined` before the first release. Tags
+ * are fetched first: a clone made before the last release does not have its tag, and comparing against an older one would
+ * hide the newest drift.
  */
 export const newestTag = (shell, path) => {
     const fetched = shell.run("git", ["fetch", "-q", "--tags", "origin"]);
@@ -141,7 +142,7 @@ export const newestTag = (shell, path) => {
         return (y?.[0] ?? 0) - (x?.[0] ?? 0) || (y?.[1] ?? 0) - (x?.[1] ?? 0) || (y?.[2] ?? 0) - (x?.[2] ?? 0);
     });
     if (!version)
-        throw new Error("no v<x.y.z> tag to compare the changelog with");
+        return undefined;
     const shown = shell.run("git", ["show", `v${version}:${path}`]);
     if (!shown.ok)
         throw new Error(`git show v${version}:${path} failed: ${shown.out}`);

package/dist/dev/main.js

@@ -133,6 +133,10 @@ const changelog = (args, io) => {
         if (action === "restore") {
             const shell = processShell(io.cwd);
             const tag = newestTag(shell, relative(io.cwd, file));
+            if (!tag) {
+                io.err("no v<x.y.z> tag yet: a first release has nothing to restore");
+                return 0;
+            }
             if (!taggedSection(tag.text, tag.version)) {
                 io.err(`v${tag.version}'s changelog has no section of its own; nothing to restore`);
                 return 0;

package/dist/standards/audit.js

@@ -64,10 +64,18 @@ export const PARITY_GROUPS = defineParityGroups([
     { name: "messengers", members: ["tg", "max"], covers: "tree", differences: [] },
     {
         name: "all",
-        members: ["tg", "max", "memo", "drive", "zm", "wa", "gcal"],
+        members: ["tg", "max", "memo", "drive", "zm", "wa", "mail"],
         covers: ["commands", "doctor", "skill", "mcp", "upgrade", "search", "notes", "meetings"],
         differences: [],
     },
+    // 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".
+    {
+        name: "gcal-shared",
+        members: ["tg", "max", "memo", "drive", "zm", "wa", "gcal"],
+        covers: ["commands", "upgrade", "notes", "meetings"],
+        differences: [],
+    },
 ]);
 const requiredRootSchema = v.strictObject({ path: v.pipe(v.array(segment), v.minLength(1)), meaning: text });
 export const defineRequiredRoots = (input) => parseRegistry("required roots", v.array(requiredRootSchema), input, (roots) => duplicates(roots.map((root) => root.path.join(" "))).map((path) => `"${path}" is listed twice`));

package/dist/standards/flags-calendar.js

@@ -56,4 +56,17 @@ export const CALENDAR_FLAGS = [
         type: "switch",
         meaning: "act on the whole repeating event, not only this occurrence",
     },
+    {
+        name: "--following",
+        role: "target",
+        type: "switch",
+        meaning: "act on this occurrence and every later one of the repeating event",
+    },
+    {
+        name: "--to-calendar",
+        value: "<id>",
+        role: "target",
+        type: "id",
+        meaning: "the calendar it moves to, of the same account",
+    },
 ];

package/dist/standards/flags-what.js

@@ -187,6 +187,13 @@ export const WHAT_FLAGS = [
         type: "string",
         meaning: "the profile to use, instead of the first word",
     },
+    {
+        name: "--profiles",
+        value: "<names|all>",
+        role: "scope",
+        type: "list",
+        meaning: "the profiles an MCP server serves, comma-separated, or all of them",
+    },
     {
         name: "--history-since-time",
         value: "<time>",

package/dist/standards/vocabulary.js

@@ -115,7 +115,9 @@ const verbs = [
     ["start", "start a running process, or a login session"],
     ["stop", "stop a running process"],
     ["restart", "stop and start a running process"],
+    ["serve", "run a server in this process and answer its clients until stopped"],
     ["end", "end a login session"],
+    ["revoke", "take back what was granted, so it stops working: a login, an invite link, a consent"],
     ["install", "install a system unit"],
     ["uninstall", "remove a system unit"],
     ["cancel", "stop a job or a pending thing"],
@@ -180,7 +182,7 @@ const verbs = [
     ["reject", "the owner refuses what an agent proposed"],
     ["review", "list what waits for the owner's decision"],
     ["resolve", "settle one thing that waits for the owner's decision, with the owner's choice"],
-    ["move", "move a file in the source"],
+    ["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"],
     ["claim", "take a thing for a while so no other agent works it at once; the claim lapses by itself"],

package/docs/standards/README.md

@@ -32,14 +32,14 @@ the four steps that need a person. A new CLI is ready for its first release when
 | [Commands](commands.md) | `CMD` | 28 | Paths, vocabulary, flags, arguments, effects, lifetime, query, help, external references |
 | [Output](output.md) | `OUT` | 23 | 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` | 11 | The explicit profile, reads across accounts, scope flags, linked identities |
+| [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 |
 | [Architecture](architecture.md) | `ARCH` | 17 | Layers, dependency direction, vendor types, what goes in which package |
-| [Lifecycle](lifecycle.md) | `LIFE` | 14 | Opening late, who closes, one-shot exits, long-running commands, the `serve` relay, resumable syncs, the run log |
+| [Lifecycle](lifecycle.md) | `LIFE` | 15 | Opening late, who closes, deadlines, long-running commands, the `serve` relay, resumable syncs and their request budget, the run log |
 | [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` | 22 | Secrets, logs, keyring, argv, error text, untrusted text, scanners, workflow hardening, reporting, OAuth sign-in, meeting secrets |
+| [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 |
 | [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` | 15 | `bin/release`, the release lock, versions, release reports, trusted publishing |

package/docs/standards/accounts.md

@@ -3,7 +3,7 @@
 ## Scope
 
 How a CLI chooses an account: the profile is always explicit, a read across accounts covers all of them and says so,
-and scope flags work the same everywhere.
+scope flags work the same everywhere, and sign-in has the same four commands in every CLI.
 
 A **profile** is the name of one login of a CLI on one computer, for example `personal` or `work`. One profile can
 hold a personal session, a bot token, or both.
@@ -16,7 +16,8 @@ Rule ids on this page are `WC-ACCT-<n>`. How to read a rule, how ids work and wh
 cli-core resolves the profile for tg, max and wa. WC-ACCT-1 needs cli-core 0.319.0 or newer. memo has no messenger profile: its shared commands run without one, and they pick accounts with `--provider`
 and `--account` (WC-ACCT-7). zoom resolves its own profile word by the same rules (`zm <profile> …`, `ZM_PROFILE`,
 `ZM_PROFILE_LOCK`) from zoom-cli 0.35.0, with cli-core's `liftProfile` and `usableProfileName`. drive still has its own
-profile code: it registers its own profiles. That is a known gap, not an exception.
+profile code: it registers its own profiles. That is a known gap, not an exception. gcal resolves the profile through
+cli-core's `run()`, like tg, max and wa. Which CLIs lack a sign-in command of WC-ACCT-12 is listed in that rule.
 
 ## Rules
 
@@ -31,9 +32,11 @@ on the computer.
 - **Example:** `tg personal chats list`, or `TG_PROFILE=personal tg chats list`. When no profile is named and the
   config file still has `default_profile`, cli-core stops and says which profile to type. `config set default_profile`
   is refused.
-- **Exceptions:** a command that touches no account runs without a profile, for example `account list`,
-  `config show` and `commands`.
-- **Applies to:** all CLIs. **Since:** cli-base 0.41.0. **Rulings:** NEED-84.
+- **Exceptions:** a command that touches no account runs without a profile, for example `session list`
+  ([WC-ACCT-12](#wc-acct-12--sign-in-is-session-start-status-and-end-and-session-list-names-the-profiles)),
+  `config show` and `commands`; tg, max and wa still name their list `account list`. `mcp serve` may name its profiles with `--profiles <names|all>` instead
+  ([WC-MCP-9](mcp.md#wc-mcp-9--a-server-serves-the-profiles-it-is-told-with-one-connection-for-each)); `all` is the owner's explicit choice, never a fallback.
+- **Applies to:** all CLIs. **Since:** cli-base 0.41.0. **Rulings:** NEED-84, NEED-1881.
 
 ### WC-ACCT-2 · The profile is a word, never a flag
 
@@ -44,8 +47,9 @@ profile.
 - **Enforced by:** `cli-core: src/cli/profile.test.ts`.
 - **Example:** `max work bot messages send …` uses the same first word as `max work chats list`. `tg --json chats list`
   still works, because `--json` is an option.
-- **Exceptions:** none.
-- **Applies to:** all CLIs. **Since:** cli-base 0.41.0. **Rulings:** NEED-84, NEED-294.
+- **Exceptions:** `mcp serve --profiles <names|all>` names the profiles one server serves ([WC-MCP-9](mcp.md#wc-mcp-9--a-server-serves-the-profiles-it-is-told-with-one-connection-for-each)). It is used in
+  place of the first word, never with it.
+- **Applies to:** all CLIs. **Since:** cli-base 0.41.0. **Rulings:** NEED-84, NEED-294, NEED-1881.
 
 ### WC-ACCT-3 · A missing profile is an error that lists the choices
 
@@ -78,8 +82,8 @@ top-level command, such as `chats` or `bot`, is refused when the profile is crea
 
 ### WC-ACCT-5 · A profile lock pins a process to one profile
 
-When `<PREFIX>_PROFILE_LOCK` is set, a first word or `<PREFIX>_PROFILE` that names any other profile is refused with
-`permission_error`.
+When `<PREFIX>_PROFILE_LOCK` is set, a first word, `<PREFIX>_PROFILE` or `mcp serve --profiles` that names any other
+profile is refused with `permission_error`. `--profiles all` names every profile, so it is refused too.
 
 - **Why:** an agent must not escape its guards by naming a profile with fewer of them.
 - **Enforced by:** `cli-core: src/cli/settings.test.ts`.
@@ -155,6 +159,35 @@ inferred from a matching name, and `unlink` undoes it.
 - **Exceptions:** none.
 - **Applies to:** all CLIs. **Since:** cli-base 0.43.1. **Rulings:** none.
 
+### WC-ACCT-12 · Sign-in is `session start`, `status` and `end`, and `session list` names the profiles
+
+Every CLI that signs in has four commands under `session`:
+
+- `<cli> <profile> session start` signs the profile in.
+- `<cli> <profile> session status` says whether this profile is signed in, and as whom.
+- `<cli> <profile> session end` signs the profile out and forgets its login.
+- `<cli> session list` takes no profile and lists the profiles on this computer.
+
+`status` answers about one profile; `list` answers which profiles exist. Neither one connects to more than it must:
+`list` reads only what the computer holds.
+
+- **Why:** the owner and an agent look for sign-in in the same place in every CLI. Today each CLI has a different
+  part of the set, so an agent that learned one CLI guesses wrong in the next.
+- **Enforced by:** review only.
+- **Example:** `gcal personal session status` answers whether the `personal` profile holds a Google login;
+  `gcal session list` lists `personal` and `work` with no profile named.
+- **Exceptions:** known gaps, as of 2026-10-27:
+  - tg, max and wa have `session start` and `session end`, no `session status`, and list their profiles with
+    `account list` instead of `session list`.
+  - drive has `session start`, `session list` and `session end`, and no `session status`.
+  - gcal has `session start`, `session status` and `session end`, and no `session list`.
+  - zm has `session start` and `session status`, and no `session end` or `session list`.
+  - memo signs in per mail account with `mail add` and has no `session` group.
+
+  A CLI that adds a missing command adds it under `session`; a renamed path keeps no alias
+  ([WC-CMD-8](commands.md#wc-cmd-8--keep-no-aliases-a-renamed-path-stops-working-in-the-release-that-renames-it)).
+- **Applies to:** every CLI that signs in. **Since:** cli-base 0.65.0. **Rulings:** NEED-1884.
+
 ## Sources
 
 These documents explain the rules on this page in more detail. Where one of them disagrees with this page, this page

package/docs/standards/architecture.md

@@ -20,7 +20,9 @@ at start-up and the `serve` relay are in [Lifecycle](lifecycle.md); the store's
 - **Service:** a use case, written once, that both a command and an MCP tool call.
 - **Composition root:** the place in a CLI where real implementations are chosen and connected, usually
   `program.ts` and the command context.
-- **Vendor type:** a type from a provider library, such as `@mtcute/*` or `ws`.
+- **Vendor type:** a type from a provider library, such as `@mtcute/*` or `ws`, and a type generated from a
+  provider's API description, such as gcal's and drive's types under `src/generated/` from a Google Discovery
+  document: both change when the provider changes, not when we do.
 
 ## Rules
 
@@ -57,7 +59,9 @@ at start-up and the `serve` relay are in [Lifecycle](lifecycle.md); the store's
   `src/adapter/` maps the client onto the shared messenger port. A field that only one provider has travels in
   `providerMetadata`.
 - **Exceptions:** a bot slice that talks to an official HTTP API keeps its own transport, beside the personal
-  account's adapter, never above it.
+  account's adapter, never above it. Generated API types may also be used by the generated `api <method>` commands,
+  which are the provider's own API by design; the shared ports and services never see them. In gcal,
+  `calendar-source.ts` and `calendar-writer.ts` translate the generated event type into cli-core's calendar entry.
 - **Applies to:** all CLIs. **Since:** cli-base 0.41.0. **Rulings:** NEED-12.
 
 ### WC-ARCH-4 · Put code in the lowest shared package that can hold it
@@ -77,14 +81,16 @@ at start-up and the `serve` relay are in [Lifecycle](lifecycle.md); the store's
 
 ### WC-ARCH-5 · Build a feature that another provider could have as a shared command behind a capability
 
-- **Why:** a command written once in cli-core gives every messenger the same path, flags and output.
+- **Why:** a command written once in cli-core gives every provider of a kind the same path, flags and output.
 - **Enforced by:** review only.
 - **Example:** topics and polls are port groups and shared commands in cli-core. A messenger that lacks a capability
   refuses the command; it does not silently do less. A bot is another messenger with fewer capabilities, and tg and
-  max share the bot code.
-- **Exceptions:** a feature stays in one CLI only when the other providers cannot have it, such as MAX's socket server
-  or Telegram's app registration.
-- **Applies to:** messenger CLIs (tg, max, wa). **Since:** cli-base 0.41.0. **Rulings:** NEED-820, NEED-440,
+  max share the bot code. Calendars have the same shape: cli-core's `addCalendarCommands` builds `calendars`,
+  `sync`, `status`, `events` and `search` over the `CalendarSource` and `CalendarWriter` ports, and mounts
+  `calendars busy` or the event writes only when the provider has them.
+- **Exceptions:** a feature stays in one CLI only when the other providers cannot have it, such as MAX's socket server,
+  Telegram's app registration, or gcal's generated `api` commands.
+- **Applies to:** messenger CLIs (tg, max, wa) and calendar CLIs (gcal). **Since:** cli-base 0.41.0. **Rulings:** NEED-820, NEED-440,
   NEED-301, NEED-444.
 
 ### WC-ARCH-6 · Replace a use case, not a command
@@ -93,9 +99,10 @@ at start-up and the `serve` relay are in [Lifecycle](lifecycle.md); the store's
 - **Enforced by:** review only.
 - **Example:** `Messenger.services` receives the shared services and returns only the ones it changes:
   `services: (base) => ({ messages: { ...base.messages, list: maxList } })`. To add a subcommand, a CLI calls
-  `addCommand` on the command a factory returns.
+  `addCommand` on the command a factory returns. A calendar CLI changes what the shared calendar commands do through
+  the source and writer it passes to `addCalendarCommands`, never by writing its own `sync` or `events list`.
 - **Exceptions:** none.
-- **Applies to:** messenger CLIs. **Since:** cli-base 0.41.0. **Rulings:** none.
+- **Applies to:** messenger CLIs and calendar CLIs. **Since:** cli-base 0.41.0. **Rulings:** none.
 
 ### WC-ARCH-7 · Keep policy in the service; a command or MCP handler only parses input and presents the result
 
@@ -215,9 +222,9 @@ out of search and listed under `skipped`, with the hint to run that CLI once.
 - **Why:** a new source joins search and memo without editing cli-core, and a provider nobody described is never read
   as something it is not (until this rule, an unlisted provider was searched as a messenger).
 - **Enforced by:** `cli-core: src/store/sqlite/providers.test.ts`.
-- **Example:** cal registers `{ name: "google-calendar", kind: "events", aliases: ["cal"], command: "cal" }` each
-  time it starts. On a machine where cal has never run, a search across accounts lists cal's accounts under
-  `skipped` instead of reading their rows as messages.
+- **Example:** gcal registers `{ name: "google-calendar", kind: "events", aliases: ["gcal", "calendar"], command:
+  "gcal" }` each time it opens the store. On a machine where gcal has never run, a search across accounts lists
+  gcal's accounts under `skipped` instead of reading their rows as messages.
 - **Exceptions:** the built-in providers of cli-core need no entry. Two entries that disagree on a kind are an error
   naming both.
 - **Applies to:** cli-core and every CLI with a provider of its own. **Since:** cli-base 0.53.0. **Rulings:** none

package/docs/standards/ci.md

@@ -172,6 +172,7 @@ its prompt in cli-template says so from cli-template 0.8.0. A CLI on an older te
   | 02:27 | gcal-cli |
   | 02:31 | cli-memo |
   | 02:38 | cli-core |
+  | 02:41 | mail-cli |
   | 02:45 | drive-cli |
   | 02:52 | cli-testing |
   | 02:59 | max-cli |