maeve-cli 0.10.0 → 0.11.0

package/README.md

@@ -2,6 +2,10 @@
 
 A command-line tool for the Maeve public API. Schedule posts, manage media, run analytics, and send client reviews from a terminal or a script.
 
+The current package exposes 181 commands across 15 command groups. It is a `/v1` REST client
+and never calls MCP. Inbox automation rules and the 41-operation Workbench v2 API are not CLI
+surfaces. See [`SCOPE.md`](./SCOPE.md) for the complete inclusion and exemption rules.
+
 [![npm](https://img.shields.io/npm/v/maeve-cli.svg)](https://www.npmjs.com/package/maeve-cli)
 [![node](https://img.shields.io/node/v/maeve-cli.svg)](https://nodejs.org)
 [![license](https://img.shields.io/npm/l/maeve-cli.svg)](./LICENSE)
@@ -231,10 +235,14 @@ maeve content:archive --workspace <id> --id <contentId>
 maeve content:restore --workspace <id> --id <contentId>
 maeve content:retry --workspace <id> --id <contentId>
 maeve content:delete --workspace <id> --id <contentId>
+maeve content:recurring-occurrence:cancel --workspace <id> --occurrence <occurrenceId> --yes
+maeve content:recurring-series:cancel --workspace <id> --series <seriesId> --effective-occurrence <occurrenceId> [--expected-version <number>] --yes
 maeve content:failed-count --workspace <id>
 maeve content:pending-approval-count --workspace <id>
 ```
 
+`content:delete` refuses content that belongs to a recurring series; use the recurring cancel commands instead. `content:list` includes a `recurringMetadata` object on recurring-linked items with the `seriesId`, `occurrenceId`, and `seriesVersion` those commands need. `content:recurring-occurrence:cancel` cancels a single occurrence. `content:recurring-series:cancel` cancels the series and every not-yet-published occurrence from the effective occurrence forward. Both require `--yes` because they remove scheduled publishing work.
+
 Approvals, comments, and activity:
 
 ```bash
@@ -347,7 +355,7 @@ maeve analytics:report --workspace <id> --provider instagram --json analytics-re
 
 `analytics:posts` is single-integration. `analytics:posts-aggregate` accepts `--integration-ids` and `--sort-by recent|engagement|views`.
 
-`analytics:report` is team-plan only. It saves the PDF to `--output`. Stdout stays JSON metadata.
+`analytics:report` is standard-plan only. It saves the PDF to `--output`. Stdout stays JSON metadata.
 
 ### Inbox
 
@@ -368,10 +376,49 @@ maeve inbox:note --workspace <id> --thread <threadId> --json inbox-note.json
 maeve inbox:moderate --workspace <id> --message <messageId> --json inbox-moderate.json --yes
 maeve inbox:retry-message --workspace <id> --message <messageId> --yes
 maeve inbox:delete-failed --workspace <id> --message <messageId> --yes
+maeve inbox:tags --workspace <id> --include-archived
+maeve inbox:tags:create --workspace <id> --name "Needs follow-up" --color "#2563eb"
+maeve inbox:tags:update --workspace <id> --tag <tagId> --name "Replied"
+maeve inbox:tags:archive --workspace <id> --tag <tagId>
+maeve inbox:tags:restore --workspace <id> --tag <tagId>
+maeve inbox:tags:delete --workspace <id> --tag <tagId> --yes
+maeve inbox:tags:reorder --workspace <id> --json inbox-tag-order.json
+maeve inbox:tag-thread --workspace <id> --thread <threadId> --tag <tagId>
 ```
 
 `inbox:resolve` and `inbox:resolve-message` accept an optional `--json` file with a resolution reason and note. `inbox:resolve-all` resolves every thread matching the filter payload and requires `--yes`. The reopen commands take no body.
 
+`inbox:tag-thread` replaces the complete tag set on one thread. Repeat `--tag` to assign
+several tags, or omit it to clear all tags. `inbox:tags:delete` removes the tag from every
+conversation and therefore requires `--yes`.
+
+### Task board
+
+```bash
+maeve tasks:list --workspace <id>
+maeve tasks:archive --workspace <id> --limit 50
+maeve tasks:get --workspace <id> --id <taskId> --include-comments --include-activity
+maeve tasks:for-post --workspace <id> --post-id <postId>
+maeve tasks:linkable-posts --workspace <id> --query "launch" --stage drafting
+maeve tasks:comments --workspace <id> --id <taskId>
+maeve tasks:activity --workspace <id> --id <taskId> --limit 50
+maeve tasks:create --workspace <id> --json task.json
+maeve tasks:update --workspace <id> --id <taskId> --json task-update.json
+maeve tasks:move --workspace <id> --id <taskId> --json task-move.json
+maeve tasks:archive-task --workspace <id> --id <taskId>
+maeve tasks:restore --workspace <id> --id <taskId>
+maeve tasks:delete --workspace <id> --id <taskId> --yes
+maeve tasks:comments:create --workspace <id> --id <taskId> --json task-comment.json
+maeve tasks:checklist:create --workspace <id> --id <taskId> --json checklist-item.json
+maeve tasks:checklist:update --workspace <id> --id <taskId> --item <itemId> --json checklist-update.json
+maeve tasks:checklist:move --workspace <id> --id <taskId> --item <itemId> --json checklist-move.json
+maeve tasks:checklist:delete --workspace <id> --id <taskId> --item <itemId> --yes
+```
+
+`tasks:archive` lists archived tasks; `tasks:archive-task` archives one task. Archived tasks
+are read-only until `tasks:restore` brings them back. `tasks:delete` and
+`tasks:checklist:delete` require `--yes`; deleted tasks cannot be restored.
+
 ### Grid planner
 
 ```bash
@@ -388,7 +435,7 @@ maeve grid:promote --workspace <id> --item <itemId> --json grid-promote.json --y
 
 ### Boosts
 
-Read-only, team plan. The CLI reads boost state for reporting but does not create, pause,
+Read-only, standard plan. The CLI reads boost state for reporting but does not create, pause,
 resume, delete, or estimate boosts, because those spend Meta ad budget. Run those from the
 app.
 
@@ -460,7 +507,7 @@ Common fields:
 
 ### Approvals and client reviews
 
-Approval and client review commands need an team workspace plan and the role shown in each command's `--help`. Payloads mirror the public API DTOs.
+Approval and client review commands need a standard workspace plan and the role shown in each command's `--help`. Payloads mirror the public API DTOs.
 
 Internal approval request:
 
@@ -537,6 +584,54 @@ Read-all takes the same filter shape as listing threads. Use `{}` only when you
 }
 ```
 
+### Task board
+
+Create:
+
+```json
+{
+  "title": "Draft launch teaser",
+  "description": "Short teaser for the spring drop.",
+  "priority": "high",
+  "dueAt": "2026-09-01",
+  "assigneeIds": ["00000000-0000-4000-8000-000000000001"],
+  "checklistItemTitles": ["Write caption", "Pick cover image"]
+}
+```
+
+Update payloads carry only the fields to change. Pass `null` to clear a value or remove the
+content post link. Assignee and label arrays are full replacement sets.
+
+```json
+{ "priority": null, "postId": null, "dueAt": "2026-09-05" }
+```
+
+Move (omit both anchors to place the task at the top of the column):
+
+```json
+{ "targetColumnId": "00000000-0000-4000-8000-000000000002", "afterTaskId": null }
+```
+
+Comment (@mentions notify workspace members):
+
+```json
+{ "content": "Ready for review @Brie." }
+```
+
+Checklist create, update, and move:
+
+```json
+{ "title": "Write caption" }
+```
+
+```json
+{ "isCompleted": true }
+```
+
+```json
+{ "beforeItemId": "00000000-0000-4000-8000-000000000003" }
+```
+
 ### Grid planner
 
 Visual-only item: