maeve-cli 0.9.0 → 0.10.0

package/README.md

@@ -150,14 +150,17 @@ maeve media:list --workspace <id> --type image --label-ids <id,id> --favorite
 maeve media:list --workspace <id> --state deleted
 maeve media:upload ./image.png --workspace <id>
 maeve media:get --workspace <id> --id <mediaId>
+maeve media:usage-history --workspace <id> --id <mediaId>
 maeve media:update --workspace <id> --id <mediaId> --json media-update.json
 maeve media:download-url --workspace <id> --id <mediaId>
 maeve media:view-url --workspace <id> --id <mediaId>
 maeve media:archive --workspace <id> --id <mediaId>
 maeve media:delete --workspace <id> --id <mediaId>
+maeve media:restore --workspace <id> --id <mediaId>
+maeve media:delete-permanent --workspace <id> --id <mediaId> --yes
 ```
 
-`media:delete` and `media:bulk-delete` move active media to the Bin. The API returns `deleteAfter`; media attached to scheduled posts is blocked with `MEDIA_ATTACHED_TO_SCHEDULED_POST`.
+`media:delete` and `media:bulk-delete` move active media to the Bin. The API returns `deleteAfter`; media attached to scheduled posts is blocked with `MEDIA_ATTACHED_TO_SCHEDULED_POST`. Use `media:restore` to bring an item back from the Bin, or `media:delete-permanent` to remove it for good (requires `--yes`).
 
 Folders and labels:
 
@@ -175,9 +178,28 @@ maeve media:labels:update --workspace <id> --id <labelId> --json media-label.jso
 maeve media:labels:delete --workspace <id> --id <labelId>
 maeve media:labels:attach --workspace <id> --id <mediaId> --json media-label-ids.json
 maeve media:labels:detach --workspace <id> --id <mediaId> --json media-label-ids.json
+maeve media:labels:usage --workspace <id> --label-ids <id,id>
+maeve media:labels:health --workspace <id>
+maeve media:labels:archive --workspace <id> --id <labelId>
+maeve media:labels:restore --workspace <id> --id <labelId>
+maeve media:labels:merge --workspace <id> --id <sourceLabelId> --json media-label-merge.json
 ```
 
-`media:labels:*` is the canonical Media Room organization command family. If a global install still shows `media:tags:*`, upgrade `maeve-cli`.
+`media:labels:*` is the canonical Media Room organization command family. If a global install still shows `media:tags:*`, upgrade `maeve-cli`. `media:labels:merge` folds the source label into a target; its payload is `{ "targetLabelId": "<id>" }`.
+
+Label groups:
+
+```bash
+maeve media:label-groups:list --workspace <id>
+maeve media:label-groups:create --workspace <id> --json label-group.json
+maeve media:label-groups:update --workspace <id> --id <groupId> --json label-group.json
+maeve media:label-groups:reorder --workspace <id> --json label-group-order.json
+maeve media:label-groups:add-labels --workspace <id> --id <groupId> --json label-ids.json
+maeve media:label-groups:ungroup-labels --workspace <id> --json label-ids.json
+maeve media:label-groups:delete --workspace <id> --id <groupId> --json label-group-delete.json
+```
+
+`media:label-groups:reorder` takes the full `{ "groupIds": [...] }` order. `add-labels` and `ungroup-labels` take `{ "labelIds": [...] }`. `delete` takes `{ "mode": "archive-labels" }` or `{ "mode": "ungroup-labels" }` to say what happens to the labels in the group.
 
 Bulk operations:
 
@@ -187,6 +209,8 @@ maeve media:bulk-move --workspace <id> --json media-bulk-move.json
 maeve media:bulk-label --workspace <id> --json media-bulk-labels.json
 maeve media:bulk-unlabel --workspace <id> --json media-bulk-labels.json
 maeve media:bulk-delete --workspace <id> --json media-ids.json --yes
+maeve media:bulk-restore --workspace <id> --json media-ids.json
+maeve media:bulk-delete-forever --workspace <id> --json media-ids.json --yes
 ```
 
 ### Content
@@ -201,7 +225,6 @@ maeve content:schedule --workspace <id> --id <contentId> --scheduled-at "2026-05
 maeve content:intended-time --workspace <id> --id <contentId> --scheduled-at "2026-05-01T10:00:00+10:00"
 maeve content:notes --workspace <id> --id <contentId> --notes "<p>Planning notes</p>"
 maeve content:notes --workspace <id> --id <contentId> --json notes.json
-maeve content:workflow --workspace <id> --id <contentId> --status drafting
 maeve content:publish --workspace <id> --id <contentId> --yes
 maeve content:published-caption --workspace <id> --id <contentId> --json published-caption.json --yes
 maeve content:archive --workspace <id> --id <contentId>
@@ -248,6 +271,52 @@ maeve client-reviews:update-participant --workspace <id> --batch <batchId> --jso
 maeve client-reviews:comment --workspace <id> --batch <batchId> --json comment.json
 ```
 
