@easysociable/cli 0.1.2 → 0.1.4

package/skills/easysociable-template/workflows/FILL_AND_RENDER.md

@@ -1,86 +1,7 @@
-# Fill slots and Hosted Render (published template)
+# Fill slots and Hosted Render — RETIRED
 
-Primary **Agent use** of a published single-page template: read the public slot table, fill values, submit a Hosted Render Job, poll for Artifact / Manifest.
+**Retired as a paid delivery path (2026-09-04).** PNG packs come from Slideshow **Studio Download** (browser ZIP). Gateway `POST /v1/renders`, CLI `renders create|export`, and MCP `create_render_job` return `HEADLESS_RENDER_DISABLED`.
 
-This path belongs to **Template Skill** (ADR-0021 / AC-25～26). Do **not** hand off to Content Skill for single-page fill-slots out图.
+Do not invoke fill-slots render for customer output. Author templates with this skill; consume carousels with Slideshow Skill → Studio → Download.
 
-## Preconditions
-
-```bash
-easysociable auth status --json
-```
-
-Prefer Template MCP tools when available; CLI is the fallback.
-
-## Steps
-
-### 1. Get template + public slots
-
-**MCP:** `get_template({ templateId })`  
-**CLI:** `easysociable templates get --id <id> --json`
-
-Response MUST include `slots[]` with `key`, `type`, `required`, optional `maxCharacters` / `overflow` / `aiHint` / `label`.  
-MUST NOT include AST, Binding Map, or RenderPlan.
-
-### 2. Fill slots
-
-| Slot type | Agent action |
-|---|---|
-| `text` / `number` | Generate from user brief; respect `maxCharacters` / required |
-| `image` | Ask user: upload or choose an existing account image. After confirmation, use `import_template_image` / the unified image import flow so the bytes are stored through Gateway → R2 and the metadata is recorded in the existing Directus `Image` collection; put the returned **`imageId`** in the slot. Never pass temporary Unsplash/Pexels/Pinterest URLs, local paths or transient asset IDs as authority. |
-
-Omit optional empty slots (`null` / `''`) rather than inventing filler.
-
-All V1 image uploads use the account image import flow. There is no separate
-transient render-asset command.
-
-### 3. Create Hosted Render Job
-
-**MCP:** `create_render_job({ templateId, slots, outputFormats, idempotencyKey? })`  
-**CLI:**
-
-```bash
-easysociable renders create \
-  --template-id <id> \
-  --slots '{"title":"Hello","caption":"World"}' \
-  --format png \
-  --idempotency-key fill_1 \
-  --json
-```
-
-**Forbidden inputs:** `ContentDocument`, `contentDocumentHash`, client `RenderPlan`, AST, Binding Map.
-
-### 4. Poll Job / Manifest
-
-**MCP:** `get_render_job({ jobId })` → when completed, `get_render_manifest` if needed  
-**CLI:** `easysociable renders wait --id <id> --json`
-
-Success: signed Artifact URL(s) on the public Manifest.  
-Job may also return `previewUrl` + `capture` (signed Studio-parity page). Deliver the **Hosted Artifact**, not a local screenshot of that preview URL.
-
-### 5. Hosted Capture failure
-
-V1 does not expose a second local capture command. If Hosted Capture fails,
-surface the Gateway error and retry only when it is marked retryable; do not
-invent a browser URL, selector or viewport and do not treat an Authoring Studio
-screenshot as a billable final Artifact.
-
-#### Error-code table
-
-| Code / signal | Local capture? | Agent action |
-|---|---|---|
-| Job `completed` + Manifest Artifact | No | Deliver signed Artifact URL(s) |
-| Retryable worker/queue/5xx error | No | Retry Hosted with the same idempotency key |
-| Rate limit | No | Respect retry-after/backoff and retry once if allowed |
-| `VALIDATION_ERROR` / missing required slots | **No** | Fix slots; no fallback expected |
-| Auth / entitlement / tier denied | **No** | Fix credentials/plan; no fallback |
-Failed jobs without a retryable error are surfaced to the user; no freestyle
-browser screenshot is accepted as final output.
-
-## Anti-patterns
-
-- Building or submitting a local RenderPlan / AST / Binding Map
-- Using ContentDocument export as a render prerequisite
-- Treating Studio html-to-image as Hosted delivery or as the default on success
-- Local capture when Hosted succeeded or when `fallback.capture` is absent
-- Calling Content MCP/CLI for this single-page fill-slots flow
+Public `slots[]` on a published template remain a catalog contract. They are not a PNG API.

