@wirecat/cli-base 0.64.0 → 0.65.1

package/docs/standards/store.md

@@ -52,8 +52,9 @@ Related pages: which account a read covers, and how a read across accounts is as
   accounts on purpose asks for the whole store with `crossAccount(deps, reason)`; see [Accounts](accounts.md).
 - **Exceptions:** `forAccount` binds only the account areas (accounts, chats, sync, messages, attachments, roster,
   people, conversations, vectors, counters, tags, mentions). The `chats`, `conversations` and `attachments` services
-  use the bound store; the other services still pair `deps.store()` with `deps.account()`. New code uses the bound
-  store.
+  use the bound store; the other services still pair `deps.store()` with `deps.account()`. The calendar areas
+  (calendars, calendar entries, their sync cursors) are not bound either: cli-core's calendar commands pass
+  `accountId` to every call, a known gap as of 2026-10-27. New code uses the bound store.
 - **Applies to:** cli-core and every CLI that adds a service. **Since:** cli-base 0.41.0. **Rulings:** none.
 
 ### WC-STORE-4 · Reach the store through its public module, never a table module

package/docs/standards/testing.md

@@ -171,8 +171,9 @@ and which run after merge is in [CI](ci.md).
 - **Enforced by:** `node-ci.yml:check` · `<app>: pnpm test:matrix:check`.
 - **Example:** under vitest, `run()` appends each parsed command path and option name (never a value) to
   `coverage/argv.jsonl`. `pnpm test:matrix` turns that into `docs/dev/test-matrix.md` and fails on a command or
-  option with neither a test nor a reason. A reason names the live scenario that covers it. A test that calls a
-  function directly does not count.
+  option with neither a test nor a reason. A test counts only when it runs the command through `run()`: a test that
+  calls a function directly records no command line, so the matrix does not see it. A reason says what covers the
+  command instead: the live scenario that runs it, or, for a generated group, the two tests below.
 - **Exceptions:** commands generated from a service's API description, such as drive's and gcal's
   `api <method>` from a Google Discovery snapshot, share one reason for the whole group (`api *` and its options).
   It names two tests: one that checks every generated command's options against the snapshot, and one that drives a
@@ -198,9 +199,13 @@ and which run after merge is in [CI](ci.md).
 - **Enforced by:** `node-ci.yml:check` · `<app>: pnpm contracts:upgrade`.
 - **Example:** `pnpm contracts:upgrade` runs the previous published package and this build on the same synthetic
   state and checks that the data survives. Each store migration also has its own upgrade test (WC-STORE-9).
-- **Exceptions:** a CLI with no local state, or with no published version yet. Local state is data the CLI's own
-  code writes and reads back in a later run, such as a store, a session or a cache. A config file and run records
-  that only cli-core writes do not count.
+- **Exceptions:** a CLI with no local state, or with no published version yet. Local state is data the CLI writes
+  and reads back in a later run, such as a store, a session or a cache. The shared store counts, also when cli-core's
+  code writes it, because the CLI's release decides which cli-core and so which migrations run: gcal's calendars and
+  events in the store are its local state. A config file, run records, the
+  update check, MCP logins and lock files that only cli-core writes do not count. Tests still keep them in the
+  sandboxed home, like every other path
+  ([WC-TEST-1](#wc-test-1--point-every-path-a-test-could-write-at-a-temporary-directory)).
 - **Applies to:** all CLIs with local state. wa has no upgrade contract yet. **Since:** cli-base 0.41.0. **Rulings:** none.
 
 ### WC-TEST-15 · A refactor keeps `commands --json` and the MCP tool list as they were

package/docs/standards/time.md

@@ -76,7 +76,14 @@ local midnight. The answer gives the window it used, in UTC.
 - **Why:** "messages of 1 September" means the owner's day, not the UTC day, which starts hours earlier or later.
 - **Enforced by:** review only.
 - **Example:** in `Asia/Vladivostok`, `--since-time 2026-09-01` gives `meta.window.since` = `2026-08-31T14:00:00.000Z`.
-- **Exceptions:** none.
+  A thing that has only dates, such as an all-day event (`start_date` 2026-09-01, `end_date` 2026-09-02, the end
+  not included), matches by comparing local dates, never UTC moments: it is in the window when its dates overlap the
+  local dates the window covers. So in `Europe/Madrid` a filter for 1 September returns the all-day event of
+  1 September and not the one of 31 August, whatever zone the event's calendar is in.
+- **Exceptions:** none. Known gap, as of 2026-10-27, read from the code and not run: cli-core's event filter
+  (`src/store/sqlite/calendar.ts`, the `events` query) compares `starts_at` and `ends_at` with the UTC window for
+  all-day events too, and gcal stores an all-day event's start as midnight in its calendar's zone. The two agree
+  when the calendar's zone is the zone in use, and miss by a day at the edges when it is not.
 - **Applies to:** all CLIs. **Since:** cli-base 0.48.0. **Rulings:** none.
 
 ### WC-TIME-6 · Run the tests in a zone that is not UTC, and prove stored values do not depend on it

package/docs/standards/toolchain.md

@@ -200,8 +200,13 @@ no-unbounded-spread ([WC-TOOL-12](#wc-tool-12--do-not-spread-a-list-of-user-data
   request.
 - **Enforced by:** `<app>: pnpm lint:commands`.
 - **Example:** `"lint:commands": "cli-dev lint --cli dist/bin/max.js"`, run by `ci:quick` after the build. Known
-  violations live in `lint/baseline/<rule-id>.json`; an entry with no violation left fails the run. A permanent
-  exception goes in `lint/overrides.json` with `rule`, `target`, `reason`, `owner` and `review_after`. More than 10
+  violations live in `lint/baseline/<rule-id>.json`; an entry with no violation left fails the run. A violation that a
+  shared package forces, such as a verb cli-core names before the vocabulary has it, goes in the baseline too and
+  comes out when the shared package catches up. A word the CLI needs that the vocabulary does not have yet goes in
+  `lint/overrides.json`, never in the baseline: its `reason` links the cli-base pull request or issue that adds the
+  word, and it comes out in the change that takes the cli-base release with the word. The shared package's words
+  go in the baseline, as above; the CLI's own go in the overrides, where the count and the date keep them few. A permanent exception also goes in `lint/overrides.json`, with `rule`, `target`, `reason`, `owner`
+  and `review_after`. More than 10
   overrides fail the run, and so does one past its date. The rules themselves are on the
   [Commands page](commands.md).
 - **Exceptions:** zoom runs `lint:commands` in full validation only. cli-core runs its own command lint test in

package/package.json

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