Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,13 @@

Museon CLI follows semantic versioning for its package and command contract.

## 2.2.0

Declarative Agentic Campaign specs.

- New `agentic-campaign +apply-spec --campaign-id <id> --file spec.yaml`: one YAML/JSON file declares Personas and Topics under your own keys, Formats by key -> id, and Plans with their format x topic pairs, an optional exact member roster and an optional dated calendar (`schedule.rule` walks the pairs one per day; `schedule.cells` pins any day, optionally for one account). Without `--preview-token` it previews the diff and returns a token; with the token it applies. Re-applying the same file changes nothing; a changed day re-commits only that Plan. Applying generates nothing by itself.
- `ai-slideshow publish +create-schedule`, `+preview-schedule-plan`, `+submit-schedule-plan`, the managed-publishing skill and the task guide point multi-day Campaign calendars to `+apply-spec`.

## 2.1.0

Agentic Creative Campaign publish time and one-off Plan posts.
Expand Down
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -140,7 +140,7 @@ If you prefer to install the CLI yourself, use Python 3.11+, `uv`, and the exact
wheel from the official GitHub release:

```bash
uv tool install "https://github.com/Museon-AI/museon-cli/releases/download/v2.1.0/museoncli-2.1.0-py3-none-any.whl"
uv tool install "https://github.com/Museon-AI/museon-cli/releases/download/v2.2.0/museoncli-2.2.0-py3-none-any.whl"
```

Then continue with Skill setup and browser authorization:
Expand Down
2 changes: 1 addition & 1 deletion README.zh-CN.md
Original file line number Diff line number Diff line change
Expand Up @@ -111,7 +111,7 @@ MuseOn 只有组织:访问权限由组织角色加 Campaign 范围决定。每
固定版本的 wheel:

```bash
uv tool install "https://github.com/Museon-AI/museon-cli/releases/download/v2.1.0/museoncli-2.1.0-py3-none-any.whl"
uv tool install "https://github.com/Museon-AI/museon-cli/releases/download/v2.2.0/museoncli-2.2.0-py3-none-any.whl"
```

安装成功后继续配置 Skills 和浏览器授权:
Expand Down
374 changes: 367 additions & 7 deletions contracts/command-catalog.json

Large diffs are not rendered by default.

1 change: 1 addition & 0 deletions contracts/task-index.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -773,6 +773,7 @@ chapters:
- agentic-campaign.plan-attribution
- agentic-campaign.campaign-update: "Change the name by itself. Publish window and --publish-timezone may change while active; future not-yet-generated slots move to the new time."
- agentic-campaign.plan-update
- agentic-campaign.apply-spec: "Create or overwrite personas, topics, plans, members and a dated calendar from one spec file. Preview first, apply with the returned preview token."
- agentic-campaign.plan-extra-post: "One more post on top of the daily one (e.g. a missed day). A manual ai-slideshow publish schedule on these accounts instead replaces that day's automatic post."
- agentic-campaign.campaign-pause
- agentic-campaign.campaign-activate
Expand Down
9 changes: 5 additions & 4 deletions docs/agent-discoverability.md
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@ after changing specs; `tests/test_docs_sync.py` fails CI on drift.

<!-- BEGIN GENERATED COMMANDS (scripts/gen_command_docs.py) -->

494 commands across 17 domains (source of truth: `museoncli schema`).
495 commands across 17 domains (source of truth: `museoncli schema`).

### research