package/skills/easysociable-template/workflows/MULTI_PLATFORM_FAMILY.md

@@ -0,0 +1,81 @@
+# Multi-platform Layout Family (default create path)
+
+**SoT for creating templates that ship on several platforms at once.**  
+One user-facing **Layout Family**; one **master** canvas page; additional **variant** pages per aspect preset. Studio switches variants with platform chips — it does not resize one AST (ADR-0033).
+
+Single-page ≠ single-platform. Still never create slideshow/carousel packs (`OUT_OF_SCOPE.md`).
+
+## Default when the user asks to create a template
+
+Unless they explicitly want **one platform only**:
+
+1. Lock a **master** platform + recommended canvas (`PLATFORM_SPECS.md`).
+2. Create the master draft (Family is created with it).
+3. **Derive** missing vertical presets for the family.
+4. **Hand-tune** each variant’s absolute layout (do not ship raw derive output for dense pages).
+5. Visual-QA master + each variant, then hand off Studio with chip switching.
+
+### Default vertical bucket (most social covers)
+
+| Role | Preset | Pixels | Platforms on that variant |
+|---|---|---|---|
+| Master (typical) | `3:4` | 1080×1440 | `xiaohongshu` |
+| Variant | `4:5` | 1080×1350 | `instagram` + `threads` (shared tree) |
+| Variant | `9:16` | 1080×1920 | `tiktok` |
+| Variant | `1:1` | 1080×1080 | `linkedin` |
+
+If the user’s primary platform is already `4:5` / `9:16` / `1:1`, that page is master; derive the other presets in the bucket (see Gateway `defaultDerivePolicyForPreset`).
+
+Skip or trim targets only when the user names a subset (“只要 IG 和 LinkedIn”).
+
+## CLI
+
+```bash
+# After create-draft, read familyId from the draft view (or families list)
+easysociable templates families get --id <familyId> --json
+
+# Create missing presets (idempotent; use --presets to limit)
+easysociable templates families derive --id <familyId> --presets 4:5,9:16,1:1 --json
+
+# Hand-tuned layout per variant pageId
+easysociable templates update-draft --id <variantPageId> --file ./variant-4x5.patch.json --json
+```
+
+Gateway equivalents: `GET/POST /v1/template-families/:id`, `POST /v1/template-families/:id/derive`.
+
+If CLI `--json` fails Zod on new family fields (`familyId`, `variants`, …) but HTTP succeeded, re-fetch with `families get` / `list-drafts` or raw Gateway — do not assume create/derive failed.
+
+## Hand-tune rules (required after derive)
+
+`derive` applies pin `v1_vertical` (scale + bottom/center corrections). That is a **starting point**, not shippable layout for dense covers.
+
+For **each** variant page:
+
+1. Keep the **same slots / copy / icons** as master (same `data-variable` keys).
+2. Rebuild absolute geometry for the target `canvas` (`width`/`height` + root Graphic size must match preset pixels).
+3. Distribute vertical rhythm across the full board: even section gaps; **no** packed header + empty foot.
+4. TikTok `9:16`: keep critical UI out of bottom ~120–160px chrome.
+5. JSX styles must be `style={{ ... }}` (double braces). Python f-strings turn `{{` into `{` — validate with Babel/`validate-authoring-source.mjs` before update.
+6. Per-variant `selectionMetadata.platforms` / `canvasPreset` / `canvas` must match that page only (IG+Threads both listed on the `4:5` page).
+7. Theme/preview tokens stay on the **Family** (`preview_tokens` via `theme.create` on draft) — not a TemplateTheme row (`THEME_TOKENS.md`, ADR-0033).
+
+```bash
+node scripts/validate-authoring-source.mjs ./variant-4x5.authoring.json
+easysociable templates update-draft --id <variantPageId> --file ./variant-4x5.patch.json --json
+```
+
+## Visual QA
+
+Run `VISUAL_QA.md` on the **master** and **each derived preset** (screenshot Studio at that draft URL / platform chip). Fail if any variant has clipped content, overlapping bands, or large empty voids with cramped clusters.
+
+## Handoff
+
+After QA, open the **master** Studio URL and tell the user they can switch platforms with the top-bar chips (each chip is a real canvas variant). Save still applies to the active variant; Agent publish remains post-Save (`PUBLISH_FROM_DRAFT.md`). Include every variant `pageId` + preset in the handoff notes.
+
+## Do not
+
+- Author one AST and claim it fits 3:4 + 9:16 + 1:1
+- Leave dense pages on raw derive output
+- Put Instagram and Threads on different presets when both are 4:5
+- Create a second Family for the same template identity
+- Treat multi-platform variants as a slideshow / carousel pack

