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
8 changes: 8 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,14 @@

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

## 2.1.0

Agentic Creative Campaign publish time and one-off Plan posts.

- `agentic-campaign +campaign-create` / `+campaign-update --publish-timezone <IANA>`: the Campaign publish time is `--preferred-publish-windows-json` read in this timezone for every member account (default `Asia/Shanghai`). Both may change while the Campaign is active; future slots that have not started generating move to the new time. The help no longer says config is setup-only.
- New `agentic-campaign plan +extra-post`: one more post for one Plan member outside the daily cadence (for example a missed day), from the Plan's current reference pairs, generated and published by Museon, idempotent per `--idempotency-key`.
- `ai-slideshow publish +create-schedule`, `+preview-schedule-plan` and `+submit-schedule-plan` explain Agentic Campaign accounts: a manual row becomes that day's Plan post and replaces the automatic post of the day unless it is publishing; pairs outside the Plan are rejected with `AGENTIC_PLAN_PAIR_NOT_IN_PLAN`; `plan +extra-post` adds a post on top. The managed-publishing skill and task guide say the same and ask to agree the publish time before admitting accounts.

## 2.0.1

Fixes from a production sweep of 2.0.0.
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.0.1/museoncli-2.0.1-py3-none-any.whl"
uv tool install "https://github.com/Museon-AI/museon-cli/releases/download/v2.1.0/museoncli-2.1.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.0.1/museoncli-2.0.1-py3-none-any.whl"
uv tool install "https://github.com/Museon-AI/museon-cli/releases/download/v2.1.0/museoncli-2.1.0-py3-none-any.whl"
```

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

Large diffs are not rendered by default.

5 changes: 3 additions & 2 deletions contracts/task-index.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -749,7 +749,7 @@ chapters:
before: MuseOn publishes on its own after the rollout; do not run a local loop. Plans keep reviewed {format, topic} pairs, never a cross product.
steps:
- agentic-campaign.list
- agentic-campaign.campaign-create: "Confirm name, budget and persona count with the user first."
- agentic-campaign.campaign-create: "Confirm name, budget, persona count and publish time (--preferred-publish-windows-json read in --publish-timezone, an IANA zone) with the user first."
- agentic-campaign.campaign-review-only: "Manual review for the whole Campaign; tell the user it affects every Plan."
- agentic-campaign.plan-create: "Only in setup; --persona-id."
- agentic-campaign.plan-supply-update: "The complete paired supply with the latest Plan version; opens a proposal, does not publish."
Expand All @@ -771,8 +771,9 @@ chapters:
- agentic-campaign.plan-get
- agentic-campaign.plan-tags
- agentic-campaign.plan-attribution
- agentic-campaign.campaign-update: "Budget and config are setup-only; change the name by itself."
- 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.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
- agentic-campaign.campaign-archive: "Stops every member account of every Plan."
Expand Down
11 changes: 6 additions & 5 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) -->

493 commands across 17 domains (source of truth: `museoncli schema`).
494 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. |
| `ai-slideshow publish +submit-schedule-plan` | destructive | yes | `--yes` | async_run | 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`. |
| `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 +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. |
| `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 +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 @@ -396,6 +396,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 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 All @@ -406,7 +407,7 @@ after changing specs; `tests/test_docs_sync.py` fails CI on drift.
| `agentic-campaign proposal +list` | read | — | — | direct | List Proposals for exactly one Plan or all Plans in one Campaign. Campaign scope returns each Proposal's Plan and Persona summary. |
| `agentic-campaign proposal +get` | read | — | — | direct | Read an adjustment proposal, its latest revision guidance, and the full round-by-round annotation history (annotations). |
| `agentic-campaign +campaign-create` | write | yes | — | direct | Create an Agentic Creative Campaign in the selected organization. Confirm the intent (name, total budget, planned persona count) with the operator before creating, and report the campaign link back afterward. |
| `agentic-campaign +campaign-update` | write | yes | `--yes` | direct | Patch only supplied campaign fields. Budget and config fields are setup-only; name must be changed by itself. Field-level hashtag, mention, and publish-window options merge into existing config, while --config-json replaces the full config. |
| `agentic-campaign +campaign-update` | write | yes | `--yes` | direct | Patch only supplied campaign fields; name must be changed by itself. Field-level hashtag, mention, publish-window and publish-timezone options merge into existing config, while --config-json replaces the full config. The publish time is --preferred-publish-windows-json read in --publish-timezone (IANA, default Asia/Shanghai) for every member account; both can change while the campaign is active, and future not-yet-generated slots move to the new time. |
| `agentic-campaign +plan-update` | write | yes | — | direct | Update plan tokens for the next generation while a campaign is active or paused, or update name/budget only during setup. |
| `agentic-campaign +plan-create` | write | yes | — | direct | Create a Persona Plan under a campaign. Only allowed while the campaign is in setup (setting_up or setup_ready); the server rejects the request otherwise and the error is passed through unchanged. |
| `agentic-campaign +campaign-activate` | write | yes | — | direct | Activate an Agentic Creative Campaign, resuming member account operations. |
Expand Down
Loading
Loading