@wirecat/cli-base 0.43.5 → 0.44.0

package/docs/standards/testing.md

@@ -47,14 +47,17 @@ and which run after merge is in [CI](ci.md).
 - **Applies to:** all CLIs and the shared packages. cli-base uses the shared setup; the CLIs keep their own sandboxes
   for now. drive has none yet, and zoom's moves only the temporary directory. **Since:** cli-base 0.41.0. **Rulings:** none.
 
-### WC-TEST-2 · No test reaches the real keyring
+### WC-TEST-2 · No test opens a real credential store
 
-- **Why:** the owner's tokens live in the real keychain, and one test that forgets an option would write there.
-- **Enforced by:** `src/keyring.test.ts`.
+- **Why:** the owner's tokens live in the real keychain, and a messenger's device keys in a file of their own; one
+  test that forgets an option would read or write the real one.
+- **Enforced by:** `src/keyring.test.ts` · `whatsapp-cli: src/testing/sandbox.test.ts`.
 - **Example:** every test passes `memoryKeyring()` from `@wirecat/cli-base/testing`. The shared setup
   (`@wirecat/cli-base/testing/setup`, [WC-TEST-1](#wc-test-1--point-every-path-a-test-could-write-at-a-temporary-directory))
   also replaces `@napi-rs/keyring` with a module that throws, so a forgotten option fails the test instead of
   reaching the keychain, and `src/keyring.test.ts` asserts that `systemKeyring` throws under it.
+  A credential store that is a file, such as WhatsApp's linked-device keys in `private.db`, resolves under the
+  sandbox's state directory, and a sandbox test asserts that its path is inside the temporary root, as wa's does.
 - **Exceptions:** none. Until a CLI adopts the shared setup, its sandbox does not replace `@napi-rs/keyring`; tg and
   max only scope the keyring entry through environment variables.
 - **Applies to:** all CLIs and the shared packages. **Since:** cli-base 0.41.0. **Rulings:** none.
@@ -220,7 +223,9 @@ and which run after merge is in [CI](ci.md).
 - **Example:** live scenarios run by hand, by the owner or with the owner's yes, on test profiles and test chats
   only. The cast lives in an ignored file, no profile is assumed, and the record keeps the shape of each answer,
   never its content. When a scenario is run again, the sentence it supports is updated.
-- **Exceptions:** none.
+- **Exceptions:** a messenger with no test accounts, such as WhatsApp, where a second account or a second linked
+  device would change the owner's real one, runs live scenarios on the owner's profile and only in the owner's own
+  chat (the chat with themselves). It never writes to another person, and still runs only with the owner's yes.
 - **Applies to:** all CLIs that talk to a real account. **Since:** cli-base 0.41.0. **Rulings:** none.
 
 ## Sources

package/docs/standards/toolchain.md

@@ -1,10 +1,12 @@
 # Toolchain
 
+<!-- cspell:ignore gofmt -->
+
 ## Scope
 
 How a repository is built and checked before review: the shared presets and `standards:check`, strict TypeScript,
 the shared Biome preset and its grit plugins, the file size cap, import cycles, layer boundaries as lint, the command
-lint, spelling and Markdown lint.
+lint, spelling, Markdown lint, and the checks for a Go part.
 
 Rule ids on this page are `WC-TOOL-<n>`. How to read a rule, how ids work and which rule wins are in the
 [index](README.md). What runs on which trigger is on the [CI page](ci.md).
@@ -156,7 +158,8 @@ cli-testing, cli-docs, plus community itself.
   in [WC-LAY-7](layout.md#wc-lay-7--treat-300-and-500-lines-as-review-signals).
 - **Exceptions:** a file that is one cohesive unit may get its own override, listed by path in `biome.json` (tg
   `src/telegram/adapter.ts`; four files in cli-core). A smaller cap is allowed: zoom uses 500. cli-base, cli-testing,
-  cli-docs and community have no cap yet.
+  cli-docs and community have no cap yet. Biome reads only JavaScript and TypeScript, so the cap does not cover
+  code in another language, such as wa's Go engine; the review signals of WC-LAY-7 still apply to it.
 - **Applies to:** the ten repositories. **Since:** cli-base 0.41.0. **Rulings:** none.
 
 ### WC-TOOL-14 · Turn on the import cycle rule
@@ -223,6 +226,18 @@ cli-testing, cli-docs, plus community itself.
 - **Exceptions:** memo, drive, cli-base and cli-core do not run `rumdl` yet.
 - **Applies to:** the CLIs and cli-testing. **Since:** cli-base 0.41.0. **Rulings:** none.
 
+### WC-TOOL-20 · Build a Go part with the version in `go.mod`, and check it with gofmt, vet and its tests
+
+- **Why:** the TypeScript checks do not read Go, so a Go part with no checks of its own drifts without anyone seeing
+  it.
+- **Enforced by:** `whatsapp-cli: engine-pr.yml:engine` · `whatsapp-cli: ci.yml:engine`.
+- **Example:** every workflow that builds the Go part uses `actions/setup-go` with `go-version-file` pointing at its
+  `go.mod`, never a version written in the workflow. A path-scoped pull request job and full validation both run
+  `gofmt -l .` (any file listed fails), `go vet ./...` and `go test ./...` in the Go folder. wa's engine is the
+  example.
+- **Exceptions:** none.
+- **Applies to:** CLIs with a Go part (wa). **Since:** cli-base 0.44.0. **Rulings:** none.
+
 ## 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.43.5",
+  "version": "0.44.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",