@easysociable/cli 0.1.17 → 0.1.19

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@easysociable/cli",
-  "version": "0.1.17",
+  "version": "0.1.19",
   "description": "Agent-first CLI for EasySociable: Content Engine, Template, Slideshow, and MCP",
   "type": "module",
   "license": "MIT",
@@ -8,11 +8,10 @@
   "homepage": "https://easysociable.com",
   "repository": {
     "type": "git",
-    "url": "git+https://github.com/murphywuwu/8MRR-Project.git",
-    "directory": "apps/cli"
+    "url": "git+https://github.com/murphywuwu/easysociable-mcp.git"
   },
   "bugs": {
-    "url": "https://github.com/murphywuwu/8MRR-Project/issues"
+    "url": "https://github.com/murphywuwu/easysociable-mcp/issues"
   },
   "keywords": [
     "easysociable",
@@ -51,27 +50,31 @@
     "LICENSE",
     "README.md"
   ],
+  "scripts": {
+    "typecheck": "tsc --noEmit",
+    "test": "vitest run",
+    "build": "tsup",
+    "prepack": "node scripts/prepack.mjs && pnpm build",
+    "pack:check": "npm pack --dry-run"
+  },
   "publishConfig": {
     "access": "public",
     "registry": "https://registry.npmjs.org/"
   },
   "dependencies": {
-    "commander": "^11.1.0"
+    "@resvg/resvg-wasm": "^2.6.2",
+    "commander": "^11.1.0",
+    "satori": "^0.36.0"
   },
   "devDependencies": {
+    "@easysociable/mcp-server": "workspace:*",
+    "@easysociable/template-gateway-client": "workspace:*",
+    "@easysociable/tsconfig": "workspace:*",
+    "@easysociable/tweet-card": "workspace:*",
+    "@easysociable/vitest-config": "workspace:*",
     "@types/node": "^22.14.0",
     "tsup": "^8.0.2",
     "typescript": "^5.8.3",
-    "vitest": "^1.3.1",
-    "@easysociable/mcp-server": "0.0.0",
-    "@easysociable/tsconfig": "0.0.0",
-    "@easysociable/template-gateway-client": "0.0.0",
-    "@easysociable/vitest-config": "0.0.0"
-  },
-  "scripts": {
-    "typecheck": "tsc --noEmit",
-    "test": "vitest run",
-    "build": "tsup",
-    "pack:check": "npm pack --dry-run"
+    "vitest": "^1.3.1"
   }
-}
+}

package/skills/ONBOARDING.md

@@ -19,14 +19,13 @@ V1 expects an Agent (Grok Bot, Codex, Claude Code, …) to drive setup. The webs
 
    Default skills:
 
-   - `easysociable-slideshow` — turns a draft into slideshow pages you preview and download in the dashboard
-   - `easysociable-template` — creates page templates
+   - `easysociable-slideshow` — turns a topic into carousel pages you edit and download in Studio
 
    Optional Content Engine skill (install via CLI only — not in the public
    content-engine git repo; operations still follow that engine’s `CLAUDE.md`):
 
    ```bash
-   easysociable install --skills content,template,slideshow --yes
+   easysociable install --skills content,slideshow --yes
    ```
 
    Get a Content Engine core (preferred):

package/skills/easysociable-slideshow/SKILL.md

@@ -1,178 +1,280 @@
 ---
 name: easysociable-slideshow
 description: >
