xevol 0.12.6 → 0.12.8

package/README.md

@@ -2,7 +2,7 @@
 
 Terminal client for Xevol content execution.
 
-Use it to operate Xevol Work Leads, Contacts, and Companies; ingest content; run analysis; manage prompts; inspect usage; and work across Workspaces.
+Use it to operate Xevol Work Offers, Leads, Contacts, Companies, Deals, Activities, tasks, and search; ingest content; run analysis; manage prompts; inspect usage; and work across Workspaces.
 
 ## Install
 
@@ -53,25 +53,50 @@ xevol workspace switch <workspace-id>
 ### Xevol Work CRM
 - `xevol companies ...` — all Companies reads and commands: list, get, options, create, update, remove, enrich, research, and primary Contact
 - `xevol contacts ...` — all Contacts reads and commands: list, get, create, update, and proposed-fact decisions
+- `xevol offers ...` — every Offers procedure used by Xevol Work Web, including profiles, status, snapshots, audiences, angles, artifacts, revisions, and reviewed generation
 - `xevol leads ...` — every Leads procedure used by Xevol Work Web, including campaigns, review, identity, packets, Deal handoff, outreach, learning, import, insights, and export
+- `xevol deals ...` — list, get, create, update, and stage management
+- `xevol activities ...` — record timelines, counts, personal tasks, activity creation, and task completion
+- `xevol search [query]` — search Companies, Contacts, and Deals across the selected Workspace
 
-Every procedure is a first-class kebab-case subcommand. Use `xevol <group> --help` for the complete list. Common creation has direct flags:
+Every grouped procedure is a first-class kebab-case subcommand; Search is a direct command. Use `xevol <group> --help` for the complete list. Common creation has direct flags:
 
 ```bash
 xevol companies create --name Acme --domain acme.com --json
 xevol contacts create --first-name Ada --email ada@acme.com --company-id <company-id> --json
 xevol leads create --campaign-id <campaign-id> --source MANUAL --company Acme --domain acme.com --json
+xevol deals create --name "Acme renewal" --company-id <company-id> --owner-id <user-id> --amount-cents 125000 --currency USD --json
+xevol activities create --type TASK --subject "Follow up" --deal-id <deal-id> --due-at 2026-09-01T09:00:00Z --json
+xevol search Acme --json
 ```
 
 Complex or less common inputs still accept exactly one of `--input`, `--file`, or stdin:
 
 ```bash
+xevol offers create --input '{"offerProfileId":"...","kind":"SERVICE","name":"Fixed package"}' --json
 xevol leads packet-decide --input '{"packetId":"...","action":"QUALIFY"}' --json
 xevol leads packet-decide --file decision.json --json
 cat decision.json | xevol leads packet-decide --json
 ```
 
-List commands also accept `--query`, `--page`, `--page-size`, `--sort`, and `--dir`. `--workspace-id` overrides the selected Workspace for one command while still relying on server-side membership authorization.
+List commands also accept `--query`, `--page`, `--page-size`, `--sort`, and `--dir`. Deal lists add status, owner, stage, and closing-window facets. Activity commands provide direct timeline anchors, filters, task windows, and limits. `--workspace-id` overrides the selected Workspace for one command while still relying on server-side membership authorization.
+
+Campaign execution commands keep the Work API's reviewed-policy and acknowledgement requirements. In particular, `campaign-execution-activate` can start sending and requires both `expectedEnrollmentCount` and `"acknowledgeSend": true`; the CLI supplies no bypass and the API rechecks current Workspace authority.
+
+### Bounded system workflow
+
+A strict `xevol.system/v1` JSON manifest can manage one Offer profile, up to two reviewed Offers, up to two manual campaigns, and up to five reviewed Leads:
+
+```bash
+xevol system plan -f system.json --json
+xevol system approve -f system.json --plan-hash <hash> --confirm "APPROVE_SYSTEM_PLAN:<hash>" --operation-key <key> --json
+xevol system apply -f system.json --approval-id <id> --approval-token <token> --operation-key <key> --json
+xevol system verify -f system.json --json
+```
+
+Planning and verification are read-only. Approval is bound to the exact manifest and observed state. Apply is atomic and replay-safe. V1 permits no campaign run, outreach, provider write, publication, or external cost, and provides no `--yes` or `--force` bypass.
+
+Work and system commands return `xevol.cli/v1` envelopes in `--json` mode and keep normal handled errors off stderr.
 
 ### Ingestion & content
 - `xevol add [url]` — URL ingestion (YouTube + non-YouTube); omit URL when using `--batch`
@@ -95,6 +120,16 @@ List commands also accept `--query`, `--page`, `--page-size`, `--sort`, and `--d
 - `xevol coordinates locations` — Xevol Coordinates history
 - `xevol whereami` / `xevol locations` — legacy convenience aliases
 
+### Workspace Agent skills
+- `xevol skills list` — list accessible active reviewed skill revisions
+- `xevol skills search <query>` — search accessible skill names and descriptions
+- `xevol skills get <skill-id> --revision <revision-id>` — read one exact revision
+- `xevol skills export <skill-id> --revision <revision-id> --output <directory>` — create a local text-only Agent Skills package without overwriting files
+
+Use `--agent-id` and `--agent-revision` together only when reading a legitimately pinned archived revision. Skill instructions do not grant tools, data access, or permission to act. Exported Workspace material cannot be recalled and may be private.
+
+These commands require a Work API release that provides `agentSkills.discover` and `agentSkills.readRevision`. An older server returns `UNSUPPORTED_SERVER`; the CLI never falls back to the administrative skill-history surface.
+
 ### Interface
 - `xevol agent-help` — machine-oriented guide for agents/scripts using xevol-cli
 - `xevol agent-help --json` — structured command/workflow guide for agents