package/skills/easysociable-template/workflows/OUT_OF_SCOPE.md

@@ -10,6 +10,7 @@ If the user asks for any of the following, **do not** execute them under this sk
 | Pick Theme as slideshow “Look” for a whole Run | **easysociable-slideshow** + Profile Theme |
 | Local Obsidian content authoring | Content Skill |
 | UGC/publication/social posting | Deferred in V1 |
-| Submit `contentDocumentHash` / ContentDocument to Template render | **Forbidden** — use fill-slots (`FILL_AND_RENDER.md`) |
+| Submit `contentDocumentHash` / ContentDocument to Template render | **Forbidden** |
+| `create_render_job` / CLI `renders create` for customer PNG | **Forbidden** — Studio Download on a Slideshow Run |
 
-**In scope:** single-page template authoring/publish **and** fill-slots Hosted Render of one published PageTemplate (`get_template` → slots → `create_render_job`).
+**In scope:** single-page template authoring/publish. Customer PNG packs are Slideshow Studio Download.

package/skills/easysociable-template/workflows/PUBLISH_FROM_DRAFT.md

@@ -34,7 +34,7 @@ easysociable templates publish --id <draftId> --json
 Or two steps:
 
 ```bash
-easysociable templates update --id <draftId> --file ./draft-patch.json --json
+easysociable templates update-draft --id <draftId> --file ./draft-patch.json --json
 easysociable templates publish --id <draftId> --json
 ```
 

package/skills/easysociable-template/workflows/VISUAL_QA.md

@@ -15,6 +15,15 @@ Run after draft creation and before the user handoff. Source inspection alone is
 
 0. If `theme-tokens.json` exists, compare screenshot contrast to its `contrast` report for the active mode. Failed pairs are hard failures or cap `colorContrast` at 5. When `surfacePreview.kind` is `gradient` or `image`, also check text against `contrastAnchor` / scrim — do not assume Theme.canvas alone matches the wash.
 
+0b. **Reference compare (required when `source.kind = image_reference`)** — before numeric scoring:
+   - Open the **reference image** and the **Studio canvas screenshot** side by side
+   - Check against `design-plan.json` → `referenceSpec`: margins, card stack order, radii, gaps, type hierarchy, badge/icon box sizes
+   - Confirm every `referenceImageInventory` entry is an **image-slot frame** on canvas (not CSS fake faces/illustrations). Missing inventory → hard failure
+   - Confirm recognizable glyphs used Icon Catalog (or documented degrade), not hand-drawn substitutes
+   - A draft that is “structurally educational” but clearly a different layout/density than the reference **fails** this pass even if the numeric rubric might scrape by
+   - Record on `visual-qa.json`: `sourceKind: "image_reference"` and `referenceCompare: { performed, geometryMatch, imageSlotsMatchInventory, notes? }`. A `pass` verdict requires all three booleans `true` (`validate-design-v2.mjs` enforces)
+   - If browser/screenshot tools are unavailable, mark reference compare **pending** (`performed: false`) and do not claim Visual QA passed
+
 1. **Craft Pass (philosophy discipline)** — before numeric scoring:
    - Read `design-plan.json` → `philosophy.craftBar` and the selected concept’s `philosophyExpression`
    - If the screenshot contradicts the philosophy (e.g. generic SaaS three-card grid vs “monumental single metric”), treat that as a composition/hierarchy issue and plan a revise toward the stated expression
@@ -32,6 +41,7 @@ Run after draft creation and before the user handoff. Source inspection alone is
 - missing required slot content/image
 - background or decoration obscuring the focal message
 - third-party temp URLs or broken CDN for image surface/slots
+- **reference path:** pictorial regions replaced by CSS/emoji stand-ins; composition clearly diverged from the reference without user acceptance
 3. Score the fixed rubric in `references/DESIGN_V2_1.md`:
 
 - hierarchy 20

package/skills/easysociable-content/INSTALL.md

@@ -1,60 +0,0 @@
-# Install easysociable-content (private copy)
-
-Ship this folder — **not** the whole monorepo.
-
-## What to copy
-
-```text
-easysociable-content/
-├── SKILL.md
-├── INSTALL.md
-├── scripts/
-├── starter/
-├── workbench/
-├── references/
-├── workflows/
-├── platforms/
-└── fixtures/          # optional
-```
-
-Do **not** include API keys, `.env`, or the user's Content Engine.
-
-## Where to install
-
-| Agent host | Path |
-|---|---|
-| Cursor | `~/.cursor/skills/easysociable-content/` |
-| Claude Code | `~/.claude/skills/easysociable-content/` |
-| Codex | host-specific skills directory (see `platforms/codex.md`) |
-
-```bash
-cp -R easysociable-content ~/.cursor/skills/easysociable-content
-```
-
-Restart the Agent session so the skill is picked up.
-
-## Prerequisites
-
-1. **python3** (workbench `build.py` / `serve.py`)
-2. A parent directory for `Content Engine/` (any folder; Obsidian is not required)
-3. For rendering: unified `easysociable` CLI + Template/Slideshow skills (optional until first render)
-
-## First run (Agent)
-
-1. Ask for a parent directory (or an existing `Content Engine/` path). Do not ask language.
-2. Apply and start workbench:
-
-   ```bash
-   node scripts/setup.mjs --root "<parent>" --preview --json
-   node scripts/setup.mjs --root "<parent>" --apply --json
-   ```
-
-3. Follow `workflows/GETTING_STARTED.md`. Daily operations follow engine `CLAUDE.md`.
-
-Existing files are never overwritten. Later skill updates: `--apply` adds **missing** starter files only; skip existing `workbench/template.html`.
-
-## Package script (maintainers)
-
-```bash
-node skills/easysociable-content/scripts/package-skill.mjs --output /tmp/easysociable-content-skill
-```

package/skills/easysociable-content/platforms/claude.md

@@ -1,4 +0,0 @@
-# Claude Desktop
-
-- Install the unified EasySociable Skill bundle. Content is filesystem-first under `Content Engine/`; hosted Template/Slideshow calls use the unified `easysociable` CLI/MCP.
-- Prefer the Skill frontmatter in each `SKILL.md`.

package/skills/easysociable-content/platforms/codex.md

@@ -1,4 +0,0 @@
-# Codex
-
-- Install `skills/easysociable-content` under the host skill directory for local content workflows.
-- Install the unified EasySociable Skill bundle; hosted preview/render uses the unified `easysociable` CLI/MCP.

package/skills/easysociable-content/platforms/hermes.md

@@ -1,4 +0,0 @@
-# Hermes overrides
-
-- Point Hermes skill loader at this directory.
-- Prefer explicit `Content Engine/` paths in multiprocess environments.

package/skills/easysociable-content/platforms/openclaw.md

@@ -1,4 +0,0 @@
-# OpenClaw overrides
-
-- Register the unified `easysociable` CLI/MCP entry.
-- Keep API Keys and session material out of tool logs. Gateway authentication is owned by the unified client.

package/skills/easysociable-content/references/CLI.md

@@ -1,40 +0,0 @@
-# Content Skill filesystem reference
-
-The Content Skill does not own a Content CLI. It writes `Content Engine/` on disk and uses the unified `easysociable` command only for hosted Template/Slideshow handoff.
-
-## Local workflow
-
-Ask for a parent directory (or existing engine path). Do not ask language. Do not require Obsidian.
-
-Do not invent `easysociable-content init/start/doctor`.
-
-## Setup
-
-```bash
-node scripts/setup.mjs --detect --json
-node scripts/setup.mjs --root <parent-or-engine> --preview --json
-node scripts/setup.mjs --root <parent-or-engine> --apply --json
-node scripts/setup.mjs --root <parent-or-engine> --validate --json
-node scripts/workbench.mjs start --engine <Content Engine> --json
-node scripts/workbench.mjs build --engine <Content Engine> --json
-```
-
-`--no-open` skips the browser and the workbench server.
-
-## Hosted handoff
-
-```bash
-easysociable templates list --platforms tiktok --json
-easysociable slideshows create --file ./runs/<slug>/pack-tiktok.json --json
-easysociable slideshows render --id run_xxx --idempotency-key run_xxx-final-1 --json
-easysociable slideshows export --id run_xxx --output ./exports/<slug> --json
-```
-
-Validate before slideshow create:
-
-```bash
-node scripts/validate-run.mjs --run ./runs/<slug> --require-pack --json
-node scripts/validate-pack.mjs --file ./runs/<slug>/pack-tiktok.json --json
-```
-
-Use unified MCP first when the host exposes it. CLI is the fallback.

package/skills/easysociable-content/references/CONTRACT_SYNC.md

@@ -1,42 +0,0 @@
-# Contract sync
-
-Pack validation in this skill mirrors the hosted public contract. When those
-contracts change, update this skill in the same PR.
-
-## Source of truth
-
-| Contract | Repository path |
-|---|---|
-| `content-pack.v1` schema | `packages/template-public-contracts/src/index.ts` → `contentPackSchema` |
-| Platform page caps | `slideshowPlatformCaps` in the same file |
-| Page roles | `pageRoleSchema` in the same file |
-
-## Mirrored in skill
-
-| Skill file | What to sync |
-|---|---|
-| `scripts/contracts.mjs` | caps, roles, forbidden keys, validate logic |
-| `references/PAGE_PACK.md` | Agent-facing summary + examples |
-| `references/PLATFORM_GUIDE.md` | slideshow vs template routing |
-
-## Maintainer checklist
-
-Before merging contract changes:
-
-1. Diff `contentPackSchema` / `slideshowPlatformCaps` / `pageRoleSchema`.
-2. Update `contracts.mjs` and `PAGE_PACK.md`.
-3. Run:
-
-   ```bash
-   node skills/easysociable-content/scripts/validate.test.mjs
-   node skills/easysociable-content/scripts/fixture.test.mjs
-   node skills/easysociable-content/scripts/setup.test.mjs
-   ```
-
-4. If caps or roles changed, refresh `fixtures/golden-run-en/pack-tiktok.json` when needed.
-
-## Optional hard sync (future)
-
-Import `contentPackSchema` from `@easysociable/template-public-contracts` in
-`validate-pack.mjs` once skill scripts run through the monorepo toolchain. Until
-then, `contracts.mjs` is the portable mirror (marked with `ponytail:`).