-  Create, list, update and review durable multi-page Slideshow Runs for
-  EasySociable from a local Content Pack. Name the argument (arc) first, then
-  pick a Layout Family per page (one layout, adapted to every platform) by
-  role, slotSummary and density — never default Cover→Point→Steps→Recap→CTA.
-  A Formula with a Look already fixes each page's Layout Family. Page 1 must
-  be a cover or hook class family; those must not appear on later pages. Use the
-  unified `easysociable` CLI or MCP, open Studio to preview and edit, then
-  ask the user to click Download for a PNG ZIP. CLI/MCP must not call
-  render/export or create_render_job for final pixels. Runs remain in the
-  owner dashboard until archive or hard delete.
+  Turn a topic into an editable, ready-to-post carousel (Slideshow Run) in
+  EasySociable Studio. Research facts, pick a proven hook and structure
+  (Formula), lay pages out from reference designs (the user's, a Formula's,
+  or the catalog's, shuffled), render-check every page locally, then create the Run and hand the user a Studio link.
+  Ask the user only for what only they know (their Brand, once; their own
+  images/screenshots). Final pixels come only from Studio Download.
 ---
 
 # EasySociable Slideshow Skill
 
-A Slideshow Run is a composition of explicit Layout Families, one per page.
-A Layout Family is one layout whose templates differ only by platform canvas,
-so one Run yields the carousel for every platform (Studio switches variants).
-It is not a reusable Carousel/Deck Template and it is not a public post.
-Page order is the argument of **this pack**, not a catalog recipe.
+The user gives a topic. You return a Studio link to a carousel that is good
+enough to post, where every word is still editable. The output is editable,
+so **a wrong guess is cheap and a question is expensive**: decide platform,
+page count, arc, style and copy yourself; the user fixes details in Studio.
 
-## Rules
+Ask only for what only the user knows:
 
-1. Read a local `content-pack.v1` from the Content Engine.
-2. Use the unified `easysociable` CLI or the unified MCP server. All hosted
-   calls go through Gateway; never call Directus, R2, Stripe or private services.
-3. Choose a Brand (or Profile/Theme) and an explicit Layout Family for every
-   page, sent as `layoutFamilyId` in the pack (Gateway resolves it to the
-   family's template on the Run's native canvas; `pageTemplateId` is still
-   accepted). The server never silently chooses or replaces a layout.
-   Order of precedence: (a) a Formula **Look** (see Formula handoff),
-   (b) families already chosen on the Content Engine pack (**Template
-   Selection** after **Page Contracts**), (c) a shortlist from
-   `easysociable slideshows recommend --file contracts.json --seed <slug>`
-   (MCP `recommend_slideshow_templates`) — pick one `familyId` per page with a reason.
-   The recommender filters platform + native canvas + slotSummary + cover rule,
-   demotes Layout Families used in the owner's recent Runs, and keeps one
-   unused family per page. `role` / `supportedRoles` are weak retrieval tags,
-   not sequence position. Never browse with bare `templates list` (first 20
-   ids only); use `--platform <p> --all` if you must see the full catalog.
-   Do not copy a previous pack's Template Selection as the default.
-4. **Cover / hook placement (hard):** a template is cover/hook class when
-   `supportedRoles` includes `cover` or `hook`. `pages[0]` must use one.
-   Cover/hook class templates must not appear on any later page. Later pages
-   use metric / quote / compare / value / steps / cta / etc. Do not put a
-   Point or metric-only template on page 1 to “open with a number” — pick a
-   cover or hook template whose slots fit the opening copy.
-5. A Run has up to 8 pages on Free and 20 on paid, one native platform
-   (`tiktok`, `instagram`, `linkedin` or `threads`; it sets the page cap and
-   the canvas edited first) and one Brand across pages. Studio renders the
-   same Run for every platform its Layout Families support.
-6. Topology is fixed after creation: no add, copy, delete, reorder or template
-   switch. Page-instance slot/layout/type/style/decoration edits remain allowed
-   in Studio.
-7. Final pixels leave the product only from **Studio Download** (browser PNG
-   ZIP). Do not call `slideshows render`, `slideshows export`, `renders create`
-   or MCP `render_slideshow_run` / `create_render_job`. Those return
-   `HEADLESS_RENDER_DISABLED`.
-8. Before creating a new Run, list/find prior Runs by `contentSlug`. **Update**
-   the same Run only when page count, Layout Families, and intended sequence
-   still match. A different arc or family set is a **new Run** — never PATCH
-   new copy into a locked Cover-Point-Steps-Recap-CTA skeleton.
-8b. **Knowledge hard gate (every create, not only the first Run):** before
-    `create_run` / `slideshows create`, read Identity (Role / What I build /
-    Point of view — no `(fill)`, non-empty) and `boundaries.md` (Not covering
-    and Never claim non-empty), or run
-    `easysociable engine validate --run <run-dir> --require-knowledge`.
-    If `needs/` exists, `needs/_index.md` ≥ 3 `N-` rows; if `needs/` is absent, skip that count. Fail → hand back to
-    **easysociable-content** / refuse create; list missing files. Do not add
-    Gateway or MCP params. User must say **强制继续** / **force continue**
-    to call Gateway. **Exempt:** Formula handoff Runs (prompt names
-    `Formula: F-…`) — the Formula supplies the arc and the user supplies the
-    topic, so a first-time user with no Content Engine is not blocked.
-8c. **Identity chain (ADR-0036, hard):** before create, the CLI must be
-    logged in with the **user's Dashboard Workspace API key** (same account
-    that will open Studio). Refuse fixture `workspace_local` / local
-    `test-key` unless the user explicitly asked for a local fixture
-    (`--allow-local-fixture`). Order: `easysociable auth login` (opens the
-    browser; the user approves once and the key is stored — use
-    `--api-key <key>` only when headless) → create Run → open
-    `studioUrl` while logged in as that user. If Studio shows “belongs to
-    another account”, recreate with the current key — do not invent
-    cross-workspace access.
-9. Preview is free. Free Download is 3 successful ZIPs per month and one
-   platform. Paid Download is unmetered.
-10. **Forbidden default:** do not assemble Cover → Point → Steps → Recap → CTA
-    because those are P0 family names. Name the arc first
-    (`references/ARC.md`). Page count follows the argument, not the catalog.
-    Rule 4 still applies: page 1 is cover/hook class, not “whatever family
-    is named Cover”.
+- their Brand (IP name, handle, avatar) — once, ever;
+- their own material (screenshots, photos) when a page needs it.
 
 ## Workflow
 
-1. Write one arc line (`references/ARC.md`). Do not skip this for a five-family fill-in.
-2. Validate Page Contracts / pack when present:
-   `python3 scripts/validate-pack.py runs/<slug>/pack.md` (in the Content Engine).
-   Refuse create if contracts are empty or contain `templateId`.
-3. Resolve or create the user's Brand through the unified CLI/MCP.
-4. Use the Formula Look's families, else pack **Template Selection**. Otherwise run
-   `easysociable slideshows recommend --file contracts.json --seed <slug> --json`
-   and choose a `familyId` from each page's `candidates`; never place a cover/hook class
-   family after page 1. Report `gaps` (pages with < 2 role-matching
-   templates) to the user as authoring backlog. Record Layout Family evidence
-   as `hypothesis` unless published comparable results support `tested` /
-   `supported` — a template having been used before is not evidence.
-5. List existing Runs when the Pack has a stable content slug:
+### 0. Login (once per session)
 
-   ```bash
-   easysociable slideshows list --content-slug my-post --json
-   ```
+`easysociable auth status --json`.
 
-6. **Hard gate, then** create (new arc/templates) or update (same topology,
-   slot copy only). Check files or:
+- `authenticated: false` → stop; ask the user to run `easysociable auth login`
+  (one browser approval covers CLI and Studio). Draft nothing while logged out.
+- `authenticated: true` → say once: "This Run will be created as
+  `<account.email>` — open Studio with the same account."
 
