@scribed/cli 0.1.7 → 0.1.9

package/README.md

@@ -127,7 +127,7 @@ account selection contract as the in-product agent.
 
 ## Team Chat
 
-Chat channels, DMs, messages, threads, search, mentions, files, Drive/Vault handoffs, tasks from messages, member controls, reactions, pins, saved messages, drafts, read state, appearance and status use the same `chat_*` tools in the in-product agent, CLI, stdio MCP, hosted MCP and `/v1/tools`. `team-chat` is in the default MCP catalog. Each call acts as you in the selected workspace; full-seat membership, private-channel access and your role still apply. Read-only credentials cannot change even personal Chat state. Personal Chat has its own opt-in `personal-chat` category, including exact person discovery, requests, messages, authorized history and attachments; it does not grant access to someone else's account or private workspace history.
+Chat channels, DMs, messages, threads, search, mentions, files, Drive/Vault handoffs, tasks from messages, member controls, reactions, pins, saved messages, drafts, read state, appearance and status use the same `chat_*` tools in the in-product agent, CLI, stdio MCP, hosted MCP and `/v1/tools`. `team-chat` is in the default MCP catalog. Each call acts as you in the selected workspace; workspace membership, private-channel access and your role still apply. Read-only credentials cannot change even personal Chat state. Personal Chat has its own opt-in `personal-chat` category, including exact person discovery, requests, messages, authorized history and attachments; it does not grant access to someone else's account or private workspace history.
 
 ```bash
 scribed chat list
@@ -503,7 +503,7 @@ The hosted adapter signs each catalog-derived loopback request with a short-live
 
 An API key belongs to **your Scribed account** and lets a script or unattended integration act as you through the shared tool API. Browser sign-in with `scribed login` and the hosted MCP connection do not need one. An API key is optional for the CLI and local `scribed mcp`; hosted `/mcp` uses OAuth. Create and manage keys in **Settings → Account → API keys**.
 
-Choose a name, expiry, read-only or read/write access, and the exact tools the integration needs. Selected tools stay fixed when new tools are released. “All tools” includes future tools within the key's read/write scope; existing keys keep that behavior until edited. Read/write permission alone never overrides a tool restriction, your current account access, workspace membership, role, seat or billing rules. A workspace restriction limits workspace operations to one workspace you belong to; the key is still account-owned and permitted account tools still act on your personal account. To exclude those tools, leave them out of the tool selection.
+Choose a name, expiry, read-only or read/write access, and the exact tools the integration needs. Selected tools stay fixed when new tools are released. “All tools” includes future tools within the key's read/write scope; existing keys keep that behavior until edited. Read/write permission alone never overrides a tool restriction, your current account access, workspace membership, role or billing rules. A workspace restriction limits workspace operations to one workspace you belong to; the key is still account-owned and permitted account tools still act on your personal account. To exclude those tools, leave them out of the tool selection.
 
 Store the secret in your deployment's secret manager as `SCRIBED_API_KEY`. Start with the **Account basics** preset or explicitly allow `workspaces_list` for this read-only connection check: