@audienti/cli 0.1.45 → 0.1.51

package/CHANGELOG.md

@@ -4,8 +4,57 @@ All notable changes to the Audienti CLI are documented here.
 
 ## [Unreleased]
 
+## [0.1.51] - 2026-09-03
+
+### Added
+
+- Add first-class `audienti inbox-ops queue`, `filters`, and `rule` commands backed by owner-scoped account APIs, authoritative row-derived sender/domain identities, all four allow/filter rule combinations, and unchanged JSON output.
+
+## [0.1.50] - 2026-09-02
+
+### Added
+
+- Add preview-first `audienti prospects move-account` with dual-account selection, optional destination assignment, motion and list mappings, manifest-bound apply, stable human-readable summaries, and unchanged final JSON output.
+
+## [0.1.49] - 2026-09-02
+
+### Added
+
+- Expose configured user and social-cookie proxy geography, effective proxy source, and server-calculated LinkedIn quotas, warm-up ramp, outstanding-invitation inventory state, and current invitation capacity in `audienti setup play preflight` without exposing proxy or authentication secrets.
+
+## [0.1.48] - 2026-09-02
+
+### Added
+
+- Add account-scoped `audienti users automation show` and preview-first `update` commands for principal-specific LinkedIn controls, category and aggregate visibility limits, warm-up ramping, unchanged JSON readback, and explicit `--apply` persistence.
+- Add reversible `audienti icps archive` and `restore` commands, active/archived/all list filtering, lifecycle status in ICP analytics, and inspectable primary-motion and preserved-secondary-link effects.
+
+## [0.1.47] - 2026-09-02
+
+### Added
+
+- Expose server-derived social-cookie active days, working hours, effective timezone, and current in-window status in `audienti setup play preflight`.
+
+### Changed
+
+- Allow `audienti motions update <motn_id> --payload <file.json>` to replace an account-scoped motion principal and backing list, including `list_id: null` clearing.
+
+## [0.1.46] - 2026-09-02
+
+### Added
+
+- Add `audienti analytics icps` and the account-scoped ICP analytics API for current source-ICP prospect mix, rolling seven-day contribution, per-ICP counts, creation timestamps and human-readable ages, and explicit unattributed semantics.
+
+### Changed
+
+- Allow `audienti motions update <motn_id> --status closing` for motion wind-downs that stop discovery while admitted Operator work drains.
+
 ## [0.1.45] - 2026-09-02
 
+### Added
+
+- Add `audienti analytics motions` and the account-scoped motion analytics API for current prospect mix, rolling seven-day recorded-source contribution, per-motion counts, explicit attribution semantics, and unchanged machine-readable JSON output.
+
 ### Changed
 
 - Keep Operator and analytics API responses within shared product visibility while preserving true-user authorization for Operator queues.

package/README.md

@@ -4,7 +4,8 @@ Audienti CLI is the agent-first command-line client for the Audienti production
 API and the local bridge for Audienti's app-hosted MCP endpoint. It lets local
 coding agents and operators inspect accounts,
 create and manage plays, import prospects, build lists, manage task reminders,
-configure list routing rules, and work supported operator flows.
+configure list routing rules and account-user automation safety, and work
+supported operator flows.
 
 ## Install
 
@@ -137,14 +138,18 @@ Common inspection commands:
 audienti update check
 audienti operator next --plan
 audienti writer test-run <prsp_id>
+audienti analytics motions --json
+audienti analytics icps --json
 audienti motions analytics <motn_id>
 audienti motions run-discovery <motn_id>
 audienti motions quick-start --url https://example.com --wait --confirm
 audienti motions abm-companies <motn_id> add --file abm-domains.txt
 audienti motions abm-companies <motn_id> list
+audienti motions update <motn_id> --status closing
 audienti motions update <motn_id> --status paused
 audienti motions update <motn_id> --start-date 2026-09-01 --end-date 2026-09-30 --maximum-company-count 25
 audienti motions update <motn_id> --own-post-engagement true
+audienti motions update <motn_id> --payload motion-principal-list.json
 audienti motions update <motn_id> --payload motion-signals.json
 audienti motions activate <motn_id>
 audienti motions delete <motn_id> --confirm yes
@@ -167,6 +172,9 @@ audienti company-rules list
 audienti lists routing-rules <list_id> list
 audienti lists routing-rules <list_id> apply
 audienti users activity --window 7d
+audienti users automation show 136 --platform linkedin --json --account <acct_id>
+audienti users automation update 136 --payload automation-controls.json --json --account <acct_id>
+audienti users automation update 136 --payload automation-controls.json --apply --json --account <acct_id>
 audienti analytics prospects --window 24h
 audienti analytics dashboard --play-tag wine_campaign
 audienti analytics metrics --cohort-preset week-to-date
@@ -206,6 +214,21 @@ audienti operator next --plan
 audienti operator next --done --note "Connection request sent."
 ```
 
+Inbox Ops has its own owner-scoped CLI surface. Queue rows expose the stable row
+id used by the rule command; sender and domain values are always derived by the
+server from that authorized row:
+
+```bash
+audienti inbox-ops queue [--page <n>]
+audienti inbox-ops filters
+audienti inbox-ops rule <row_id> --scope sender --disposition filter
+audienti inbox-ops rule <row_id> --scope domain --disposition allow
+```
+
+The four rule combinations mirror the Operator card actions. They update only
+the authenticated owner's personal/global Inbox Ops preferences and do not
+archive mail, call the provider, or add a DNC entry.
+
 To manage simple reminders for yourself:
 
 ```bash
@@ -318,6 +341,112 @@ happened later, such as connection requests sent in a date range. Rebuild the
 list when the event definition or date window changes so the analytics question
 stays auditable.
 
+`audienti setup play preflight` includes the selected sender's server-derived
+working schedule under `social_cookie.automation`, including `active_days`,
+normalized `working_hours`, effective `time_zone`, and current
+`in_working_hours` state. The human-readable output reports the same timezone,
+today's window, and whether provider execution is currently inside the window.
+It also reports the configured user fallback location, the connected account's
+configured and last-verified effective proxy geography, and the proxy source
+without exposing proxy URLs, credentials, egress IPs, or browser session data.
+For LinkedIn, `social_cookie.automation.pacing` includes effective weekly
+quotas, daily targets, motion active days, the outstanding-invitation cap, ramp
+configuration, current outstanding inventory, any inventory blocker, and current
+invitation capacity calculated by the server. A `null` weekly quota means
+unlimited.
+
+Use `users automation` to inspect or change one account user's LinkedIn safety
+policy without changing the saved account selection:
+
+```bash
+audienti users automation show 136 --platform linkedin --json --account acct_example
+audienti users automation update 136 --payload automation-controls.json --json --account acct_example
+audienti users automation update 136 --payload automation-controls.json --apply --json --account acct_example
+```
+
+`update` is preview-only unless `--apply` is present. The CLI always sends
+`platform: "linkedin"` and an explicit `apply` boolean after the file fields,
+so a payload file cannot silently opt into applying a change. The server scopes
+the connected account through the selected account plus account user, preserves
+omitted controls, returns the before and proposed/actual after states, and
+records an audit event only for an applied update. `--json` prints the server
+payload unchanged.
+
+An `automation-controls.json` warm-up payload can use every automation gate,
+independent action limits, an aggregate visibility limit, and a weekly ramp:
+
+```json
+{
+  "automation_controls": {
+    "automatic_sending_enabled": false,
+    "visibility_operations_autopilot_enabled": true,
+    "post_comment_autopilot_enabled": false,
+    "connection_request_autopilot_enabled": false,
+    "inmail_autopilot_enabled": false,
+    "direct_message_autopilot_enabled": false,
+    "email_sending_autopilot_enabled": false,
+    "manual_action_handoff_enabled": false,
+    "risk_cooldown_enabled": true
+  },
+  "action_limits": {
+    "profile_view": { "hourly": 2, "daily": 4, "weekly": 20 },
+    "follow": { "hourly": 2, "daily": 3, "weekly": 15 },
+    "like": { "hourly": 1, "daily": 2, "weekly": 10 },
+    "invite": { "hourly": 1, "daily": 2, "weekly": 10 },
+    "message": { "hourly": 1, "daily": 2, "weekly": 10 },
+    "comment": { "hourly": 1, "daily": 1, "weekly": 5 },
+    "visibility": { "hourly": 3, "daily": 8, "weekly": 40 }
+  },
+  "visibility_ramp": {
+    "enabled": true,
+    "starting_daily_limit": 8,
+    "weekly_increment": 2
+  }
+}
+```
+
+`follow` covers follows and unfollows; `like` covers likes and unlikes;
+`message` covers messages and InMail. `visibility` is the aggregate cap across
+profile views, follows/unfollows, and likes/unlikes. The show/preview readback
+includes configured, default, effective, used, and remaining hourly, daily,
+and weekly values plus the currently binding limits.
+
+Motion update payload mode can replace the selected principal and backing list:
+
+```json
+{
+  "principal_account_user_id": 136,
+  "list_id": "list_abc123"
+}
+```
+
+The principal and list are resolved inside the selected account. Use
+`"list_id": null` to clear the backing list.
+
+To inspect the account's current prospect mix by motion type and compare it
+with the rolling seven-day recorded-source contribution:
+
+```bash
+audienti analytics motions
+audienti analytics motions --json
+```
+
+Current Unattributed counts mean no current motion association. Rolling
+seven-day Unattributed counts mean no attributable recorded source motion; the
+server falls back to the current motion only when recorded source data is
+blank.
+
+To inspect the account's current prospect mix by source ICP and compare it
+with the rolling seven-day source contribution:
+
+```bash
+audienti analytics icps
+audienti analytics icps --json
+```
+
+Unattributed means no attributable account source ICP. The server falls back
+to the current motion ICP only when recorded ICP source data is blank.
+
 To see whether one motion is producing prospects by day, and where each
 produced-day cohort currently sits in the funnel:
 
@@ -362,12 +491,19 @@ To create or update an ICP from a rich JSON payload:
 ```bash
 audienti icps create --payload icp.json
 audienti icps update <icp_id> --payload icp-patch.json
+audienti icps list --status all
+audienti icps archive <icp_id>
+audienti icps restore <icp_id>
 ```
 
 `icps update --payload` accepts the same human-readable facet keys as create.
 Supplied facet collections, such as `company_sizes_attributes`, replace that
 collection in place; omitted fields and collections remain unchanged. Invalid
 lookup values fail server-side without partially applying the patch.
+Archive is reversible and is the normal cleanup action. It removes the ICP from
+new selection, closes active primary motions so admitted work can drain,
+archives inactive primary motions, and preserves secondary motion links.
+Restoring the ICP does not reactivate motions.
 
 To audit one account user's outbound actions, optionally narrowed to one motion
 and one AccountProspect.created_at cohort:
@@ -446,6 +582,19 @@ audienti prospects assign <prsp_id> --assigned-user <account_user_id|me>
 audienti prospects assign <prsp_id> --assigned-user unassign
 ```
 
+To preview moving a prospect and its account-scoped history into another
+account where you are also an administrator:
+
+```bash
+audienti prospects move-account <prsp_id> --account <source_acct_id> --target-account <target_acct_id>
+audienti prospects move-account <prsp_id> --account <source_acct_id> --target-account <target_acct_id> --assigned-user me --target-motion <motn_id> --target-list <list_id> --apply
+```
+
+The command is preview-only unless `--apply` is present. Apply always requests
+a fresh preview first and submits the returned `manifest_digest`, so a move is
+rejected when the underlying state changes. `--json` prints the preview or final
+apply response unchanged.
+
 To make emergency prospect state changes without going through a motion:
 
 ```bash

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@audienti/cli",
-  "version": "0.1.45",
+  "version": "0.1.51",
   "description": "Agent-first command-line client for Audienti.",
   "type": "module",
   "bin": {

package/skills/audienti/SKILL.md

@@ -70,9 +70,17 @@ Useful MCP tools:
 - `auth.me` confirms the token identity.
 - `accounts.list` shows accessible accounts.
 - `setup.play_preflight` returns connected-account readiness and setup or
-  mapping URLs.
+  mapping URLs, including the selected sender's active days, working hours,
+  effective timezone, current in-window status, configured user fallback
+  location, effective proxy geography and source, and server-calculated
+  LinkedIn pacing and outstanding-invitation inventory authority under
+  `social_cookie.automation`. Treat `ready: true` as connection readiness, not
+  approval to start automation.
 - `offers.create`, `icps.create`, and `motions.create` set up the offer, ICP,
   and play.
+- Use `audienti icps list --status all` to audit active and archived ICPs. Use
+  `audienti icps archive <icp_id>` for reversible cleanup and `restore` to make
+  the ICP selectable again; restore never reactivates motions.
 - Use `audienti motions abm-companies <motn_id> add --file <txt|json>` to attach
   a positive company filter list for isolated ABM discovery runs.
 - `analytics.stages` returns stage conversion cohorts and stage aging.
@@ -85,6 +93,9 @@ Useful MCP tools:
   payload or behavior is unclear.
 - Inspect the current resource before a create, update, attach, delete, or
   operator outcome writeback.
+- For account-user automation, run `users automation show`, then preview the
+  exact payload without `--apply`. Apply only after explicit authorization and
+  verify the applied response/readback.
 - Treat the production API as the source of truth. Persist durable work in
   Audienti rather than leaving it only in agent prose.
 - Keep current gaps explicit. Do not imply that unsupported actions execute.
@@ -96,10 +107,15 @@ audienti help agent-workflows
 audienti prospects list --query "name or company" --wide --json
 audienti prospects list --assigned-user unassigned --json
 audienti prospects assign <prsp_id> --assigned-user me --json
+audienti prospects move-account <prsp_id> --account <source_acct_id> --target-account <target_acct_id> --json
+audienti prospects move-account <prsp_id> --account <source_acct_id> --target-account <target_acct_id> --assigned-user me --apply --json
 audienti prospects set-status <prsp_id> --status not_fit --json
 audienti prospects lock <prsp_id> --note "Emergency hold" --json
 audienti prospects unlock <prsp_id> --json
 audienti users activity me --window 7d --json
+audienti users automation show <account_user_id|me> --platform linkedin --json --account <acct_id>
+audienti users automation update <account_user_id|me> --payload automation-controls.json --json --account <acct_id>
+audienti users automation update <account_user_id|me> --payload automation-controls.json --apply --json --account <acct_id>
 audienti prospects import-batch --file prospects.csv --motion <motn_id> --assigned-user me --json
 audienti lists create --name "Target list" --json
 audienti lists routing-rules <list_id> list --json
@@ -111,10 +127,16 @@ audienti motions abm-companies <motn_id> add --file abm-domains.txt --json
 audienti motions abm-companies <motn_id> list --json
 audienti motions update <motn_id> --status paused --json
 audienti motions update <motn_id> --start-date 2026-09-01 --end-date 2026-09-30 --maximum-company-count 25 --json
+audienti motions update <motn_id> --payload motion-principal-list.json --json
 audienti motions activate <motn_id> --json
 audienti motions delete <motn_id> --confirm yes --json
 audienti operator next --json
 audienti operator next --plan
+audienti inbox-ops queue --json
+audienti inbox-ops filters --json
+audienti inbox-ops rule <row_id> --scope <sender|domain> --disposition <allow|filter> --json
+audienti analytics motions --json
+audienti analytics icps --json
 audienti analytics prospects --window 24h --json
 audienti analytics stages --window 30d
 audienti analytics visibility --window 24h --user me --json
@@ -132,6 +154,83 @@ audienti writer test-run <prsp_id> --mode step --branch no-accept --step 3 --rep
 audienti writer test-run show <prsp_id> <rprt_id>
 ```
 
+## Prospect Account Moves
+
+Use `audienti prospects move-account` only to transfer one prospect and its
+account-scoped history, not to copy it. `--account` is the source account and
+`--target-account` is the destination. The authenticated user must administer
+both accounts.
+
+Start with a preview and inspect `eligible`, `blockers`, `mappings`,
+`dispositions`, and `expected_state`:
+
+```bash
+audienti prospects move-account <prsp_id> \
+  --account <source_acct_id> \
+  --target-account <target_acct_id> \
+  --assigned-user <target_account_user_id|me> \
+  --target-motion <target_motn_id> \
+  --target-list <target_list_id> \
+  --json
+```
+
+Omit mappings that were not explicitly chosen; never infer a target motion,
+list, agent, or research mapping by name. Apply only after the preview is
+eligible and the user authorizes the move:
+
+```bash
+audienti prospects move-account <prsp_id> \
+  --account <source_acct_id> \
+  --target-account <target_acct_id> \
+  --assigned-user <target_account_user_id|me> \
+  --target-motion <target_motn_id> \
+  --target-list <target_list_id> \
+  --apply \
+  --json
+```
+
+With `--apply`, the CLI performs a fresh preview and submits that response's
+`manifest_digest`; it does not reuse an older preview. Treat a stale manifest,
+any blocker, or any failed response as not applied, then inspect current source
+and target state before retrying.
+
+## Account-User Automation Safety
+
+`audienti users automation show <account_user_id|me>` resolves one connected
+account through the selected account, account user, and LinkedIn platform. Use
+per-command `--account` for administrative inspection without changing the
+saved default. Fail closed on API ambiguity or missing access; do not substitute
+another connected account.
+
+Automation updates are preview-first:
+
+```bash
+audienti users automation show 136 --platform linkedin --json --account acct_example
+audienti users automation update 136 --payload automation-controls.json --json --account acct_example
+audienti users automation update 136 --payload automation-controls.json --apply --json --account acct_example
+audienti users automation show 136 --platform linkedin --json --account acct_example
+```
+
+The payload object accepts `automation_controls`, `action_limits`, and
+`visibility_ramp`. Action-limit keys are `profile_view`, `follow`, `like`,
+`invite`, `message`, `comment`, and aggregate `visibility`; each action limit
+may provide `hourly`, `daily`, and `weekly`. `follow` covers follow/unfollow,
+`like` covers like/unlike, and `message` covers messages/InMail. A ramp accepts
+`enabled`, `starting_daily_limit`, `weekly_increment`, and optional
+`started_at`.
+
+The CLI wraps the file as `{ automation: { ...payload, platform: "linkedin",
+apply: false|true } }`; file values cannot override the command's platform or
+apply decision. Omitted settings are preserved by the server. Use unchanged
+JSON output to compare current, before, and after snapshots, including policy
+source, schedule/timezone, configured/default/effective limits, used and
+remaining capacity, binding limits, preview/applied state, and applied audit id.
+
+For a new account, keep contact and writing controls disabled, enable risk
+cooldown, and bound `visibility` to the authorized active-day warm-up level.
+Never infer that `ready: true`, paused motions, or prepared queue work authorizes
+provider execution.
+
 List routing-rule create and update commands accept the same normalized
 condition and action data as the list UI. Inspect the ordered rules first, use
 `audienti lists routing-rules help` for the payload contract, and treat `apply`

package/src/api-client.js

@@ -51,6 +51,17 @@ export class AudientiClient {
     return this.requestJson(accountPath(accountId, ["users"]));
   }
 
+  userAutomation(accountId, userId, query = {}) {
+    return this.requestJson(accountPath(accountId, ["users", userId, "automation"], query));
+  }
+
+  updateUserAutomation(accountId, userId, body, query = {}) {
+    return this.requestJson(accountPath(accountId, ["users", userId, "automation"], query), {
+      method: "PATCH",
+      body
+    });
+  }
+
   socialCookies(accountId, query = {}) {
     return this.requestJson(accountPath(accountId, ["social_cookies"], query));
   }
@@ -87,8 +98,8 @@ export class AudientiClient {
     });
   }
 
-  icps(accountId) {
-    return this.requestJson(accountPath(accountId, ["icps"]));
+  icps(accountId, query = {}) {
+    return this.requestJson(accountPath(accountId, ["icps"], query));
   }
 
   icp(accountId, icpId) {
@@ -109,6 +120,20 @@ export class AudientiClient {
     });
   }
 
+  archiveIcp(accountId, icpId) {
+    return this.requestJson(accountPath(accountId, ["icps", icpId, "archive"]), {
+      method: "POST",
+      body: {}
+    });
+  }
+
+  restoreIcp(accountId, icpId) {
+    return this.requestJson(accountPath(accountId, ["icps", icpId, "restore"]), {
+      method: "POST",
+      body: {}
+    });
+  }
+
   addIcpTag(accountId, icpId, body) {
     return this.requestJson(accountPath(accountId, ["icps", icpId, "add_tag"]), {
       method: "POST",
@@ -467,6 +492,13 @@ export class AudientiClient {
     return this.requestJson(accountPath(accountId, ["prospects", prospectId]));
   }
 
+  moveProspectAccount(accountId, prospectId, body) {
+    return this.requestJson(accountPath(accountId, ["prospects", prospectId, "move_account"]), {
+      method: "POST",
+      body
+    });
+  }
+
   replanProspect(accountId, prospectId, body = {}) {
     return this.requestJson(accountPath(accountId, ["prospects", prospectId, "replan"]), {
       method: "POST",
@@ -625,6 +657,17 @@ export class AudientiClient {
     return this.requestJson(accountPath(accountId, ["operator"], query));
   }
 
+  inboxOpsFilters(accountId) {
+    return this.requestJson(accountPath(accountId, ["inbox_ops", "filters"]));
+  }
+
+  updateInboxOpsRule(accountId, rowId, body) {
+    return this.requestJson(accountPath(accountId, ["inbox_ops", rowId, "rule"]), {
+      method: "PATCH",
+      body
+    });
+  }
+
   operatorNext(accountId, query = {}) {
     return this.requestJson(accountPath(accountId, ["operator", "next"], query));
   }
@@ -663,6 +706,14 @@ export class AudientiClient {
     return this.requestJson(accountPath(accountId, ["analytics", "dashboard"], query));
   }
 
+  analyticsMotions(accountId) {
+    return this.requestJson(accountPath(accountId, ["analytics", "motions"]));
+  }
+
+  analyticsIcps(accountId) {
+    return this.requestJson(accountPath(accountId, ["analytics", "icps"]));
+  }
+
   analyticsMetrics(accountId, query = {}) {
     return this.requestJson(accountPath(accountId, ["analytics", "metrics"], query));
   }