-   ```bash
-   easysociable engine validate --run <run-dir> --require-pack --require-knowledge
-   ```
+### 1. Brand (ask once, ever)
+
+`easysociable brands list --json`.
+
+- A Brand exists → use it (the most recently updated if several), silently.
+- None → ask in **one** message, everything skippable:
+  "What name and @handle should appear on your carousels? (Optional: an
+  avatar/logo image path.) Reply 'skip' to post without a signature."
+  Create it with `easysociable brands create --file brand.json`
+  (`{ "name", "handle", "colors", "logoAssetId" }`) using the default palette
+  that matches the deck's style (`references/REFERENCES.md`). An avatar: upload
+  it first (step 5's `images upload`) and pass the returned `asset.id` as
+  `logoAssetId`; `brands get` then returns its `logoUrl`.
+  Skipped → no Brand: header shows the topic, the CTA has no handle, and that
+  palette goes in `theme.json` (without a Brand or theme Studio falls back to
+  its dark default).
+
+### 2. Facts
+
+Research the topic from primary sources (official announcement, docs,
+reputable press). Keep a source URL for every fact. Drop claims you can only
+find in secondary blogs. Never invent numbers, dates, quotes or features.
+
+When the user started from a Content Engine run, facts come from its knowledge
+pages instead (see `easysociable-content`).
+
+### 3. Hook and structure
+
+Both catalogs are hosted cards distilled from real viral posts, with evidence
+pooled across niches (a hook or structure works by its mechanism, not its
+niche). Use a card when it fits; otherwise write your own. Never force one.
+
+- Decide the content's **shape** from your facts: N tips → `tip-list`, a
+  procedure → `steps`, a transformation → `before-after`, errors →
+  `mistake-list`, a single piece of news or a claim → no list recipe.
+- `easysociable hooks recommend --json` → one mold per hook type (list-tease,
+  contrast, number, identity, …), ranked by evidence.
+- **Always** look for a structure first:
+  `easysociable formulas recommend [--recipe <recipe>] --platform <p> --fact-count <n> --json`
+  (`--recipe` when the shape is a list recipe; without it you see every
+  structure and judge fit yourself). Near-equal cards come back shuffled.
+  When the user asked for something different from last time, add
+  `--exclude <formulaId>` for the Formula that Run used.
+- Use a card only if `stop` is false **and** it fits this content (a news
+  explainer is not an "N things" list). Prefer `published`; a `hypothesis`
+  card is thin evidence: use it only when it clearly fits.
+- Hook: fill the mold's `format` with the topic (never copy its example).
+  Formula: its `swipe` is the page order and each `beat.fill` guides the copy.
+- No fitting card → write the hook and arc yourself (`references/ARC.md`):
+  draft 3 hooks of different types, keep the most specific one the carousel
+  fully pays off.
+- Platform: what the user said, else the one their Brand/history uses, else
+  Instagram 4:5. Page count follows the argument (usually 6–9), within
+  `references/PLATFORM_CAPS.md`.
+- One idea per page, ≤ 45 words per page. Page 1 is the hook. Last page asks
+  for one action (comment, save or follow).
+
+### 4. Look and pages
+
+Structure (step 3) and look are chosen separately. The look comes from a
+**reference**; the first rule that applies wins:
+
+1. The user names a Run or says "same as last time / like this one" →
+   "Reuse a Run" below.
+2. The user shares a post (screenshot or link) → study its grid, type scale,
+   background, density and decoration; take the closest catalog references as
+   structure and restyle them to match the post. Never copy its words or images.
+3. A Formula with a Look → the Look's designs (Formula handoff below).
+4. The user asks for a different look ("换个样子", "something else") → first
+   write 3–5 art directions that differ from each other and from this Brand's
+   previous Run (one line each: grid, type treatment, background, density,
+   decoration). Drop any the previous Run used, take the least conventional
+   one, and pick references whose `style` fits it.
+5. Otherwise → the content decides: get candidates for the cover with
+   `easysociable templates references --role hook,cover [--no-image] --json`
+   (results are shuffled) and take the first that fits the content. Its
+   `style` is the deck's style; for each other page ask for that page's roles
+   with `--style <style>`. A number → `metric,proof`; a list item →
+   `point,value,steps`; a comparison → `compare`; a real product →
+   `screenshot`. No match in that style → any style, keeping the cover's chrome.
+
+`--no-image` unless you have (or will leave a placeholder for) a real image.
+Read each chosen design with `easysociable templates source --family <familyId> --json`
+and adapt it as in `references/REFERENCES.md` ("Adapting a reference" and
+"Avoid"). Put the result in the pack as a generated page:
+
+```json
+{ "role": "hook", "slots": { "text_0": "…", "text_1": "…" },
+  "layout": { "studioJson": "<div id=\"Graphic\" data-type=\"post\" …>…</div>",
+              "canvas": { "width": 1080, "height": 1350 } } }
+```
+
+`slots` maps each `data-variable` to its plain text. Generated pages carry no
+`layoutFamilyId` / `pageTemplateId`.
+
+In the final message, add one line: "Want future carousels to look like this?
+Say 'same as this'. Want another look? Say 'different look'."
 
-   Fail → refuse; return to **easysociable-content**. **强制继续** / **force continue**
-   is the only override (conversational — not a CLI flag). Formula handoff
-   Runs skip this knowledge check (rule 8b) but not the identity gate. Then:
+### 5. Images
 
+- Real products, apps, people, data → real screenshots or photos only. Never
+  an AI-generated picture of a real product UI.
+- Concept / mood / background → generate one if this environment has an
+  image-generation tool; otherwise leave the page text-only.
+- Images never contain text: all words stay in editable text layers.
+- **Every page whose content needs a real image you don't have gets a
+  placeholder slot** (as many pages as need one), never a text-only layout. Size it into the composition (usually the
+  lower half of the page) and label it with exactly what belongs there, e.g.
+  "Add: Grok Bot app screenshot". The user selects it in Studio and clicks
+  the upload button to replace it. Markup and SVG in `references/REFERENCES.md`
+  ("Image placeholder").
+- An image you do have: upload it
+  (`easysociable images upload --file body.json` with
+  `{ "file": "data:image/png;base64,…", "filename": "x.png" }`) and use the
+  returned `asset.url` as `src`.
+- List every placeholder in the final message ("page 2: app screenshot").
+
+### 6. Check (hard gate)
+
+```bash
+easysociable brands get --id <brandId> --json > brand.json
+node <skill>/scripts/check-pages.mjs pack.json --out ./check --brand brand.json
+# no Brand: --theme theme.json instead of --brand brand.json
+```
+
+- Exit 1 → fix every ERROR (overflow, off-canvas, text overlap, contrast) and
+  re-run. Do not create the Run with errors.
+- Warnings (small text, too many words, empty band) → fix unless deliberate.
+- Open `check/grid.png` and review it as a designer: one clear focal point per
+  page, nothing cramped, no two adjacent pages alike, reads in 2 seconds.
+  At most two fix rounds.
+- Exit 2 (no Chrome) → continue, and tell the user the visual check was skipped.
+
+### 7. Create and hand off
+
+```bash
+easysociable slideshows create --file pack.json --brand-id <brandId> --json
+# no Brand: --theme theme.json instead of --brand-id
+```
+
+Reply once with: the `studioUrl`, the arc in one line, the sources, and each
+image placeholder to replace (page + what to upload). Tell them to edit in
+Studio and click **Download** for the PNG ZIP.
+
+### 8. Revise (same Run, never a copy)
+
+Feedback on an existing Run ("page 3 looks off", "shorter hook") edits that Run.
+
+1. `easysociable slideshows get --id <runId> --json > revisions/<runId>-r<revision>.json`
+   — the saved Run is the source of truth (it holds the user's Studio edits);
+   never rebuild from your local pack.json. The file is also the backup.
+2. Change only the pages the user named. Start from each page's saved `layout`
+   and `slots`, adapt as in step 4, and run step 6 on the changed pages.
+3. Write `patch.json` and apply it:
+   ```json
+   { "baseRevision": <run.revision>,
+     "pages": [{ "pageIndex": 2, "layout": { "studioJson": "…", "canvas": { "width": 1080, "height": 1350 } }, "slots": { … } }] }
+   ```
    ```bash
-   easysociable slideshows create --file ./pack.json --json
+   easysociable slideshows update --id <runId> --file patch.json --json
    ```
+   `slots` replaces the page's slots, so send the full set for that page.
+   Unlisted pages stay untouched.
+4. `RUN_REVISION_CONFLICT` → the user saved in Studio meanwhile: `get` again,
+   re-apply your change on top, retry once.
+5. "Go back to the previous version" → take those pages' `layout` / `slots`
+   from the newest `revisions/<runId>-r*.json` before the change and send them
+   as a normal patch with the current `baseRevision`. The original generated
+   pages are in the Run's `packSnapshot`.
+
+Same `studioUrl`; tell the user to reload Studio. A new Run only for a
+different topic, or when the user asks for an alternative version to compare.
+
+## Formula handoff (prompt names `Formula: F-…`)
+
+`easysociable formulas get --id <id> --json`. Its `beats` are the pages (same
+order and roles); `title_template` with `{X}` = the topic is the arc. Write copy
+from each `beat.fill` and your facts; never copy the formula's example posts.
+With `Look: L-…` (else the formula's first `looks` entry) the page source is
+`look.slides["<n>"]` or `look.layouts[beat.role]` (a design's `familyId`):
+read it with `templates source --family` and adapt it as in step 4. The Look
+wins over rule 5 of step 4 but not over a Run or post the user named.
+Then continue at step 5.
+
+## Reuse a Run (prompt names a `run_…` for a new topic)
+
+A new topic → a **new** Run; the source Run is never changed. Never ask which
+mode; decide from the words and the content:
+
+- **Template** — "using run_x as the template", "same as last time", "like
+  this one" (last time = the newest Run of this Brand, `slideshows list`).
+  Keep every page's look: only slot content changes.
+- **Style** — "in the style / feel / vibe of run_x", or Template was asked but
+  the new content does not fit its page roles (a "N tips" Run for an "A vs B"
+  topic). Take its colours, type treatment, chrome and spacing; lay pages out
+  fresh in step 4.
+
+Template steps:
+
+1. `easysociable slideshows get --id <runId> --json`. Its pages' `role`,
+   `layout` and `slots` are the source (they include the user's Studio edits).
+2. Write facts and the arc for the new topic (steps 2–3, no Formula search).
+3. Pages by role: one-off roles (hook, cta) copy that page's `layout`
+   verbatim; repeated roles (point, step) reuse the source page of that role
+   **as many times as the new content needs** (4 tips → 4 pages, 6 → 6). Drop
+   roles the new content has none of.
+4. Change only text inside `data-variable` elements and send matching
+   `slots`. Too long → rewrite shorter; never resize boxes or move elements.
+   Every source image becomes a placeholder for the new topic (step 5);
+   Brand avatar/logo stay.
+5. Step 6 check, then create (step 7). In the reply, say in one line what
+   differs from the source ("6 tips, so 6 point pages instead of 4") and that
+   the user can say "back to 4 pages" or "different layout".
+
+## Rules
 
-7. Open the returned `studioUrl` and inspect every page.
-8. Save Studio edits and wait for the saved revision.
-9. After explicit user confirmation, tell them to click **Download** in Studio.
-   Do not render or export from CLI/MCP.
-
-## Formula handoff (prompt names a `Formula: F-…` id)
-
-1. `easysociable formulas get --id <id> --json` (falls back to the hosted
-   catalog). Not found → tell the user; do not guess a structure.
-2. The formula's `beats` are the page order: one page per beat, same roles,
-   same count. Its `title_template` with `{X}` = the user's topic is the arc
-   line, so rule 10 is satisfied by the formula, not by P0 family names.
-3. Write each page's copy from `beat.fill` and the user's topic. Ask at most
-   one question when tip/point pages need facts the topic doesn't supply.
-   Never copy sentences from the formula's viral example posts.
-4. **Look = copy the layout.** If the prompt names `Look: L-…` (else use the
-   formula's first entry in `looks`), set each page's `layoutFamilyId` to
-   `look.slides["<1-based slide number>"]` if present, else
-   `look.layouts[beat.role]`. Do not run `slideshows recommend` for those
-   pages and ignore the "demote recently used families" preference — the
-   user asked for this layout. Only roles missing from the Look fall back to
-   the recommender. Copy layout only: colours and fonts come from the user's
-   Brand. If a Look family has image slots, ask the user for images (or say
-   which slots are empty) instead of delivering blank image slots.
-5. Turn beats into Page Contracts, then continue at Workflow step 3
-   (Brand → families → identity gate → create → Studio). The knowledge gate
-   (rule 8b) does not apply to Formula handoff Runs.
+1. All hosted calls go through the `easysociable` CLI or the unified MCP
+   server (Gateway). Never call Directus, R2, Stripe or private services.
+2. Final pixels leave only via Studio **Download**. Do not call
+   `slideshows render`, `slideshows export`, `renders create`, or MCP
+   `render_slideshow_run` / `create_render_job` (`HEADLESS_RENDER_DISABLED`).
+3. Revisions edit the same Run page by page (step 8): layout, text and images
+   can all change. Page count and order are fixed for now (no add, delete,
+   reorder) — if the user needs that, say so; create a new Run only when they agree.
+4. Every plan: up to 20 pages. Free: 3 Downloads per month and 1 Brand; Creator: unlimited, 3 Brands; Studio: unlimited, 25 Brands. `BRAND_LIMIT_REACHED` → tell the user their plan's limit and the suggested action; never create a Run without the Brand silently.
+5. Identity: create with the user's own login, not `workspace_local` /
+   `test-key` (unless they asked for `--allow-local-fixture`). Studio says
+   "belongs to another account" → recreate with the current login.
+6. Content Engine runs keep their knowledge gate:
+   `easysociable engine validate --run <run-dir> --require-knowledge`.
+   Topic-only requests (no Content Engine) use researched, sourced facts.
 
 ## Failure handling
 
-- If the knowledge hard gate fails, do not create the Run. Hand back to
-  easysociable-content and list missing files unless the user said
-  **强制继续** / **force continue**.
-- If page 1 is not cover/hook class, or a later page uses a cover/hook
-  class template, stop and rebuild the Pack. Do not create the Run.
-- If a page template, slot or image is invalid, return the structured Gateway
-  error to the Agent; do not substitute another template.
-- `LAYOUT_FAMILY_NOT_FOUND`: the family has no template for the Run's
-  platform. Tell the user and pick another platform or family; do not guess.
-- If Download is exhausted (`USAGE_LIMIT_REACHED`) or past due, tell the user
-  to upgrade or update billing.
-- If a Run was deleted, or Gateway returns `RUN_TOPOLOGY_LOCKED` because the
-  pack changed sequence/templates, create a new Run from the Pack.
+- `CONTENT_PACK_INVALID` → fix the pack field it names; do not drop pages silently.
+- `BRAND_NOT_FOUND` → the Brand belongs to another account; list Brands again.
+- `USAGE_LIMIT_REACHED` / past due → tell the user to upgrade or update billing.
+- `RUN_REVISION_CONFLICT` → `slideshows get`, re-apply on the latest revision, retry once.
+- `RUN_TOPOLOGY_LOCKED` → you sent a full `pack` or a `pageTemplateId`; send
+  page `layout` / `slots` instead (step 8).
 
 ## Handoff boundary
 
-The Content Engine owns semantic copy, Pack creation, and the arc.
-The Template Skill owns single-page authoring and publish.
-This Skill composes explicit page instances and opens Studio for review/Download.
-It does not own a product-level story recipe.
+The Content Engine owns knowledge pages and Formula research. Reference
+designs are authored internally (Template skill); this skill only reads them. This skill turns a topic into a Run
+and opens Studio.

package/skills/easysociable-slideshow/references/CONTENT_PACK.md

@@ -1,18 +1,19 @@
 # ContentPack v1
 
-Page `role` is a **weak retrieval tag** (layout-ish), not sequence position.
-`layoutFamilyId` is the explicit Layout Family chosen by the Agent (from a
-Formula Look or the recommender's `familyId`); Gateway resolves it to that
-family's template on the pack platform's canvas, and Studio derives the other
-platforms from the same family. `pageTemplateId` (one exact template) is still
-accepted and wins when both are sent. `slots` are public values only. Do not add a `deck_template_id`,
-`bindingMap`, AST, ContentDocument, or product `arc` / `pageSequence`.
+A page is **generated**: `layout: { studioJson, canvas }` adapted from a
+reference design (see `REFERENCES.md`). Catalog pages (`layoutFamilyId` /
+`pageTemplateId`) are legacy; do not create new Runs with them. `role` is a weak tag from the closed enum, not a
+sequence position. `slots` are public values only. Do not add a
+`deck_template_id`, `bindingMap`, AST, ContentDocument, or product `arc` /
+`pageSequence`.
 
-The Gateway validates each `role` against the closed enum and that slots exist.
-It does not require Cover → Point → Steps → Recap → CTA.
+Generated page:
 
-This skill **does** require page 1 to be cover/hook class (`supportedRoles`
-includes `cover` or `hook`) and forbids that class on later pages.
+```json
+{ "role": "hook", "slots": { "text_0": "Meta's new AI doesn't chat." },
+  "layout": { "studioJson": "<div id=\"Graphic\" data-type=\"post\" …>…</div>",
+              "canvas": { "width": 1080, "height": 1350 } } }
+```
 
 ## Example: cost → mechanism (TikTok)
 
@@ -47,10 +48,6 @@ Opening beat is cost; page 1 is still a hook-class template.
 }
 ```
 
-Pick families by **slotSummary + density** (or take them from a Formula Look),
-not by matching the beat name to a family named Cover / Point / Steps / Recap /
-CTA. Page 1 must still be cover/hook class.
-
 The renderer accepts any supported page count within the platform cap. A newly
 published Layout Family can be selected in a new Run without creating a
 carousel asset.

package/skills/easysociable-slideshow/references/PLATFORM_CAPS.md

@@ -1,4 +1,4 @@
-# Platform page caps (ADR-0026)
+# Platform page caps
 
 The Run validates only the actual `content-pack.v1.pages.length`. There is no
 `designMax`, full-page deck skeleton, or deck catalog to clone.