Expand Down Expand Up @@ -309,8 +309,8 @@ after changing specs; `tests/test_docs_sync.py` fails CI on drift.
| `ai-slideshow publish +bulk-set-asset-pools` | destructive | yes | `--yes` | async_run | Submit one durable Cloud Task job to change publish asset pools for MULTIPLE accounts. Use this instead of issuing one write per account or writing Python/shell scripts; keep the single command for small, precise one-account edits. This batch command is preferred when atomically configuring all five pools for one account. Requires the opaque token and identical normalized patches from a fresh live preview, plus a stable idempotency key and --yes. After submission, poll only +get-asset-pool-job and inspect every failed/skipped account. If preview marks any fully-managed account requires_managed_operation_approved=true, relay its impact and add --managed-operation-approved only after explicit approval; without it those accounts fail per-account. |
| `ai-slideshow publish +get-asset-pool-job` | read | — | — | direct | Read durable asset-pool batch progress and per-account results. This is the only state source after +bulk-set-asset-pools; do not rescan accounts or loop +bulk-get-asset-pools for verification. |
| `ai-slideshow publish +cancel-asset-pool-job` | write | yes | — | direct | Request cancellation of a durable asset-pool batch job. Stops account work not yet started but does not roll back accounts already completed. |
| `ai-slideshow publish +preview-schedule-plan` | read | — | — | direct | Live-preview a durable schedule-plan operation without writing. --operation cancel-only is the primary way to inspect deletion of current eligible schedule items: it returns cancellable/protected counts by status and an opaque token for the matching batch. For --operation plan, use this before replace-non-published; unlike generic --dry-run, it asks the server to inspect current conflicts, account assets, product bindings, and BGM availability. After resolving account IDs in one bulk social-account +list call, invoke this preview directly; do not preflight with per-account asset, BGM, schedule, or publish-version calls. The response preview_token must be passed unchanged to the matching replace submission. On an account in an Agentic Creative Campaign a manual row becomes that day's Plan post and replaces the automatic post of the day unless it is already publishing (the cadence adds none); its format/topic must be one of the Plan's current reference pairs, otherwise AGENTIC_PLAN_PAIR_NOT_IN_PLAN. To add a post on top of the daily one use `agentic-campaign plan +extra-post`. |
| `ai-slideshow publish +submit-schedule-plan` | destructive | yes | `--yes` | async_run | On an account in an Agentic Creative Campaign a manual row becomes that day's Plan post and replaces the automatic post of the day unless it is already publishing (the cadence adds none); its format/topic must be one of the Plan's current reference pairs, otherwise AGENTIC_PLAN_PAIR_NOT_IN_PLAN. To add a post on top of the daily one use `agentic-campaign plan +extra-post`. Submit one durable asynchronous schedule-plan operation. --operation cancel-only is the primary batch deletion path for current eligible schedule items; it requires the matching preview token and reports cancelled, already cancelled, and protected results by prior status. For --operation plan, create MULTIPLE accounts or MULTIPLE occurrences. MUST use this command instead of looping social-account +list-schedules/+create-schedule/+delete-schedule or Python/shell scripts. One plan accepts up to 200 accounts and 5,000 total occurrences. BGM mode required makes an account fail when its pool has no valid BGM; it never silently creates a no-BGM occurrence. After submission, the only state source is +get-schedule-plan-job. When --bgm-policy required finishes with status succeeded, the server guarantees every created occurrence has a concrete BGM; use bgm_bound_count/summary.bgm_bound and never call schedule-list, bgm-asset-list, or routines to verify it. Inspect every failed/skipped account. replace-non-published requires the opaque preview token from a matching live preview and fails closed when the preview has drifted. --idempotency-key is required: reuse it only for retries of the same submission, and use a new key for an intentional new job. Copy full canonical account UUIDs and the preview token verbatim from the successful preview; never reconstruct them. |
| `ai-slideshow publish +preview-schedule-plan` | read | — | — | direct | Live-preview a durable schedule-plan operation without writing. --operation cancel-only is the primary way to inspect deletion of current eligible schedule items: it returns cancellable/protected counts by status and an opaque token for the matching batch. For --operation plan, use this before replace-non-published; unlike generic --dry-run, it asks the server to inspect current conflicts, account assets, product bindings, and BGM availability. After resolving account IDs in one bulk social-account +list call, invoke this preview directly; do not preflight with per-account asset, BGM, schedule, or publish-version calls. The response preview_token must be passed unchanged to the matching replace submission. On an account in an Agentic Creative Campaign a manual row becomes that day's Plan post and replaces the automatic post of the day unless it is already publishing (the cadence adds none); its format/topic must be one of the Plan's current reference pairs, otherwise AGENTIC_PLAN_PAIR_NOT_IN_PLAN. To add a post on top of the daily one use `agentic-campaign plan +extra-post`. For a multi-day calendar across a Campaign's accounts use `agentic-campaign +apply-spec`. |
| `ai-slideshow publish +submit-schedule-plan` | destructive | yes | `--yes` | async_run | On an account in an Agentic Creative Campaign a manual row becomes that day's Plan post and replaces the automatic post of the day unless it is already publishing (the cadence adds none); its format/topic must be one of the Plan's current reference pairs, otherwise AGENTIC_PLAN_PAIR_NOT_IN_PLAN. To add a post on top of the daily one use `agentic-campaign plan +extra-post`. For a multi-day calendar across a Campaign's accounts use `agentic-campaign +apply-spec`.Submit one durable asynchronous schedule-plan operation. --operation cancel-only is the primary batch deletion path for current eligible schedule items; it requires the matching preview token and reports cancelled, already cancelled, and protected results by prior status. For --operation plan, create MULTIPLE accounts or MULTIPLE occurrences. MUST use this command instead of looping social-account +list-schedules/+create-schedule/+delete-schedule or Python/shell scripts. One plan accepts up to 200 accounts and 5,000 total occurrences. BGM mode required makes an account fail when its pool has no valid BGM; it never silently creates a no-BGM occurrence. After submission, the only state source is +get-schedule-plan-job. When --bgm-policy required finishes with status succeeded, the server guarantees every created occurrence has a concrete BGM; use bgm_bound_count/summary.bgm_bound and never call schedule-list, bgm-asset-list, or routines to verify it. Inspect every failed/skipped account. replace-non-published requires the opaque preview token from a matching live preview and fails closed when the preview has drifted. --idempotency-key is required: reuse it only for retries of the same submission, and use a new key for an intentional new job. Copy full canonical account UUIDs and the preview token verbatim from the successful preview; never reconstruct them. |
| `ai-slideshow publish +get-schedule-plan-job` | read | — | — | direct | Read durable schedule-plan operation progress and per-account results. This is the only state source after submission. cancel-only results include cancelled and protected counts by prior status. For plan with --bgm-policy required and status succeeded, bgm_bound_count/summary.bgm_bound is the server-owned proof that every created occurrence has concrete BGM; never call schedule-list, bgm-asset-list, or routines for post-write verification, rescan accounts, or rely on /tmp state. |
| `ai-slideshow publish +cancel-schedule-plan-job` | write | yes | — | direct | Abort unfinished work in a durable schedule-plan job. This is job control only: it never deletes schedule items already created. Use +preview-schedule-plan/+submit-schedule-plan --operation cancel-only when the operator wants schedule items removed. |
| `ai-slideshow publish +get-config` | read | — | — | direct | Read account publish configuration, including the account-wide output language used for overlays, captions, and hashtags. |
Expand All @@ -323,7 +323,7 @@ after changing specs; `tests/test_docs_sync.py` fails CI on drift.
| `ai-slideshow publish +list-schedules` | read | — | — | direct | List account publish schedule items. |
| `ai-slideshow publish +get-schedule` | read | — | — | direct | Read one account publish schedule item. |
| `ai-slideshow publish +generate-schedule` | write | yes | — | async_run | Start content generation for one account publish schedule item. |
| `ai-slideshow publish +create-schedule` | write | yes | — | direct | Create one manual account publish schedule item. On an account in an Agentic Creative Campaign a manual row becomes that day's Plan post and replaces the automatic post of the day unless it is already publishing (the cadence adds none); its format/topic must be one of the Plan's current reference pairs, otherwise AGENTIC_PLAN_PAIR_NOT_IN_PLAN. To add a post on top of the daily one use `agentic-campaign plan +extra-post`. |
| `ai-slideshow publish +create-schedule` | write | yes | — | direct | Create one manual account publish schedule item. On an account in an Agentic Creative Campaign a manual row becomes that day's Plan post and replaces the automatic post of the day unless it is already publishing (the cadence adds none); its format/topic must be one of the Plan's current reference pairs, otherwise AGENTIC_PLAN_PAIR_NOT_IN_PLAN. To add a post on top of the daily one use `agentic-campaign plan +extra-post`. For a multi-day calendar across a Campaign's accounts use `agentic-campaign +apply-spec`. |
| `ai-slideshow publish +update-schedule` | write | yes | — | direct | Update one account publish schedule item. |
| `ai-slideshow publish +delete-schedule` | write | yes | — | direct | Cancel one account publish schedule item. |
| `ai-slideshow cta-target +list` | read | — | — | direct | List a product's CTA targets (what its posts point viewers to): title, Markdown body, images and status. Staff only (the server refuses other callers). |
Expand Down Expand Up @@ -397,6 +397,7 @@ after changing specs; `tests/test_docs_sync.py` fails CI on drift.
| `agentic-campaign plan +supply-update` | write | yes | — | direct | Set reviewed reference pairs for a Museon persona Plan. This opens a proposal; it does not start publishing. Keep existing pairs when appending. Never creates a Format × Topic cross product. |
| `agentic-campaign plan +account-control` | destructive | yes | `--yes` | direct | Control one explicitly selected Museon managed member. Enable after reviewed rollout; pause/resume preserve membership; stop retires and releases it. Already-submitted posts keep reconciling. |
| `agentic-campaign plan +extra-post` | write | yes | — | direct | Schedule one more post for one member account of a Plan, outside its daily cadence (for example to make up a missed day). The post uses one of the Plan's current reference pairs (--element-id, or the Plan's rotation when omitted), is generated and published by Museon like the daily posts, and neither replaces nor occupies that day's daily post. The account must be a member with automatic execution enabled, and --scheduled-at (ISO-8601 with offset) at least 30 minutes ahead. Use this instead of `ai-slideshow publish` schedules for Agentic Campaign accounts. |
| `agentic-campaign +apply-spec` | write | yes | — | direct | Create or overwrite a whole Agentic Campaign from one spec file: Personas and Topics declared inline under your own keys, Formats referenced by key -> id, and Plans with their format x topic pairs, optional member accounts and an optional dated calendar (a sequence rule over the pairs plus explicit cells; a cell may name one account). Run once without --preview-token to see the diff and get a token, show the diff to the user, then run again with --preview-token to apply. Re-applying the same file is a no-op; a changed day re-commits only that Plan. Calendar dates are in the Campaign publish timezone. Applying never generates content by itself; posts are generated for member accounts as their days come up. Prefer this over chaining +plan-create / plan +supply-update / plan +members-reconcile / per-day schedules. |
| `agentic-campaign plan +posts` | read | — | — | direct | Read this Plan's posts and metrics by account or reference. Missing metrics are not zero results; platform acceptance is not public-post confirmation. |
| `agentic-campaign +campaign-review-only` | write | yes | — | direct | Require manual review for future reference/persona/strategy changes in this Museon Campaign, and disable automatic recruitment. Existing confirmed publishing continues. New CLI campaigns use this policy by default. |
| `agentic-campaign plan +members-reconcile` | write | yes | — | direct | Atomically reconcile a Plan's managed accounts and matching Plan budget. The CLI reads current versions, raises Campaign total budget only when required, and submits the member/budget change as one compare-and-swap operation. |
Expand Down
Loading
Loading