package/skills/easysociable-content/references/MCP.md

@@ -1,15 +0,0 @@
-# Unified MCP reference
-
-V1 has one MCP server from the unified EasySociable installer. It owns hosted Template, Image, Profile, Theme, Slideshow and Render tools. This Content Skill does not require a Content MCP.
-
-Content work stays on disk under `Content Engine/`. Hosted calls use the same Gateway client as the CLI.
-
-## Handoff sequence
-
-1. After SHIP, write `pack.md` (slideshow) or slot values (single-page).
-2. Slideshow skill writes `content-pack.v1` into the run folder, then `create_slideshow_run`.
-3. Open Studio URL; wait for Save.
-4. After confirmation call `render_slideshow_run`.
-5. Export PNGs into `exports/<run-slug>/`.
-
-The MCP server must never expose private AST, Binding Maps, RenderPlans, R2 credentials, Directus credentials, Stripe credentials or Local Runtime tokens.

package/skills/easysociable-content/references/PAGE_PACK.md

@@ -1,129 +0,0 @@
-# PagePack handoff (`content-pack.v1`)
-
-The Pack is the boundary between semantic content (Content Skill) and visual
-composition (Template / Slideshow Skills). Content writes slots and roles;
-downstream skills choose Page Templates and render.
-
-**Source of truth for caps and roles:** `packages/template-public-contracts`
-(`contentPackSchema`). This file is the Agent-facing summary.
-
-## Schema
-
-```json
-{
-  "schemaVersion": "content-pack.v1",
-  "platform": "tiktok",
-  "title": "Optional title",
-  "pages": [
-    {
-      "role": "hook",
-      "slots": { "text_0": "Hook line", "text_1": "Support" },
-      "pageTemplateId": "tpl_selected_at_handoff"
-    }
-  ]
-}
-```
-
-| Field | Required | Notes |
-|---|---|---|
-| `schemaVersion` | yes | Must be `content-pack.v1` |
-| `platform` | yes | See platform table below |
-| `title` | no | Display title for Studio |
-| `pages` | yes | Ordered array, length within platform caps |
-| `pages[].role` | yes | Closed `pageRoles` enum |
-| `pages[].slots` | yes | Public slot key → string/number/boolean/null |
-| `pages[].pageTemplateId` | yes | Published Page Template selected by Slideshow before `create` |
-
-## Forbidden in Pack
-
-Never include:
-
-- `deck_template_id` / Deck references
-- Template AST, Binding Maps, RenderPlans
-- `ContentDocument` / `contentDocumentHash`
-- Private gateway credentials or image URLs as slot values (use `imageId` after import)
-
-## Platform page caps
-
-| Platform | Min pages | Max pages | V1 Slideshow |
-|---|---:|---:|---|
-| `tiktok` | 4 | 35 | yes |
-| `instagram` | 2 | 20 | yes |
-| `linkedin` | 2 | 300 | yes |
-| `threads` | 2 | 20 | yes |
-| `xiaohongshu` | — | — | not a Content Pack route in V1; use Template single-page |
-
-`x` is not a Pack platform. Use Template fill-slots for single-page X graphics.
-
-## Page roles (closed set)
-
-`cover`, `hook`, `setup`, `context`, `value`, `point`, `checklist`, `proof`,
-`evidence`, `compare`, `screenshot`, `metric`, `quote`, `steps`, `cta`, `follow`, `recap`
-
-Pick roles that match the narrative arc. Slideshow maps each page to a published
-Page Template with compatible `supportedRoles`.
-
-## File naming
-
-During the run, write vault-native pack markdown:
-
-```text
-pack.md
-pack-<platform>.md
-```
-
-`content-pack.v1` JSON is created **at Slideshow/Template handoff**, not during draft:
-
-```text
-pack-<platform>.json
-```
-
-Example: `pack-tiktok.json`. Pure X text has no pack.
-
-## Validation
-
-```bash
-node scripts/validate-pack.mjs --file ./pack-tiktok.json --platform tiktok --json
-```
-
-Before Slideshow `create`, also run:
-
-```bash
-node scripts/validate-pack.mjs --file ./pack-tiktok.json --require-page-template-id --json
-```
-
-## Examples
-
-### English — TikTok (4 pages, content stage)
-
-```json
-{
-  "schemaVersion": "content-pack.v1",
-  "platform": "tiktok",
-  "title": "Morning routine tips",
-  "pages": [
-    { "role": "hook", "pageTemplateId": "tpl_hook_001", "slots": { "text_0": "Stop scrolling — this changed my mornings" } },
-    { "role": "value", "pageTemplateId": "tpl_value_001", "slots": { "text_0": "Wake at the same time", "text_1": "No phone for 20 minutes" } },
-    { "role": "value", "pageTemplateId": "tpl_value_001", "slots": { "text_0": "Move before caffeine", "text_1": "Even 5 minutes counts" } },
-    { "role": "cta", "pageTemplateId": "tpl_cta_001", "slots": { "text_0": "Save this for tomorrow" } }
-  ]
-}
-```
-
-### 中文 — TikTok（4 页，内容阶段）
-
-```json
-{
-  "schemaVersion": "content-pack.v1",
-  "platform": "tiktok",
-  "title": "晨间习惯三条",
-  "pages": [
-    { "role": "hook", "pageTemplateId": "tpl_hook_001", "slots": { "text_0": "别再瞎忙了——我靠这三条稳住早晨" } },
-    { "role": "value", "pageTemplateId": "tpl_value_001", "slots": { "text_0": "固定起床时间", "text_1": "醒来先别碰手机" } },
-    { "role": "value", "pageTemplateId": "tpl_value_001", "slots": { "text_0": "喝咖啡前先动一动", "text_1": "五分钟也算数" } },
-    { "role": "cta", "pageTemplateId": "tpl_cta_001", "slots": { "text_0": "先收藏，明早试" } }
-  ]
-}
-```
-
-JSON field names and `role` values stay English even when slot copy is 中文.