+### Campaigns
+
+```bash
+maeve campaigns:list --workspace <id> --include-phases
+maeve campaigns:get --workspace <id> --id <campaignId>
+maeve campaigns:content --workspace <id> --id <campaignId> --status scheduled
+maeve campaigns:create --workspace <id> --json campaign.json
+maeve campaigns:update --workspace <id> --id <campaignId> --json campaign.json
+maeve campaigns:archive --workspace <id> --id <campaignId>
+maeve campaigns:restore --workspace <id> --id <campaignId>
+maeve campaigns:phases:list --workspace <id> --id <campaignId>
+maeve campaigns:phases:create --workspace <id> --id <campaignId> --json campaign-phase.json
+maeve campaigns:phases:replace --workspace <id> --id <campaignId> --json campaign-phases.json
+maeve campaigns:phases:update --workspace <id> --id <campaignId> --phase-id <phaseId> --json campaign-phase.json
+maeve campaigns:phases:delete --workspace <id> --id <campaignId> --phase-id <phaseId> --yes
+```
+
+Use `campaigns:list` and `campaigns:get` to find the campaign and phase IDs that
+`content:create` and `content:update` accept in `campaignId` / `campaignPhaseId`. Create
+payload: `name`, `startDate`, and `endDate` are required (dates are ISO 8601); `color`,
+`goal`, `description`, `targetPlatforms`, `estimatedBudget`, `actualBudget`, and
+`budgetCurrency` are optional. `campaigns:phases:replace` takes the full `{ "phases": [...] }`
+array.
+
+```json
+{
+  "name": "May launch",
+  "startDate": "2026-05-01",
+  "endDate": "2026-05-31",
+  "color": "#2563EB",
+  "targetPlatforms": ["instagram", "facebook"]
+}
+```
+
+### Strategy
+
+Read-only. The CLI exposes the strategy reads the public API serves; strategy is edited in
+the app.
+
+```bash
+maeve strategy:foundation --workspace <id>
+maeve strategy:goals --workspace <id>
+maeve strategy:goals:metrics --workspace <id>
+maeve strategy:goal --workspace <id> --id <goalId>
+```
+
 ### Taxonomy and hashtags
 
 ```bash
@@ -278,7 +347,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 agency-plan only. It saves the PDF to `--output`. Stdout stays JSON metadata.
+`analytics:report` is team-plan only. It saves the PDF to `--output`. Stdout stays JSON metadata.
 
 ### Inbox
 
@@ -289,6 +358,11 @@ maeve inbox:stats --workspace <id>
 maeve inbox:read --workspace <id> --thread <threadId>
 maeve inbox:unread --workspace <id> --thread <threadId>
 maeve inbox:read-all --workspace <id> --json inbox-read-all.json --yes
+maeve inbox:resolve --workspace <id> --thread <threadId>
+maeve inbox:reopen --workspace <id> --thread <threadId>
+maeve inbox:resolve-all --workspace <id> --json inbox-resolve-all.json --yes
+maeve inbox:resolve-message --workspace <id> --message <messageId>
+maeve inbox:reopen-message --workspace <id> --message <messageId>
 maeve inbox:reply --workspace <id> --thread <threadId> --json inbox-reply.json --yes
 maeve inbox:note --workspace <id> --thread <threadId> --json inbox-note.json
 maeve inbox:moderate --workspace <id> --message <messageId> --json inbox-moderate.json --yes
@@ -296,6 +370,8 @@ maeve inbox:retry-message --workspace <id> --message <messageId> --yes
 maeve inbox:delete-failed --workspace <id> --message <messageId> --yes
 ```
 
+`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.
+
 ### Grid planner
 
 ```bash
@@ -310,6 +386,21 @@ maeve grid:remove-cover --workspace <id> --item <itemId>
 maeve grid:promote --workspace <id> --item <itemId> --json grid-promote.json --yes
 ```
 
+### Boosts
+
+Read-only, team 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.
+
+```bash
+maeve boosts:list --workspace <id> --statuses active,paused
+maeve boosts:get --workspace <id> --id <boostId>
+maeve boosts:performance --workspace <id> --id <boostId>
+maeve boosts:ad-accounts --workspace <id> --integration <integrationId>
+maeve boosts:boosted-content-ids --workspace <id>
+maeve boosts:by-content --workspace <id> --content <contentId>
+```
+
 ## Payloads
 
 ### Content
@@ -355,12 +446,10 @@ Common fields:
 - `settings`: provider settings from integration capabilities only. Media metadata belongs in `contentMedia`.
 - `firstComment`, `shareToFeed`: optional publish behavior fields.
 - `pillarIds`, `formatIds`, `labelIds`: arrays of workspace taxonomy UUIDs.
-- `campaignId`, `campaignPhaseId`: optional campaign links. Use `null` to clear when updating.
-- `priority`: `urgent`, `high`, `medium`, or `low`.
+- `campaignId`, `campaignPhaseId`: optional root-post campaign links. Use `null` to clear when updating.
+- `priority`: optional root-post priority, `urgent`, `high`, `medium`, or `low`.
 - `threadMessages`: items for thread-style content using `captions` and optional `contentMedia`.
 
-`content:workflow` accepts only the user-mutable workflow statuses: `idea` or `drafting`.
-
 `content:published-caption` edits the provider caption for an already-published Facebook item and requires `--yes`.
 
 ```json
@@ -371,7 +460,7 @@ Common fields:
 
 ### Approvals and client reviews
 
-Approval and client review commands need an agency workspace plan and the role shown in each command's `--help`. Payloads mirror the public API DTOs.
+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.
 
 Internal approval request: