adapto-publish

# adapto:publish The **terminal step of the draft-first loop**: every other skill writes `draft` content; this one takes the reviewed drafts **live** (`draft → published`), or **archives** them back (`published → archived`) as a walk-back. It's **stateless** — it *discovers* what's publishable rather than remembering a session. ## When to use - "Publish", "publish my drafts", "take it live", "go live", "unpublish/archive this" — typically after reviewing the seeded/translated drafts on the dev server. ## When not to use - Creating or editing content → the content pipeline (`content-create` → `content-upload`) or `adapto:translate`. - Just checking the environment → `adapto:doctor`. ## Inputs - **Mode:** `publish` (default) or `archive` (the inverse / walk-back). - **Optional filters:** type (Articles / Pages / collection items), language, or a specific collection / item set. - Collections enumerated from `.adapto/schema.json` (if present) or `adapto collections list --json`. ## Outputs - The selected Articles / Pages / collection items moved `draft → published` (or `published → archived`). - The **ledger** updated (acted-on pieces → `published`) and `.adapto/calendar.md` refreshed. - A report of acted-on + skipped, with ids. - **Next step:** the cycle is complete — suggest the next content cycle (`adapto:content-research`) or `adapto:translate` to localize what just went live. ## Preconditions - **Preflight** with the `adapto:doctor` checks. - **Hard-block** on an a...