kenso 0.1.14 → 0.1.17

package/docs/crm.md

@@ -29,15 +29,7 @@ Globex,globex.com,Manufacturing,"1,200"
 - **The dry run prices the research.** It asks for a credit estimate per 1,000 accounts and puts the sum in the plan: `kind`, `accountCount`, `totalMillicredits`, `availableMillicredits` and `sufficient`.
 - **Rows go 100 per call** to `POST /v1/accounts/bulk-create`.
 
-Each row comes back:
-
-| Status | Meaning |
-|---|---|
-| `created` | A new account; `id` is the account id. Research is queued (`researchQueued` in the summary), or waits for credits (`researchWaitingCredits`) |
-| `skipped`, reason `domain_taken` | A company that is already an account; `id` is that account |
-| `failed` | Kenso refused the row (`reason` is the API's code, `error` names the field) or failed to save it. An item Kenso failed to save is sent once more before it counts as failed |
-
-Rerunning the same file is safe: accounts that exist come back `domain_taken`.
+Each row comes back `created` (`id` is the new account; its research is queued, `researchQueued`, or waits for credits, `researchWaitingCredits`), `skipped` with reason `domain_taken` (already an account; `id` is that account) or `failed` (`reason` is the API's code, `error` names the field; an item Kenso failed to save is sent once more first). Rerunning the same file is safe: accounts that exist come back `domain_taken`.
 
 ## Import people
 
@@ -59,29 +51,16 @@ Bob Ray,,CTO,acme.io,
 - **`--find-emails`** queues an email find (charged in credits) for each person without an email.
 - **Rows go 200 per call** to `POST /v1/people/batch`.
 
-People already in the workspace are matched by email, then LinkedIn URL, so running the same file again creates nobody twice.
-
-| Result | Row status | reason |
-|---|---|---|
-| A new person | `created` | |
-| An existing person, added to the account | `updated` | |
-| An existing person already on the account | `skipped` | `already_on_account` |
-| An existing person, no account asked | `skipped` | `matched` |
-| The person was removed from the account before | `skipped` | `previously_removed` |
-| The account does not exist | `failed` | `account_not_found`: the person was saved without an account. Import the account, then rerun to place them |
-| Kenso refused the row | `failed` | the API's reason |
-
-The summary adds `matched`, `addedToAccounts` and `emailFindsQueued`.
+People already in the workspace are matched by email, then LinkedIn URL, so running the same file again creates nobody twice. A row comes back `created` (a new person), `updated` (an existing person added to the account), `skipped` with reason `already_on_account`, `matched` (no account asked) or `previously_removed`, or `failed`: `account_not_found` saves the person without an account (import the account, then rerun to place them), any other reason is the API's. The summary adds `matched`, `addedToAccounts` and `emailFindsQueued`.
 
 ## Edit accounts, people and opportunities
 
 Apart from `accounts bulk-update`, which sets one `accountType` on up to 500 accounts, there is no bulk edit route, so run the generated `update` command once per row with `--each`. Columns are the command's flags by API name or flag name, and the id column fills the route:
 
 ```bash
-kenso accounts update --each accounts-edit.csv --dry-run
-kenso accounts update --each accounts-edit.csv --yes
-kenso people update --each people-edit.csv --yes
-kenso opportunities update --each deals.csv --yes
+kenso accounts update --each accounts-edit.csv --dry-run   # then the same with --yes
+kenso people update --each people-edit.csv --dry-run
+kenso opportunities update --each deals.csv --dry-run
 ```
 
 ```csv
@@ -90,12 +69,7 @@ accountId,stage,ownerMemberId,overwritePinned
 502,customer,42,true
 ```
 
-A row that changes a field someone pinned in the app fails as a whole (`409 conflict`, `pinned_by_user`: nothing on that record changes, the other fields of the row included), unless the row sets `overwritePinned` to `true` (or you pass `--overwrite-pinned`). To see every flag of an update command:
-
-```bash
-kenso describe accounts update
-kenso accounts update --help
-```
+A row that changes a field someone pinned in the app fails as a whole (`409 conflict`, `pinned_by_user`: nothing on that record changes, the other fields of the row included), unless the row sets `overwritePinned` to `true` (or you pass `--overwrite-pinned`, only with the person's OK). Every flag of an update command: `kenso accounts update --help`.
 
 ## CRM sync
 

package/docs/leads.md

@@ -144,13 +144,13 @@ printf 'id,title\n9001,VP Sales\n' | kenso contacts update --file - --match id -
 
 ## Remove, restore, pause and resume
 
-These four take contact ids from `--ids` (one id per line, or a CSV or JSONL file with an `id` or `contactId` column, or `-` for stdin), or from a search with `--where` (remove, pause and resume). `--where` takes the body of `POST /v1/contacts/search` as JSON, `@file` or `-`, and does the search itself: its plan shows how many contacts match and the first ids, so run no separate search or list first.
+These four take contact ids from `--ids` (one id per line, or a CSV or JSONL file with an `id` or `contactId` column, or `-` for stdin), or from a search with `--where` (remove, pause and resume). `--where` takes the body of `POST /v1/contacts/search` as JSON, `@file` or `-`, and does the search itself: its plan shows how many contacts match and the first ids, so run no separate search or list first. `q` matches names and email addresses only; a company is a `filters` condition on `ContactCompany.Name` (`operator` 2 is contains; `kenso describe contacts search` lists the fields and operators).
 
 ```bash
-kenso contacts remove --ids ids.txt
+kenso contacts remove --ids ids.txt --dry-run
 kenso contacts remove --ids ids.txt --yes
-kenso contacts remove --where '{"campaignIds": [812], "q": "acme"}'
-kenso contacts remove --where '{"campaignIds": [812], "q": "acme"}' --yes
+kenso contacts remove --where '{"campaignIds": [812], "filters": [{"conditions": {"field": "ContactCompany.Name", "operator": 2, "value": "acme"}}]}' --dry-run
+kenso contacts remove --where '{"campaignIds": [812], "filters": [{"conditions": {"field": "ContactCompany.Name", "operator": 2, "value": "acme"}}]}' --yes
 kenso contacts remove --ids big.csv --confirm 2500 --yes
 ```
 

package/docs/reference.md

@@ -1,8 +1,8 @@
 # Kenso CLI command reference
 
-Generated from kenso 0.1.14 (API contracts cd75d09c1648) by `scripts/build-reference.ts`. Do not edit it: `pnpm build` writes it again.
+Generated from kenso 0.1.17 (API contracts 2b8736a3a88d) by `scripts/build-reference.ts`. Do not edit it: `pnpm build` writes it again.
 
-1370 commands, one entry each: summary, API route, feature gate and flag names. Beta commands work only on workspaces with their feature flag; `kenso describe` hides the ones yours cannot use. Every command also takes the global flags below. A command's notes, flag descriptions, body schema and examples: `kenso <resource> <action> --help`, or `kenso describe <resource> <action>` as JSON.
+1376 commands, one entry each: summary, API route, feature gate and flag names. Beta commands work only on workspaces with their feature flag; `kenso describe` hides the ones yours cannot use. Every command also takes the global flags below. A command's notes, flag descriptions, body schema and examples: `kenso <resource> <action> --help`, or `kenso describe <resource> <action>` as JSON.
 
 ## Global flags
 
@@ -19,7 +19,7 @@ Generated from kenso 0.1.14 (API contracts cd75d09c1648) by `scripts/build-refer
 | `--progress` | Print progress to stderr even when it is not a terminal |
 | `--all-commands` | Show beta commands in help |
 | `-h, --help` | Show help |
-| `--version` | Print the version |
+| `--version` | Print the CLI version (only on its own: kenso --version) |
 
 Exit codes: 0 ok, 1 error, 2 usage, 3 auth, 4 not found, 5 some rows failed, 6 rate limited or limit reached, 7 conflict, 8 server error, 130 interrupted.
 
@@ -39,6 +39,7 @@ Exit codes: 0 ok, 1 error, 2 usage, 3 auth, 4 not found, 5 some rows failed, 6 r
 - [agent-team](#agent-team) (9)
 - [ai-assist-reservations](#ai-assist-reservations) (1)
 - [ai-cost-estimate](#ai-cost-estimate) (1)
+- [ai-feedback](#ai-feedback) (4)
 - [ai-line-holds](#ai-line-holds) (2)
 - [ai-lines](#ai-lines) (3)
 - [ai-runs](#ai-runs) (5)
@@ -238,7 +239,7 @@ Exit codes: 0 ok, 1 error, 2 usage, 3 auth, 4 not found, 5 some rows failed, 6 r
 - [mcp-server-authorizations](#mcp-server-authorizations) (2)
 - [mcp-server-presets](#mcp-server-presets) (1)
 - [mcp-servers](#mcp-servers) (9)
-- [me](#me) (29)
+- [me](#me) (31)
 - [meeting-notes](#meeting-notes) (4)
 - [meeting-recordings](#meeting-recordings) (1)
 - [meeting-result-hints](#meeting-result-hints) (3)
@@ -792,6 +793,32 @@ Estimate prompt tokens and list the models a flow can use. `GET /v1/campaigns/{c
 
 Flags: `--campaign-id` (required), `--flow`, `--segment-id`, `--each`, `--concurrency`.
 
+## ai-feedback
+
+### kenso ai-feedback create
+
+Rate an AI output. `POST /v1/ai-feedback`. Beta: needs `ai_feedback`.
+
+Flags: `--surface`, `--target-ref`, `--rating`, `--note`, `--output-snapshot`, `--trace-id`, `--data`, `--each`, `--concurrency`.
+
+### kenso ai-feedback delete
+
+Clear one of the caller's ratings. `DELETE /v1/ai-feedback/{feedbackId}`. Beta: needs `ai_feedback`.
+
+Flags: `--feedback-id` (required), `--each`, `--concurrency`.
+
+### kenso ai-feedback get
+
+Get one of the caller's ratings. `GET /v1/ai-feedback/{feedbackId}`. Beta: needs `ai_feedback`.
+
+Flags: `--feedback-id` (required), `--each`, `--concurrency`.
+
+### kenso ai-feedback signal
+
+Record that the caller regenerated a Ken draft or suggestion. `POST /v1/ai-feedback/signals`. Beta: needs `ai_feedback`.
+
+Flags: `--surface`, `--target-ref`, `--signal`, `--data`, `--each`, `--concurrency`.
+
 ## ai-line-holds
 
 ### kenso ai-line-holds approve
@@ -912,7 +939,7 @@ Flags: `--campaign-id`, `--country`, `--dimension`, `--from`, `--limit`, `--segm
 
 Get reply classifications. `GET /v1/analytics/reply-classifications`.
 
-Flags: `--by-campaign`, `--by-configuration`, `--by-segment`, `--campaign-id`, `--configuration-id`, `--from`, `--segment-id`, `--time-zone`, `--to`, `--no-by-campaign`, `--no-by-configuration`, `--no-by-segment`, `--each`, `--concurrency`.
+Flags: `--by-campaign`, `--by-segment`, `--campaign-id`, `--from`, `--segment-id`, `--time-zone`, `--to`, `--no-by-campaign`, `--no-by-segment`, `--each`, `--concurrency`.
 
 ### kenso analytics get-variant-performance
 
@@ -956,7 +983,7 @@ Flags: `--answer-id` (required), `--each`, `--concurrency`.
 
 ### kenso api
 
-Call any Kenso API route with auth and headers set.
+Call any API route, only when no command fits.
 
 Arguments: `<METHOD>`, `<path>`.
 
@@ -1412,17 +1439,17 @@ Flags: `--action`, `--cursor`, `--limit`, `--occurred-after`, `--occurred-before
 
 ### kenso auth login
 
-Save an API key on this machine (--with-key reads it from stdin). `GET /v1/me`.
+Save an API key (--with-key reads it from stdin: pipe a variable in, no check first). `GET /v1/me`.
 
 Flags: `--device-name`, `--no-browser`, `--with-key`.
 
 ### kenso auth logout
 
-Remove a saved profile and its key from this machine.
+Remove a saved profile and its key.
 
 ### kenso auth status
 
-Show who the key belongs to, the active workspace and when the key expires. API operations: `me.get`, `api-keys.list`.
+Show the key's user, workspace and expiry. API operations: `me.get`, `api-keys.list`.
 
 ## auto-pauses
 
@@ -2922,7 +2949,7 @@ Flags: `--contact-id` (required), `--cursor`, `--limit`, `--occurred-after`, `--
 
 ### kenso contacts export
 
-Export a campaign's contacts to a CSV file (a segment: kenso contact-exports create). API operations: `contact-exports.create`, `jobs.get`, `contact-exports.content`.
+Export a campaign's contacts to CSV (a segment: contact-exports create). API operations: `contact-exports.create`, `jobs.get`, `contact-exports.content`.
 
 Flags: `--campaign`, `--out`, `--timeout`, `--wait`.
 
@@ -2934,7 +2961,7 @@ Flags: `--contact-id` (required), `--each`, `--concurrency`.
 
 ### kenso contacts import
 
-Add leads from a CSV or JSONL file to a campaign, with one result per row. API operations: `contacts.create`, `campaigns.get`, `credit-estimates.create`, `contact-imports.create`, `jobs.get`.
+Add leads from a CSV or JSONL file to a campaign. API operations: `contacts.create`, `campaigns.get`, `credit-estimates.create`, `contact-imports.create`, `jobs.get`.
 
 Flags: `--campaign`, `--file`, `--map`, `--out`, `--server-import`, `--template`, `--timeout`.
 
@@ -2952,7 +2979,7 @@ Flags: `--contact-id` (required), `--each`, `--concurrency`.
 
 ### kenso contacts pause
 
-Pause the campaign sequence of contacts by id (--ids file) or by search (--where), 1,000 per call. API operations: `contacts.bulk-pause`, `contacts.search`. Beta: needs `pause_leads`.
+Pause the campaign sequence of contacts by --ids file or --where filters. API operations: `contacts.bulk-pause`, `contacts.search`. Beta: needs `pause_leads`.
 
 Flags: `--concurrency`, `--ids`, `--out`, `--where`.
 
@@ -2964,19 +2991,19 @@ Flags: `--stage`, `--data`, `--each`, `--concurrency`.
 
 ### kenso contacts remove
 
-Remove (soft-delete) contacts by id (--ids file) or by search (--where), 1,000 per call. API operations: `contacts.bulk-delete`, `contacts.search`.
+Remove (soft-delete) contacts by --ids file or --where filters. API operations: `contacts.bulk-delete`, `contacts.search`.
 
 Flags: `--concurrency`, `--confirm`, `--ids`, `--out`, `--where`.
 
 ### kenso contacts restore
 
-Restore removed contacts by id (--ids) or by a remove run (--run). `POST /v1/contacts/bulk-restore`.
+Restore removed contacts by --ids or by a remove run (--run). `POST /v1/contacts/bulk-restore`.
 
 Flags: `--concurrency`, `--ids`, `--out`, `--run`.
 
 ### kenso contacts resume
 
-Resume the paused sequence of contacts by id (--ids file) or by search (--where), 1,000 per call. API operations: `contacts.bulk-resume`, `contacts.search`.
+Resume the paused sequence of contacts by --ids file or --where filters. API operations: `contacts.bulk-resume`, `contacts.search`.
 
 Flags: `--concurrency`, `--ids`, `--out`, `--where`.
 
@@ -2988,19 +3015,19 @@ Flags: `--company-id`, `--segment-id`, `--email`, `--q`, `--is-qualified`, `--do
 
 ### kenso contacts tag
 
-Add a tag to contacts by id (--ids only: for a campaign, contacts list its ids first). `POST /v1/tags/{tagId}/assignments`.
+Add a tag to contacts by --ids only (a campaign: list its ids first). `POST /v1/tags/{tagId}/assignments`.
 
 Flags: `--concurrency`, `--ids`, `--out`, `--tag`.
 
 ### kenso contacts untag
 
-Remove a tag from contacts by id (--ids only: for a campaign, contacts list its ids first). `DELETE /v1/tags/{tagId}/assignments`.
+Remove a tag from contacts by --ids only (a campaign: list its ids first). `DELETE /v1/tags/{tagId}/assignments`.
 
 Flags: `--concurrency`, `--ids`, `--out`, `--tag`.
 
 ### kenso contacts update
 
-Edit leads from a CSV or JSONL file, matched by id or by email (also one lead). API operations: `contacts.bulk-update`, `contacts.list`.
+Edit leads from a CSV or JSONL file, by id or email (also one lead). API operations: `contacts.bulk-update`, `contacts.list`.
 
 Flags: `--campaign`, `--concurrency`, `--file`, `--map`, `--match`, `--out`.
 
@@ -3276,7 +3303,7 @@ Flags: `--months`, `--data`, `--each`, `--concurrency`.
 
 ### kenso describe
 
-Print the command map as JSON: every command, its flags and body schema.
+The command map as JSON: commands, flags, body schemas.
 
 Arguments: `<resource>` (optional), `<action>` (optional).
 
@@ -3362,7 +3389,7 @@ Flags: `--each`, `--concurrency`.
 
 ### kenso docs
 
-Read the CLI docs offline: the topic list, or one topic as Markdown.
+Offline docs: the topic list, or one topic.
 
 Arguments: `<topic>` (optional).
 
@@ -3370,7 +3397,7 @@ Arguments: `<topic>` (optional).
 
 ### kenso doctor
 
-Check the setup: Node, the config file, the API and the key. `GET /v1/me`.
+Check Node, the config, the API and the key. `GET /v1/me`.
 
 ## domain-health-checks
 
@@ -4398,7 +4425,7 @@ Flags: `--cursor`, `--limit`, `--status`, `--type`, `--all`, `--each`, `--concur
 
 ### kenso jobs wait
 
-Wait for a background job to finish and print it. `GET /v1/jobs/{jobId}`.
+Wait for a background job and print it. `GET /v1/jobs/{jobId}`.
 
 Arguments: `<jobId>`.
 
@@ -4410,13 +4437,13 @@ Flags: `--timeout`, `--type` (required).
 
 Create the Ken chat of an eve session, or return the one that exists. `POST /v1/ken-chats`. Beta: needs `ken_agent`.
 
-Flags: `--eve-session-id`, `--eve-session-ref`, `--title`, `--data`, `--each`, `--concurrency`.
+Flags: `--eve-session-id`, `--eve-session-ref`, `--title`, `--kind`, `--data`, `--each`, `--concurrency`.
 
 ### kenso ken-chats create-message
 
 Append a message to a Ken chat. `POST /v1/ken-chats/{kenChatId}/messages`. Beta: needs `ken_agent`.
 
-Flags: `--ken-chat-id` (required), `--external-id`, `--role`, `--text`, `--duration-ms`, `--data`, `--each`, `--concurrency`.
+Flags: `--ken-chat-id` (required), `--external-id`, `--role`, `--text`, `--duration-ms`, `--trace-id`, `--data`, `--each`, `--concurrency`.
 
 ### kenso ken-chats delete
 
@@ -5208,7 +5235,7 @@ Flags: `--cursor`, `--limit`, `--all`, `--each`, `--concurrency`.
 
 ### kenso mcp call
 
-Call a hosted Kenso MCP tool, such as list_skills or load_skill.
+Call a hosted Kenso MCP tool, such as list_skills (no mcp tools first).
 
 Arguments: `<tool>`.
 
@@ -5332,6 +5359,12 @@ Get the signed-in caller. `GET /v1/me`.
 
 Flags: `--each`, `--concurrency`.
 
+### kenso me get-ai-feedback-state
+
+Get the caller's AI feedback state. `GET /v1/me/ai-feedback-state`. Beta: needs `ai_feedback`.
+
+Flags: `--each`, `--concurrency`.
+
 ### kenso me get-booking-settings
 
 Get my booking settings. `GET /v1/me/booking-settings`. Beta: needs `scheduler`.
@@ -5452,6 +5485,12 @@ Update the caller's profile. `PATCH /v1/me`.
 
 Flags: `--linkedin-url`, `--first-name`, `--last-name`, `--job-title`, `--time-zone`, `--language`, `--data`, `--each`, `--concurrency`.
 
+### kenso me update-ai-feedback-state
+
+Dismiss the coach mark or record the heavy-edit toast. `PATCH /v1/me/ai-feedback-state`. Beta: needs `ai_feedback`.
+
+Flags: `--coach-mark-dismissed`, `--heavy-edit-prompted`, `--no-coach-mark-dismissed`, `--no-heavy-edit-prompted`, `--data`, `--each`, `--concurrency`.
+
 ### kenso me update-booking-settings
 
 Update my booking settings. `PATCH /v1/me/booking-settings`. Beta: needs `scheduler`.
@@ -6970,19 +7009,19 @@ Flags: `--role-id` (required), `--title`, `--company-name`, `--company-domain`,
 
 ### kenso runs list
 
-List batch runs, newest first.
+List batch runs, newest first (finds an interrupted run).
 
 Flags: `--limit`.
 
 ### kenso runs resume
 
-Continue a batch run: rerun its command with --yes.
+Continue an interrupted batch run (its command with --yes, no dry run).
 
 Arguments: `<runId>`.
 
 ### kenso runs show
 
-Show one batch run: its run.json, its last summary and its files.
+Show one batch run and its files.
 
 Arguments: `<runId>`.
 
@@ -7728,7 +7767,7 @@ Flags: `--is-synthetic`, `--no-is-synthetic`, `--data`, `--each`, `--concurrency
 
 ### kenso skill install
 
-Install the kenso-cli Agent Skill for Claude Code, Codex or Cursor.
+Install the kenso-cli skill for Claude Code, Codex or Cursor.
 
 Flags: `--client`, `--dir`, `--force`.
 
@@ -9148,7 +9187,7 @@ Flags: `--all`, `--limit`, `--q`.
 
 ### kenso workspace use
 
-Make a workspace the default for the profile. `GET /v1/workspaces/{workspaceId}`.
+Set the profile's default workspace. `GET /v1/workspaces/{workspaceId}`.
 
 Arguments: `<workspaceId>`.
 

package/docs/studio.md

@@ -30,7 +30,7 @@ kenso studio push 12 --dir ./my-template --publish
 
 `pull` writes every file of the version under `--dir`: text files from the answer, binaries downloaded from signed links and checked against their SHA-256. It overwrites files with the same path and leaves other files in the folder alone. It checks every path before it writes anything, and refuses one that would land outside `--dir` (`unsafe_path`).
 
-`--template-version` picks the version: `draft`, `latest` (the latest published) or a version id. The default is the draft, else the latest published version. (The flag is not `--version`, which prints the CLI version.)
+`--template-version` picks the version: `draft`, `latest` (the latest published) or a version id. The default is the draft, else the latest published version. (The flag is not `--version`: after a command, `--version` fails with `unknown_flag` and points at `--template-version`.)
 
 ```bash
 kenso studio pull 12 --dir ./v3 --template-version 345

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "kenso",
-  "version": "0.1.14",
+  "version": "0.1.17",
   "description": "The Kenso CLI: bulk lead, CRM and Studio work for people and coding agents",
   "license": "MIT",
   "type": "module",
@@ -44,5 +44,5 @@
     "typescript-eslint": "8.71.1",
     "vitest": "5.0.3"
   },
-  "gitHead": "89dc1803f304f8225462a7f4129c861c1e329b97"
+  "gitHead": "4b7b6d671753dee817768174b36add31a0a6897e"
 }

package/skill/kenso-cli/SKILL.md

@@ -1,26 +1,27 @@
 ---
 name: kenso-cli
-description: The Kenso CLI (kenso) for work from a file or over about 50 records - import, update, remove, pause, tag or export leads, import CRM accounts and people, edit Studio templates as local files and fill them, run an API operation per file row. For one record or a question, use the Kenso MCP.
+description: The Kenso CLI (kenso) for work from a file (of any size, even a few ids) or over about 50 records - import, update, remove (delete), pause, tag or export leads, import CRM accounts and people, edit Studio templates as local files and fill them, run an API operation per file row, resume an interrupted run, sign in with a key from a variable (pipe it to kenso auth login --with-key, no check first). For records listed in the message (under about 50), one record or a question, use the Kenso MCP.
 ---
 
-1. Every write runs first with `--dry-run`, never `--yes`; apply with the plan's `next`. `--yes` at once only to continue an interrupted run or apply what the person confirmed.
-2. Many rows are one command with the file as it is (`--file`, `--ids`, `--each`), never a command per row. Run kenso only: no python, awk or shell tests, not even on a file or variable.
-3. Errors are JSON on stderr: follow `next`. `--force` only with the person's OK.
-4. Ids are flags: `--campaign 812` on contacts import, update, export; `--campaign-id 812` on API commands (`contacts list`). `--workspace <id>`; by name `kenso workspace list --q acme`.
+1. Every write runs first with `--dry-run`; apply with the plan's `next`. `--yes` at once only to continue an interrupted run or apply what the person confirmed.
+2. Many rows: one command on the file as it is (`--file`, `--ids`, `--each`). Run kenso only: no python, awk or shell tests, not even on a file or variable.
+3. Any output's `next` is the command to run; errors are JSON on stderr. `--force` only with the person's OK.
+4. Ids are flags: `--campaign 812` on contacts import, update, export; `--campaign-id 812` on API commands. `--workspace <id>`; by name `kenso workspace list --q acme`. Other commands: `kenso --help`; `kenso api <METHOD> <path>` only when none fits.
 
 ```bash
 kenso contacts import --campaign 812 --file leads.csv --dry-run   # skips leads already in; --map '{"Pain": "customVariables.pain_point", "Notes": null}'; over 200 MB --server-import
-kenso contacts update --file edits.csv --match id --dry-run   # also one contact; or --match email --campaign 812
-kenso contacts remove --ids ids.txt --dry-run   # same for pause, resume, restore, tag --tag 31; over 1,000 add --confirm <count>
-kenso contacts remove --where '{"campaignIds": [812], "q": "acme"}' --dry-run   # also pause, resume; the plan shows the matches: no search first
-kenso contacts list --campaign-id 812 --all -o ids > ids.txt   # tag and restore take --ids only: list the ids first
+kenso contacts update --file edits.csv --match id --dry-run   # also one lead; or --match email --campaign 812
+kenso contacts remove --ids ids.txt --dry-run   # also pause, resume, restore; over 1,000: --confirm <count>
+kenso contacts remove --where '{"campaignIds": [812], "filters": [{"conditions": {"field": "ContactCompany.Name", "operator": 2, "value": "acme"}}]}' --dry-run   # also pause, resume; 2 = contains; no search first
+kenso contacts tag --tag 31 --ids ids.txt --dry-run   # tag, restore: --ids only, so first kenso contacts list --campaign-id 812 --all -o ids > ids.txt
+kenso contact-imports create --source campaign --source-campaign-id 10601 --campaign-id 812 --dry-run   # copy another campaign's leads in
 kenso contacts export --campaign 812 --out leads.csv   # a segment: kenso contact-exports create --segment-id 55
-kenso runs list   # an interrupted run (terminal lost): find it, then kenso runs resume <runId>. A changed file is a new run
-kenso accounts import --file accounts.csv --dry-run   # companies; people (any file of people) go in with kenso people import --file people.csv
-kenso studio push 12 --dir ./tpl   # to preview local edits push first (draft only; live needs --publish), then studio preview 12
+kenso runs resume <runId>   # an interrupted run; terminal lost: kenso runs list finds it. A changed file is a new run
+kenso accounts import --file accounts.csv --dry-run   # companies; a file of people: kenso people import --file people.csv
+kenso studio push 12 --dir ./tpl   # to preview local edits push first (draft; live needs --publish), then studio preview 12
 kenso studio fill 12 --accounts ids.txt --dry-run   # or --campaign 10546 --contacts leads.csv
-kenso campaigns update --campaign-id 812 --name Q4 --dry-run   # any API operation; --each rows.csv for many
-kenso mcp call list_skills
+kenso opportunities update --each rows.csv --dry-run   # any API command on a file of rows (CSV or JSONL; keys fill flags and body). One record: kenso campaigns update --campaign-id 812 --name Q4 --dry-run
+kenso mcp call list_skills   # only to list Ken's skills
 ```
 
-`accounts import` charges per new account, `studio fill` per page (again for the same ids in another file): show the estimate first. `pinned_by_user`: with the person's OK, `--overwrite-pinned`. Workflows: `kenso workflows brief` first; secrets only as `{{secrets.NAME}}`. Key: `KENSO_API_KEY`, or any variable piped as the first command, no check or printenv (an empty key is refused): `printf '%s' "$KEY" | kenso auth login --with-key`; never in a flag, output or file. `kenso api` only when no command fits. Flags: `kenso <resource> <action> --help`. More: `kenso docs leads|batch|crm|studio`.
+Charges: `accounts import` per new account, `studio fill` per page (again for ids from another file): show the estimate. `pinned_by_user`: with the person's OK, rerun with `--overwrite-pinned`. Workflows: `kenso workflows brief` first; secrets only as `{{secrets.NAME}}`. Key: `KENSO_API_KEY`, or pipe a variable, no check: `printf '%s' "$KEY" | kenso auth login --with-key`; never in a flag, output or file.