package/skills/easysociable-content/references/PLATFORM_GUIDE.md

@@ -1,36 +0,0 @@
-# Platform guide
-
-Use this matrix before opening a run. **Ask** if the user did not name a platform. Multi-select → **N runs**.
-
-| Platform | Slideshow (V1) | Pack platform key | Page cap (slideshow) | Default path |
-|---|---|---|---:|---|
-| TikTok | yes | `tiktok` | 4–35 | Slideshow |
-| Instagram | yes | `instagram` (`ig`) | 2–20 | Slideshow |
-| LinkedIn | yes | `linkedin` | 2–300 | Slideshow |
-| Threads | yes | `threads` | 2–20 | Slideshow |
-| X | **no** | — (no Pack) | — | Template single-page or text-only |
-| Xiaohongshu | **no** (V1) | — | — | Template single-page |
-
-Craft notes live under `Content Engine/platforms/`. Map: `instagram` → `ig.md`. Read the file before brief/draft/editor.
-
-## Routing
-
-```text
-1 page                          → easysociable-template
-2+ pages + slideshow platform   → easysociable-slideshow
-x                               → easysociable-template only (if images)
-xiaohongshu                     → easysociable-template until slideshow ships
-```
-
-## Canvas hints (for downstream skills)
-
-| Platform | Typical canvas | Notes |
-|---|---|---|
-| tiktok | 9:16 @ 1080×1920 | Photo Mode carousel |
-| instagram / ig | 4:5 or 1:1 @ 1080 | Feed carousel |
-| linkedin | 4:5 or 1:1 | Document-style decks |
-| threads | 4:5 or 1:1 | Conversational copy |
-| x | 16:9 or 1:1 | Single image post |
-| xiaohongshu | 3:4 @ 1080×1440 | See Template `PLATFORM_SPECS` |
-
-Content Skill does not pick Page Templates — only platform, roles and slot copy. Pack JSON is written at Slideshow/Template handoff, not during draft.

