@scribed/cli 0.1.29 → 0.1.31

package/README.md

@@ -2,8 +2,8 @@
 
 Command-line client + MCP server for Scribed — CRM records, phone + texting, inbox, calendar + booking, transcriptions, HR, the Vault + workspace pages, and automations from the terminal or from an MCP host such as Cursor or Claude. The entire domain surface is **derived from the scribed-agent tool catalog**: nothing is hand-duplicated, so a new eligible catalog tool automatically becomes a CLI command (`scribed call <tool>`) and an MCP tool.
 
-Verified catalog (2026-10-18): **1,102 external tools across 48 categories**;
-581 tools in 28 categories are included in the default core set. Route
+Verified catalog (2026-10-19): **1,149 external tools across 50 categories**;
+584 tools in 27 categories are included in the default core set. Route
 coverage does not imply full UI parity: session-only actions and the remaining
 option audit are tracked in the repository's `output/ui-parity/` reports.
 
@@ -156,6 +156,20 @@ scribed signup --resume --email you@example.com --phone-code <code> --json
 
 Google/Apple consent stays in the browser: run `scribed login`, choose **Sign up**, complete the wizard, and then authorize the CLI. Browser login never collects signup details in the terminal. Subsequent onboarding tools remain limited by their API authorization; the offline signup lifecycle test does not prove live onboarding apply.
 
+### Connect a provider
+
+```bash
+scribed call integration_connect_start provider=google-calendar
+```
+
+Open the returned Scribed link in your signed-in browser and complete the
+provider's consent flow. Then call the returned status tool with its exact
+arguments and check any provider-specific completion conditions. Preparing the
+link does not connect an account. Workspace-owned providers require an explicit
+workspace and the existing admin permissions; Runs cannot start a handoff.
+Supported providers come from the canonical schema. Credentials, payments and
+other consent flows retain their separately documented human steps.
+
 ### Credentials and environment
 
 Credentials live in `${XDG_CONFIG_HOME:-~/.config}/scribed/config.json` (directory `0700`, file `0600`, atomically replaced). Environment overrides for CI always win over the file:
@@ -845,25 +859,23 @@ is a separate verification step.
 For large Personal Notes boards, use `account_notes_list` and `account_note_get`; received shares use `account_notes_shared_list` and `account_note_shared_get`. Confirmed `account_note_create`, `account_note_update` and `account_note_delete` carry the exact board revision and preserve unrelated notes on the server. Never send a partial or truncated board to `account_notes_set`.
 
 
-### Living knowledge
+### Account memory
 
-The shared `knowledge_base_*` tools read and manage the account's personal base
-or one explicitly selected workspace. They are available in the default MCP
-catalog and through `scribed call`:
+The Agent's memory belongs to the signed-in human account. `memory_status` reads
+its consent, configuration and deletion status without returning remembered
+content. Consent changes require the person's own Settings review.
 
 ```sh
-scribed call knowledge_base_status scope=account
-scribed call knowledge_base_manifest scope=workspace workspaceId=<workspace-id> audience=private
-scribed call knowledge_base_search scope=account query="current priorities"
-scribed call knowledge_base_file scope=account revision=3 path=README.md
+scribed call memory_status
+scribed call memory_clear confirmed=true requestId=<stable-request-uuid>
 ```
 
-Copy the returned revision and cursor/offset for subsequent pages. File reads
-return Markdown chunks; exports return paginated JSON containing complete
-Markdown files and metadata. Preserve partial coverage and original source
-permissions. Knowledge settings, updates, corrections, cancellation and rollback
-require explicit confirmation; updates may incur the configured AI usage cost.
-A million-token output budget is spread across many steps and files.
+Clear only when the account holder explicitly asks to forget their Agent memory.
+It deletes the memory messages and representation while preserving the original
+Agent conversations. Keep the same request ID after an uncertain response and
+check status; pending or unknown does not mean completed. These controls accept
+no account, workspace or source selector and are excluded from Runs. The former
+Settings Knowledge Base product and `knowledge_base_*` tools are retired.
 
 Brain Build's local computer knowledge is separate. External AI can query its
 native local MCP server; the Scribed private device relay is not exposed through