From fd674a01f0bdb60a316036ff56723f3a60edfd3a Mon Sep 17 00:00:00 2001 From: JerryChaox Date: Tue, 17 Nov 2026 00:08:51 +0800 Subject: [PATCH] feat(agentic-campaign): +apply-spec applies a declarative Campaign spec (v2.2.0) One YAML/JSON file declares Personas and Topics under the caller's keys, Formats by key -> id, and Plans with pairs, an optional roster and an optional dated calendar. Without --preview-token it previews the diff and returns a token; with the token it applies. Schedule commands, the managed-publishing skill and the task guide point multi-day Campaign calendars to it. Co-Authored-By: Claude --- CHANGELOG.md | 7 + README.md | 2 +- README.zh-CN.md | 2 +- contracts/command-catalog.json | 374 +++++++++++++++++- contracts/task-index.yaml | 1 + docs/agent-discoverability.md | 9 +- docs/domain-command-framework.md | 9 +- docs/guide.md | 11 +- docs/install.md | 12 +- docs/llms.txt | 2 +- museoncli/domains/_ai_slideshow_publish.py | 4 +- .../domains/_ai_slideshow_publish_account.py | 2 +- museoncli/domains/agentic_campaign.py | 192 +++++++++ pyproject.toml | 2 +- .../SKILL.md | 39 +- skills/museon-content-workflow-base/SKILL.md | 2 +- .../references/task-index.md | 4 +- uv.lock | 2 +- 18 files changed, 638 insertions(+), 38 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 012dfc0..96e532f 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -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 --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. diff --git a/README.md b/README.md index c8c9d9c..e5af0ec 100644 --- a/README.md +++ b/README.md @@ -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: diff --git a/README.zh-CN.md b/README.zh-CN.md index 85139f6..bea0918 100644 --- a/README.zh-CN.md +++ b/README.zh-CN.md @@ -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 和浏览器授权: diff --git a/contracts/command-catalog.json b/contracts/command-catalog.json index 0f8d92f..17527e3 100644 --- a/contracts/command-catalog.json +++ b/contracts/command-catalog.json @@ -109,6 +109,34 @@ "supports_dry_run": true, "transport": "agent_cli_api" }, + { + "authorization": { + "authentication_required": true, + "enforcement": "museon_server", + "organization_bound": true, + "required_roles": [ + "organization_member" + ], + "required_scopes": [ + "agent_cli.access" + ], + "resource_policy": "server_evaluated_organization_and_resource_access", + "workspace_bound": true + }, + "capability_key": "agentic-campaign.apply-spec", + "cli": "museoncli agentic-campaign +apply-spec", + "domain": "agentic-campaign", + "execution": "direct", + "name": "agentic-campaign.apply-spec", + "requires_confirmation": false, + "resource": null, + "risk_level": "write", + "shortcut": "+apply-spec", + "stability": "stable", + "summary": "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.", + "supports_dry_run": true, + "transport": "agent_cli_api" + }, { "authorization": { "authentication_required": true, @@ -1819,7 +1847,7 @@ "risk_level": "read", "shortcut": "+preview-schedule-plan", "stability": "stable", - "summary": "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`.", + "summary": "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`.", "supports_dry_run": false, "transport": "agent_cli_api" }, @@ -1852,7 +1880,7 @@ "risk_level": "destructive", "shortcut": "+submit-schedule-plan", "stability": "stable", - "summary": "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.", + "summary": "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.", "supports_dry_run": true, "transport": "agent_cli_api" }, @@ -2281,7 +2309,7 @@ "risk_level": "write", "shortcut": "+create-schedule", "stability": "stable", - "summary": "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`.", + "summary": "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`.", "supports_dry_run": true, "transport": "agent_cli_api" }, @@ -18336,10 +18364,342 @@ "organization" ] }, - "contract_revision": "2.1.0", + "contract_revision": "2.2.0", "package": "museoncli", "schema_version": 3, "schemas": { + "agentic-campaign.apply-spec": { + "authorization": { + "authentication_required": true, + "enforcement": "museon_server", + "organization_bound": true, + "required_roles": [ + "organization_member" + ], + "required_scopes": [ + "agent_cli.access" + ], + "resource_policy": "server_evaluated_organization_and_resource_access", + "workspace_bound": true + }, + "capability_key": "agentic-campaign.apply-spec", + "cli": "museoncli agentic-campaign +apply-spec", + "domain": "agentic-campaign", + "examples": [ + "museoncli agentic-campaign +apply-spec --campaign-id 22222222-2222-4222-8222-222222222222 --file campaign.yaml", + "museoncli agentic-campaign +apply-spec --campaign-id 22222222-2222-4222-8222-222222222222 --file campaign.yaml --preview-token spec-0123456789abcdef" + ], + "execution": "direct", + "input_schema": { + "properties": { + "campaign_id": { + "description": "Agentic Creative Campaign id", + "examples": [ + "33333333-3333-4333-8333-333333333333" + ], + "format": "uuid", + "type": "string" + }, + "dry_run": { + "default": false, + "type": "boolean" + }, + "preview_token": { + "maxLength": 128, + "minLength": 16, + "type": "string" + }, + "spec": { + "additionalProperties": false, + "properties": { + "formats": { + "additionalProperties": { + "format": "uuid", + "type": "string" + }, + "description": "Format key -> existing ready format id (formats come from source posts)", + "type": "object" + }, + "personas": { + "additionalProperties": { + "properties": { + "description": { + "type": "string" + }, + "name": { + "type": "string" + }, + "tags": { + "items": { + "type": "string" + }, + "type": "array" + } + }, + "required": [ + "name", + "description" + ], + "type": "object" + }, + "type": "object" + }, + "plans": { + "additionalProperties": { + "properties": { + "accounts": { + "description": "Exact member roster (ids or @handles); omit to leave members as they are", + "items": { + "type": "string" + }, + "type": "array" + }, + "name": { + "type": "string" + }, + "pairs": { + "items": { + "additionalProperties": false, + "properties": { + "format": { + "maxLength": 120, + "minLength": 1, + "type": "string" + }, + "topic": { + "maxLength": 120, + "minLength": 1, + "type": "string" + } + }, + "required": [ + "format", + "topic" + ], + "type": "object" + }, + "maxItems": 100, + "type": "array" + }, + "persona": { + "maxLength": 120, + "minLength": 1, + "type": "string" + }, + "schedule": { + "properties": { + "cells": { + "items": { + "additionalProperties": false, + "properties": { + "account": { + "description": "Member account id or @handle; omit for every member", + "type": "string" + }, + "date": { + "format": "date", + "type": "string" + }, + "format": { + "maxLength": 120, + "minLength": 1, + "type": "string" + }, + "topic": { + "maxLength": 120, + "minLength": 1, + "type": "string" + } + }, + "required": [ + "date", + "format", + "topic" + ], + "type": "object" + }, + "type": "array" + }, + "rule": { + "properties": { + "days": { + "minimum": 1, + "type": "integer" + }, + "start": { + "format": "date", + "type": "string" + }, + "type": { + "const": "sequence" + } + }, + "required": [ + "type", + "start" + ], + "type": "object" + } + }, + "type": "object" + } + }, + "required": [ + "persona" + ], + "type": "object" + }, + "type": "object" + }, + "publish": { + "properties": { + "timezone": { + "type": "string" + }, + "windows": { + "default": [], + "items": { + "additionalProperties": false, + "properties": { + "end": { + "pattern": "^\\d{2}:\\d{2}$", + "type": "string" + }, + "start": { + "pattern": "^\\d{2}:\\d{2}$", + "type": "string" + } + }, + "required": [ + "start", + "end" + ], + "type": "object" + }, + "type": "array" + } + }, + "type": "object" + }, + "topics": { + "additionalProperties": { + "properties": { + "keywords": { + "items": { + "type": "string" + }, + "type": "array" + }, + "narrative": { + "type": "string" + }, + "tags": { + "items": { + "type": "string" + }, + "type": "array" + }, + "title": { + "type": "string" + } + }, + "required": [ + "title", + "narrative" + ], + "type": "object" + }, + "type": "object" + }, + "version": { + "const": 1 + } + }, + "required": [ + "version" + ], + "type": "object" + } + }, + "required": [ + "campaign_id", + "spec" + ], + "type": "object" + }, + "name": "agentic-campaign.apply-spec", + "output_schema": { + "description": "Per-resource diff (create/update/unchanged), counts, warnings and preview_token.", + "properties": { + "command": { + "type": "string" + }, + "data": { + "type": [ + "object", + "array", + "string", + "number", + "boolean", + "null" + ] + }, + "next_steps": { + "items": { + "type": "string" + }, + "type": "array" + }, + "ok": { + "type": "boolean" + }, + "organization": { + "description": "The organization this command addressed (id, name).", + "type": [ + "object", + "null" + ] + }, + "run": { + "type": [ + "object", + "null" + ] + }, + "warnings": { + "items": { + "type": "string" + }, + "type": "array" + }, + "workspace": { + "deprecated": true, + "description": "Deprecated: the --workspace-id this command was given, if any.", + "type": [ + "object", + "null" + ] + } + }, + "required": [ + "ok", + "command", + "data", + "run", + "warnings", + "next_steps" + ], + "type": "object" + }, + "requires_confirmation": false, + "resource": null, + "risk_level": "write", + "shortcut": "+apply-spec", + "stability": "stable", + "summary": "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.", + "supports_dry_run": true, + "transport": "agent_cli_api" + }, "agentic-campaign.campaign-activate": { "authorization": { "authentication_required": true, @@ -26784,7 +27144,7 @@ "risk_level": "write", "shortcut": "+create-schedule", "stability": "stable", - "summary": "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`.", + "summary": "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`.", "supports_dry_run": true, "transport": "agent_cli_api" }, @@ -28352,7 +28712,7 @@ "risk_level": "read", "shortcut": "+preview-schedule-plan", "stability": "stable", - "summary": "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`.", + "summary": "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`.", "supports_dry_run": false, "transport": "agent_cli_api" }, @@ -28915,7 +29275,7 @@ "risk_level": "destructive", "shortcut": "+submit-schedule-plan", "stability": "stable", - "summary": "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.", + "summary": "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.", "supports_dry_run": true, "transport": "agent_cli_api" }, diff --git a/contracts/task-index.yaml b/contracts/task-index.yaml index 6d34356..d7a32ec 100644 --- a/contracts/task-index.yaml +++ b/contracts/task-index.yaml @@ -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 diff --git a/docs/agent-discoverability.md b/docs/agent-discoverability.md index 920cfe6..81c12d7 100644 --- a/docs/agent-discoverability.md +++ b/docs/agent-discoverability.md @@ -22,7 +22,7 @@ after changing specs; `tests/test_docs_sync.py` fails CI on drift. -494 commands across 17 domains (source of truth: `museoncli schema`). +495 commands across 17 domains (source of truth: `museoncli schema`). ### research @@ -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. | @@ -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). | @@ -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. | diff --git a/docs/domain-command-framework.md b/docs/domain-command-framework.md index b89023e..c788b81 100644 --- a/docs/domain-command-framework.md +++ b/docs/domain-command-framework.md @@ -56,7 +56,7 @@ The tables below are generated — edit code, then run -494 commands across 17 domains (source of truth: `museoncli schema`). +495 commands across 17 domains (source of truth: `museoncli schema`). ### research @@ -343,8 +343,8 @@ The tables below are generated — edit code, then run | `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. | @@ -357,7 +357,7 @@ The tables below are generated — edit code, then run | `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). | @@ -431,6 +431,7 @@ The tables below are generated — edit code, then run | `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. | diff --git a/docs/guide.md b/docs/guide.md index a4c43e7..4f43a5e 100644 --- a/docs/guide.md +++ b/docs/guide.md @@ -1,6 +1,6 @@ -# Museon CLI task guide (2.1.0) +# Museon CLI task guide (2.2.0) Museon CLI runs MuseOn's social-media operations from an Agent: UGC Campaigns (set up, recruit, approve, contract, daily tasks, content review, counting, client reports), content tracking Campaigns, analytics boards, social accounts and publishing, AI image posts, research and the organization. Find the task below, then run its commands in order. Every command prints one JSON envelope; reads change nothing; a write that reaches someone outside the organization or cannot be undone needs --yes, which only the user may give. @@ -700,10 +700,11 @@ MuseOn publishes on its own after the rollout; do not run a local loop. Plans ke 5. `museoncli agentic-campaign +plan-attribution --campaign-id --plan-id ` (read) 6. `museoncli agentic-campaign +campaign-update --campaign-id ` (write, needs --yes): Change the name by itself. Publish window and --publish-timezone may change while active; future not-yet-generated slots move to the new time. 7. `museoncli agentic-campaign +plan-update --campaign-id --plan-id ` (write) -8. `museoncli agentic-campaign plan +extra-post --campaign-id --plan-id --account-id --scheduled-at 2026-10-01T09:00:00+08:00 --idempotency-key ` (write): 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. -9. `museoncli agentic-campaign +campaign-pause --campaign-id ` (write) -10. `museoncli agentic-campaign +campaign-activate --campaign-id ` (write) -11. `museoncli agentic-campaign +campaign-archive --campaign-id ` (destructive, needs --yes): Stops every member account of every Plan. +8. `museoncli agentic-campaign +apply-spec --campaign-id --file ` (write): Create or overwrite personas, topics, plans, members and a dated calendar from one spec file. Preview first, apply with the returned preview token. +9. `museoncli agentic-campaign plan +extra-post --campaign-id --plan-id --account-id --scheduled-at 2026-10-01T09:00:00+08:00 --idempotency-key ` (write): 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. +10. `museoncli agentic-campaign +campaign-pause --campaign-id ` (write) +11. `museoncli agentic-campaign +campaign-activate --campaign-id ` (write) +12. `museoncli agentic-campaign +campaign-archive --campaign-id ` (destructive, needs --yes): Stops every member account of every Plan. ## 6. Research, analyze content and handle media diff --git a/docs/install.md b/docs/install.md index 8bf6278..b81d354 100644 --- a/docs/install.md +++ b/docs/install.md @@ -70,7 +70,7 @@ If the command is unavailable: reviewed 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" ``` Do not clone the repository, install from a mutable branch, or substitute a @@ -103,11 +103,11 @@ or `current` and includes their destination paths. For another Agent that supports Skills, use that Agent's native Skill installer to install the workflow Skill folders and Hook Analysis Skill: -https://github.com/Museon-AI/museon-cli/tree/v2.1.0/skills/museon-content-workflow-base -https://github.com/Museon-AI/museon-cli/tree/v2.1.0/skills/museon-research -https://github.com/Museon-AI/museon-cli/tree/v2.1.0/skills/museon-content-workflow-hireaicreator -https://github.com/Museon-AI/museon-cli/tree/v2.1.0/skills/museon-content-workflow-ai-slideshow -https://github.com/Museon-AI/museon-cli/tree/v2.1.0/skills/museon-content-workflow-campaigns +https://github.com/Museon-AI/museon-cli/tree/v2.2.0/skills/museon-content-workflow-base +https://github.com/Museon-AI/museon-cli/tree/v2.2.0/skills/museon-research +https://github.com/Museon-AI/museon-cli/tree/v2.2.0/skills/museon-content-workflow-hireaicreator +https://github.com/Museon-AI/museon-cli/tree/v2.2.0/skills/museon-content-workflow-ai-slideshow +https://github.com/Museon-AI/museon-cli/tree/v2.2.0/skills/museon-content-workflow-campaigns Do not invent a Skill directory for an unsupported host. If the Agent has no native Skill installation mechanism, finish the CLI authorization steps and diff --git a/docs/llms.txt b/docs/llms.txt index d7c20b1..0f4239a 100644 --- a/docs/llms.txt +++ b/docs/llms.txt @@ -7,7 +7,7 @@ Museon CLI runs MuseOn's social-media operations from an Agent: UGC Campaigns (s ## Start - [Install guide](https://www.museon.ai/cli/install.md): install the CLI and its Agent Skills, sign in, choose an organization. -- [Task guide](https://www.museon.ai/cli/guide.md): every task as ordered commands with their required flags, risk and gotchas (Museon CLI 2.1.0). +- [Task guide](https://www.museon.ai/cli/guide.md): every task as ordered commands with their required flags, risk and gotchas (Museon CLI 2.2.0). - Offline, the CLI answers the same: `museoncli guide`, `museoncli guide `, `museoncli guide --search `, `museoncli schema `. ## Tasks diff --git a/museoncli/domains/_ai_slideshow_publish.py b/museoncli/domains/_ai_slideshow_publish.py index a9db3d4..bb77dfe 100644 --- a/museoncli/domains/_ai_slideshow_publish.py +++ b/museoncli/domains/_ai_slideshow_publish.py @@ -1040,7 +1040,7 @@ def specs() -> list[CommandSpec]: "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`." + "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`." ), risk_level="read", execution="direct", @@ -1071,7 +1071,7 @@ def specs() -> list[CommandSpec]: shortcut="+submit-schedule-plan", legacy_shortcuts=("+schedule-plan-batch",), summary=( - "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`. " + "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 " diff --git a/museoncli/domains/_ai_slideshow_publish_account.py b/museoncli/domains/_ai_slideshow_publish_account.py index 78d64e0..a250ea0 100644 --- a/museoncli/domains/_ai_slideshow_publish_account.py +++ b/museoncli/domains/_ai_slideshow_publish_account.py @@ -1010,7 +1010,7 @@ def _all_specs() -> list[CommandSpec]: domain=Domain.AI_SLIDESHOW, shortcut="+create-schedule", legacy_shortcuts=("+schedule-create",), - summary="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`.", + summary="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`.", risk_level="write", execution="direct", adapter_tool_name="social_account_schedule_create", diff --git a/museoncli/domains/agentic_campaign.py b/museoncli/domains/agentic_campaign.py index a8236a9..9a82996 100644 --- a/museoncli/domains/agentic_campaign.py +++ b/museoncli/domains/agentic_campaign.py @@ -519,6 +519,7 @@ def specs() -> list[CommandSpec]: _supply_spec(), _account_control_spec(), _extra_post_spec(), + _apply_spec_spec(), *_managed_read_specs(), CommandSpec( domain=domain, @@ -1775,6 +1776,196 @@ async def _execute_extra_post(ctx: CommandContext) -> Any: ) +def _add_apply_spec_arguments(parser: argparse.ArgumentParser) -> None: + parser.add_argument("--campaign-id", required=True) + parser.add_argument("--file", required=True, help="Spec file (YAML or JSON)") + parser.add_argument( + "--preview-token", + help="Token from the preview of this same file; omit it to preview without writing", + ) + parser.add_argument("--dry-run", action="store_true") + + +def _load_spec_file(path: str) -> dict[str, Any]: + import yaml + + with open(path, encoding="utf-8") as handle: + loaded = yaml.safe_load(handle) + if not isinstance(loaded, dict): + raise ValueError(f"{path} must hold one spec object") + return loaded + + +def _build_apply_spec_arguments(args: argparse.Namespace) -> dict[str, Any]: + return compact_params( + { + "campaign_id": args.campaign_id, + "spec": _load_spec_file(args.file), + "preview_token": args.preview_token, + "dry_run": args.dry_run, + } + ) + + +async def _execute_apply_spec(ctx: CommandContext) -> Any: + token = ctx.arguments.get("preview_token") + return await ctx.api_data_v2( + ctx.cfg, + "POST", + f"/agentic-creative-campaigns/{ctx.arguments['campaign_id']}:apply-spec", + json_body=compact_params( + { + "spec": ctx.arguments["spec"], + "dry_run": not token, + "preview_token": token, + } + ), + ) + + +def _spec_reference() -> dict[str, Any]: + return {"type": "string", "minLength": 1, "maxLength": 120} + + +def _apply_spec_spec() -> CommandSpec: + pair = { + "type": "object", + "additionalProperties": False, + "properties": {"format": _spec_reference(), "topic": _spec_reference()}, + "required": ["format", "topic"], + } + cell = { + "type": "object", + "additionalProperties": False, + "properties": { + "date": {"type": "string", "format": "date"}, + "account": { + "type": "string", + "description": "Member account id or @handle; omit for every member", + }, + "format": _spec_reference(), + "topic": _spec_reference(), + }, + "required": ["date", "format", "topic"], + } + spec_schema = { + "type": "object", + "additionalProperties": False, + "properties": { + "version": {"const": 1}, + "publish": { + "type": "object", + "properties": { + "timezone": {"type": "string"}, + "windows": _campaign_config_schema()["properties"]["preferred_publish_windows"], + }, + }, + "formats": { + "type": "object", + "description": "Format key -> existing ready format id (formats come from source posts)", + "additionalProperties": {"type": "string", "format": "uuid"}, + }, + "personas": { + "type": "object", + "additionalProperties": { + "type": "object", + "properties": { + "name": {"type": "string"}, + "description": {"type": "string"}, + "tags": {"type": "array", "items": {"type": "string"}}, + }, + "required": ["name", "description"], + }, + }, + "topics": { + "type": "object", + "additionalProperties": { + "type": "object", + "properties": { + "title": {"type": "string"}, + "narrative": {"type": "string"}, + "keywords": {"type": "array", "items": {"type": "string"}}, + "tags": {"type": "array", "items": {"type": "string"}}, + }, + "required": ["title", "narrative"], + }, + }, + "plans": { + "type": "object", + "additionalProperties": { + "type": "object", + "properties": { + "persona": _spec_reference(), + "name": {"type": "string"}, + "accounts": { + "type": "array", + "items": {"type": "string"}, + "description": "Exact member roster (ids or @handles); omit to leave members as they are", + }, + "pairs": {"type": "array", "items": pair, "maxItems": 100}, + "schedule": { + "type": "object", + "properties": { + "rule": { + "type": "object", + "properties": { + "type": {"const": "sequence"}, + "start": {"type": "string", "format": "date"}, + "days": {"type": "integer", "minimum": 1}, + }, + "required": ["type", "start"], + }, + "cells": {"type": "array", "items": cell}, + }, + }, + }, + "required": ["persona"], + }, + }, + }, + "required": ["version"], + } + return CommandSpec( + domain=Domain.AGENTIC_CAMPAIGN, + shortcut="+apply-spec", + summary=( + "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." + ), + risk_level="write", + execution="direct", + adapter_tool_name="agentic_campaign_apply_spec", + input_schema=_schema( + { + "campaign_id": _uuid_property("Agentic Creative Campaign id"), + "spec": spec_schema, + "preview_token": {"type": "string", "minLength": 16, "maxLength": 128}, + "dry_run": {"type": "boolean", "default": False}, + }, + required=["campaign_id", "spec"], + ), + output_schema=_direct_output_schema( + "Per-resource diff (create/update/unchanged), counts, warnings and preview_token." + ), + examples=[ + "museoncli agentic-campaign +apply-spec --campaign-id 22222222-2222-4222-8222-222222222222 --file campaign.yaml", + "museoncli agentic-campaign +apply-spec --campaign-id 22222222-2222-4222-8222-222222222222 --file campaign.yaml --preview-token spec-0123456789abcdef", + ], + add_arguments=_add_apply_spec_arguments, + build_arguments=_build_apply_spec_arguments, + supports_dry_run=True, + ) + + def _extra_post_spec() -> CommandSpec: return CommandSpec( domain=Domain.AGENTIC_CAMPAIGN, @@ -2001,6 +2192,7 @@ async def execute(ctx: CommandContext) -> dict[str, Any]: "agentic-campaign.plan-extra-post": _managed_enveloped( _execute_extra_post, redact_api_errors=True ), + "agentic-campaign.apply-spec": _managed_enveloped(_execute_apply_spec, redact_api_errors=True), "agentic-campaign.plan-supply-update": _managed_enveloped( _execute_supply, redact_api_errors=True ), diff --git a/pyproject.toml b/pyproject.toml index 0bfda98..d3417b4 100644 --- a/pyproject.toml +++ b/pyproject.toml @@ -4,7 +4,7 @@ build-backend = "hatchling.build" [project] name = "museoncli" -version = "2.1.0" +version = "2.2.0" description = "Agent-ready CLI for Museon's social media operating platform" readme = "README.md" license = "Apache-2.0" diff --git a/skills/museon-content-workflow-ai-slideshow/SKILL.md b/skills/museon-content-workflow-ai-slideshow/SKILL.md index 4fd53f6..e21ddf1 100644 --- a/skills/museon-content-workflow-ai-slideshow/SKILL.md +++ b/skills/museon-content-workflow-ai-slideshow/SKILL.md @@ -66,6 +66,42 @@ Do not schedule a local Codex loop or use the manual generation path for this in To make up a missed day or add a post for one member, use `plan +extra-post` with a stable idempotency key; it does not change the daily cadence. + +### Whole Campaign from one file (`agentic-campaign +apply-spec`) + +When the user hands over a plan of personas, topics and a day-by-day schedule +(for example a document listing each account's 14 days), write ONE spec file and +apply it instead of chaining plan, supply, member and schedule commands: + +```yaml +version: 1 +publish: {timezone: Europe/London, windows: [{start: "20:00", end: "20:01"}]} +formats: {R02: } # formats are only referenced +personas: + EN-01: {name: ..., description: ...} # your own keys +topics: + EN-01-D01: {title: ..., narrative: ...} +plans: + EN-01: + persona: EN-01 + accounts: ["@handle"] # optional exact roster + pairs: [{format: R02, topic: EN-01-D01}] + schedule: # optional calendar + rule: {type: sequence, start: 2026-11-17} # one pair per day, in order + cells: # any single day; wins over the rule + - {date: 2026-11-18, format: R02, topic: EN-01-D01} + - {date: 2026-11-19, account: "@handle", format: R02, topic: EN-01-D01} +``` + +1. `museoncli agentic-campaign +apply-spec --campaign-id --file spec.yaml` + previews: it writes nothing and returns the diff and a `preview_token`. +2. Show the diff to the user. On their go-ahead run the same command with + `--preview-token `. A changed campaign after the preview is refused; + preview again. +3. Re-applying the same file is a no-op; editing one day re-commits only that + Plan. Calendar dates are in the Campaign publish timezone. Days without a + cell keep the Plan's rotation. Plans without accounts keep their calendar + until accounts join. Applying generates nothing by itself. Maintenance uses the same Plan and resource IDs. Retire references through a reviewed supply update; do not erase their history. Reconcile the full desired account list to add/remove members. Pause/resume/stop selected accounts through @@ -82,6 +118,7 @@ stop on a handover conflict. Never overwrite the old Plan's persona identity. | Find or maintain inputs | `museoncli ai-slideshow asset +list` | | Generate from explicit assets | `museoncli ai-slideshow generation +create` | | Inspect or change account asset pools | `museoncli ai-slideshow publish +bulk-preview-asset-pools` | +| Create or overwrite a whole Agentic Campaign (personas, topics, plans, calendar) | `museoncli agentic-campaign +apply-spec` | | Preview or apply schedule plans | `museoncli ai-slideshow publish +preview-schedule-plan` | | Inspect account publish configuration | `museoncli ai-slideshow publish +get-config` | | Read or change a product's CTA targets | `museoncli ai-slideshow cta-target +list --product-id ` | @@ -89,7 +126,7 @@ stop on a handover conflict. Never overwrite the old Plan's persona identity. ## DON'T - **DON'T** bind generation to an account or schedule. -- **DON'T** expect a manual publish schedule on an Agentic Creative Campaign account to add a post: `publish +create-schedule` / `+submit-schedule-plan` on such an account makes that row the day's Plan post and replaces the automatic post of the day (even if already generated) unless it is publishing. Use it when the operator prepared that day's post by hand. To add a post on top of the daily one use `agentic-campaign plan +extra-post`; to post a new format/topic add the pair with `plan +supply-update` (other pairs are rejected with `AGENTIC_PLAN_PAIR_NOT_IN_PLAN`). +- **DON'T** expect a manual publish schedule on an Agentic Creative Campaign account to add a post: `publish +create-schedule` / `+submit-schedule-plan` on such an account makes that row the day's Plan post and replaces the automatic post of the day (even if already generated) unless it is publishing. Use it when the operator prepared that day's post by hand; for a multi-day calendar of a Campaign use `agentic-campaign +apply-spec` instead. To add a post on top of the daily one use `agentic-campaign plan +extra-post`; to post a new format/topic add the pair with `plan +supply-update` (other pairs are rejected with `AGENTIC_PLAN_PAIR_NOT_IN_PLAN`). - **DON'T** treat generation creation or a batch job receipt as terminal success. - **DON'T** add evaluator or CTA inputs, or bind generation itself to an account or schedule. - **DON'T** confuse a product's CTA targets (`cta-target`, what its posts point viewers to) with generation inputs. Listing, creating and editing them is staff only; `+retire` takes owner, admin or operator and `--yes` after the user agrees. `+create` has no idempotency key: list before retrying an unknown outcome. diff --git a/skills/museon-content-workflow-base/SKILL.md b/skills/museon-content-workflow-base/SKILL.md index f216399..2679387 100644 --- a/skills/museon-content-workflow-base/SKILL.md +++ b/skills/museon-content-workflow-base/SKILL.md @@ -49,7 +49,7 @@ verify `museoncli version`, then resume the original task: ```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" ``` Read [operating-model.md](references/operating-model.md) for risk, async work, authentication, diff --git a/skills/museon-content-workflow-base/references/task-index.md b/skills/museon-content-workflow-base/references/task-index.md index c944658..37e557e 100644 --- a/skills/museon-content-workflow-base/references/task-index.md +++ b/skills/museon-content-workflow-base/references/task-index.md @@ -1,6 +1,6 @@ -# Task index (Museon CLI 2.1.0) +# Task index (Museon CLI 2.2.0) Museon CLI runs MuseOn's social-media operations from an Agent: UGC Campaigns (set up, recruit, approve, contract, daily tasks, content review, counting, client reports), content tracking Campaigns, analytics boards, social accounts and publishing, AI image posts, research and the organization. Find the task below, then run its commands in order. Every command prints one JSON envelope; reads change nothing; a write that reaches someone outside the organization or cannot be undone needs --yes, which only the user may give. @@ -88,7 +88,7 @@ AI image posts (生图/图文) are built from reusable format, topic and persona - **Change many accounts' pools or schedule plans at once** (`slideshow-bulk`): `museoncli ai-slideshow publish +bulk-get-asset-pools` → `museoncli ai-slideshow publish +bulk-preview-asset-pools` → `museoncli ai-slideshow publish +bulk-set-asset-pools` → `museoncli ai-slideshow publish +get-asset-pool-job` → `museoncli ai-slideshow publish +cancel-asset-pool-job` → `museoncli ai-slideshow publish +preview-schedule-plan` → `museoncli ai-slideshow publish +submit-schedule-plan` → `museoncli ai-slideshow publish +get-schedule-plan-job` → `museoncli ai-slideshow publish +cancel-schedule-plan-job` - **Manage a product's CTA targets** (`slideshow-cta`): `museoncli ai-slideshow cta-target +list` → `museoncli ai-slideshow cta-target +create` → `museoncli ai-slideshow cta-target +update` → `museoncli ai-slideshow cta-target +retire` - **Keep image posts publishing daily (Agentic Creative Campaign)** (`managed-publishing`): `museoncli agentic-campaign +list` → `museoncli agentic-campaign +campaign-create` → `museoncli agentic-campaign +campaign-review-only` → `museoncli agentic-campaign +plan-create` → `museoncli agentic-campaign plan +supply-update` → `museoncli agentic-campaign proposal +list` → `museoncli agentic-campaign proposal +get` → `museoncli agentic-campaign +schedule-rollout-preflight` → `museoncli agentic-campaign +confirm-schedule-rollout` → `museoncli agentic-campaign +schedule-rollout-get` → `museoncli agentic-campaign plan +members-reconcile` → `museoncli agentic-campaign plan +account-control` → `museoncli agentic-campaign plan +posts` → `museoncli agentic-campaign proposal +withdraw` -- **Read and maintain Agentic Creative Campaigns** (`managed-publishing-maintain`): `museoncli agentic-campaign +get` → `museoncli agentic-campaign +plan-list` → `museoncli agentic-campaign +plan-get` → `museoncli agentic-campaign +plan-tags` → `museoncli agentic-campaign +plan-attribution` → `museoncli agentic-campaign +campaign-update` → `museoncli agentic-campaign +plan-update` → `museoncli agentic-campaign plan +extra-post` → `museoncli agentic-campaign +campaign-pause` → `museoncli agentic-campaign +campaign-activate` → `museoncli agentic-campaign +campaign-archive` +- **Read and maintain Agentic Creative Campaigns** (`managed-publishing-maintain`): `museoncli agentic-campaign +get` → `museoncli agentic-campaign +plan-list` → `museoncli agentic-campaign +plan-get` → `museoncli agentic-campaign +plan-tags` → `museoncli agentic-campaign +plan-attribution` → `museoncli agentic-campaign +campaign-update` → `museoncli agentic-campaign +plan-update` → `museoncli agentic-campaign +apply-spec` → `museoncli agentic-campaign plan +extra-post` → `museoncli agentic-campaign +campaign-pause` → `museoncli agentic-campaign +campaign-activate` → `museoncli agentic-campaign +campaign-archive` ## 6. Research, analyze content and handle media diff --git a/uv.lock b/uv.lock index 5790524..c09b484 100644 --- a/uv.lock +++ b/uv.lock @@ -330,7 +330,7 @@ wheels = [ [[package]] name = "museoncli" -version = "2.1.0" +version = "2.2.0" source = { editable = "." } dependencies = [ { name = "anyio" },