package/skills/easysociable-content/references/RUN_LAYOUT.md

@@ -1,73 +0,0 @@
-# Run layout
-
-Copy `runs/_template/` to `runs/<YYYY-MM-DD-short-slug[-platform]>/`.
-
-**One folder = one platform.** Same Topic on another network = another folder sharing `topic_id`.
-
-```text
-Content Engine/runs/<slug>/
-```
-
-## Core files
-
-| File | Purpose |
-|---|---|
-| `idea.md` | Run id, status, **this** platform, selection (`swipe_id` / `atoms` / `claim_id`) |
-| `brief.md` | Angle, constraints, selection why |
-| `packet.md` | Writer context (pillar + voice + audience + craft notes) |
-| `draft.md` | Copy for **this platform only** |
-| `editor.md` | REVISE / APPROVE |
-| `rubric.md` | 6 × 0–2; SHIP ≥ 8 |
-| `pack.md` | Image deck slots after SHIP (slideshow platforms) |
-| `feedback.md` | URL + `win`/`flat`/`loss` after publish |
-| `pack-<platform>.json` | Complete `content-pack.v1` — **only at render handoff** |
-
-## `idea.md` frontmatter
-
-```yaml
----
-run_id: RUN-YYYYMMDD-slug
-status: RUN_OPEN
-created: YYYY-MM-DD
----
-```
-
-Body must include `primary_platform` equal to `platforms` (single value) and the three selection fields. `none` is allowed with why.
-
-### File status vs index status
-
-| `idea.md` | `runs/_index.md` |
-|---|---|
-| `RUN_OPEN` | `open` |
-| `BRIEF_WAIT` | `brief` |
-| `DRAFTED` / `EDIT_WAIT` | `draft` |
-| `SCORED` | `scored` |
-| `READY_TO_POST` | `ready` |
-| `PUBLISHED` | `published` |
-| `HOLD` / `KILLED` / `SUPERSEDED` | `hold` / `killed` / `superseded` |
-
-Do not use index status `partial` for new runs.
-
-## Validation
-
-Semantic run (no Pack JSON yet):
-
-```bash
-node scripts/validate-run.mjs --run <run-dir> --json
-```
-
-Slideshow handoff (Pack JSON required):
-
-```bash
-node scripts/validate-run.mjs --run <run-dir> --require-pack --json
-node scripts/validate-pack.mjs --file <run-dir>/pack-<platform>.json --platform <platform> --json
-```
-
-## Export path
-
-Final PNGs at the **engine root**, not inside the run folder:
-
-```text
-Content Engine/exports/<run-slug>/01.png
-Content Engine/exports/<run-slug>/<platform>/01.png   # optional subfolder
-```

package/skills/easysociable-content/references/TROUBLESHOOTING.md

@@ -1,13 +0,0 @@
-# Troubleshooting
-
-No Content CLI, Local API, SQLite, or Obsidian requirement.
-
-If setup fails, stop before overwriting files. `python3` missing → install Python 3; starter files may already be written.
-
-If port 8765 is in use, reuse `http://127.0.0.1:8765/workbench/` — do not start a second server. Rebuild with `python3 workbench/build.py`.
-
-Never overwrite an existing `workbench/template.html`. `--apply` only adds missing files.
-
-If a run is incomplete, keep existing markdown and report the missing file. `validate-run.mjs` / `validate-pack.mjs` list concrete gaps. Do not auto-migrate an existing engine.
-
-Deferred features: `workflows/OUT_OF_SCOPE.md`.