@growthub/cli 0.14.5 → 0.14.8

package/assets/worker-kits/growthub-zernio-social-v1/docs/growthub-agentic-social-platform-ui-shell.md

@@ -1,134 +0,0 @@
-# Growthub Agentic Social Media Platform — Exported UI Shell
-
-This document is the source of truth for the UI shell that ships inside the exported `growthub-zernio-social-v1` worker kit.
-
-**Read order:** `../runtime-assumptions.md` → `./zernio-api-integration.md` → this file.
-
----
-
-## Truth Boundary
-
-- The user exports this worker kit from the CLI.
-- After export, the user works inside the exported folder, not inside the CLI repo.
-- The UI shell lives at `studio/` inside that exported folder.
-- The rest of the exported worker kit remains the execution contract for setup, templates, agent law, and Zernio API behavior.
-
-This keeps the Vite shell fully isolated inside the exported worker-kit workspace.
-
----
-
-## Exported Workspace Shape
-
-```text
-growthub-agent-worker-kit-zernio-social-v1/
-  QUICKSTART.md
-  kit.json
-  setup/
-  docs/
-  workers/
-  templates/
-  studio/
-    package.json
-    vite.config.js
-    src/
-```
-
-The user-facing UI setup starts in `studio/`. The worker-kit root remains the source of truth for setup scripts, templates, and the Zernio operator contract.
-
----
-
-## Launch Flow
-
-From the exported worker-kit folder:
-
-```bash
-cd studio
-npm install
-```
-
-Create `studio/.env` with:
-
-```bash
-VITE_ZERNIO_API_URL=https://zernio.com/api/v1
-VITE_ZERNIO_API_KEY=<your-zernio-api-key>
-VITE_ZERNIO_PROFILE_ID=<your-profile-id>
-```
-
-Then start the UI shell:
-
-```bash
-cd studio
-npm run dev
-```
-
-Default local URL:
-
-```text
-http://127.0.0.1:5173
-```
-
-The UI shell is validated from the exported folder itself. Do not use the CLI repo copy as the runtime workspace for the end user.
-
----
-
-## What The UI Shell Covers
-
-The exported Growthub UI shell owns these surfaces:
-
-- Dashboard
-- Accounts
-- Compose
-- Scheduled
-- Queues
-- Analytics
-- Templates
-- Comment Rules
-- Sequences
-- Automations
-- Agent / Swarm
-- API Keys
-
-The Zernio worker kit owns the transport, setup scripts, API contract, and agent workflow that sit behind those screens.
-
----
-
-## Comment Automation Scope
-
-The validated comment automation surface in the UI shell is:
-
-- post-bound comment automation
-- keyword-triggered comment detection
-- optional public comment reply
-- optional DM lead magnet message
-- CRUD for comment automations
-- activation / pause control
-- automation logs
-- account-connect prompts for Instagram and Facebook
-
-The canonical API surface for that flow is `POST /api/v1/comment-automations` plus the related read, update, delete, and logs endpoints documented in the exported UI source.
-
----
-
-## Validation Contract
-
-For this UI shell to be considered valid inside the worker kit:
-
-- the exported folder contains `studio/`
-- `studio/package.json` and `studio/vite.config.js` exist
-- the user can run `npm install` and `npm run dev` from the exported `studio/` folder
-- the UI can be configured with `VITE_ZERNIO_API_URL`, `VITE_ZERNIO_API_KEY`, and `VITE_ZERNIO_PROFILE_ID`
-- the UI shell remains isolated to the exported worker-kit workspace
-- no external paired UI kit is required for the Zernio kit's UI truth
-
----
-
-## Non-Goals
-
-This document does not describe:
-
-- a main-app integration inside the CLI repo
-- a custom Agent Harness
-- a new adapter registry entry
-- a provider SDK install path
-
-Those are intentionally out of scope for this exported worker-kit UI shell.

package/assets/worker-kits/growthub-zernio-social-v1/docs/local-adapters.md

@@ -1,123 +0,0 @@
-# Local Adapters — IDE Matrix
-
-This kit is **IDE-agnostic by design**. The agent entrypoint (`workers/zernio-social-operator/CLAUDE.md`) is plain Markdown, the runtime calls Zernio's hosted REST API via Node's built-in `fetch()`, and no module inside the kit depends on any particular IDE's SDK.
-
-That means you can drive the operator from any local coding agent that supports either:
-
-1. A **Working Directory** config field (the canonical growthub-local primitive — see `docs/WORKER_KITS.md` at the repo root for details), or
-2. An **MCP server** config (for IDEs that speak the Model Context Protocol)
-
----
-
-## Why no "new adapter" for this kit
-
-- **Zernio is hosted SaaS.** There is no self-hostable Zernio component, so a local adapter on the Zernio side would just wrap `fetch()`.
-- The `@paperclipai/adapter-*` packages registered in `server/src/adapters/registry.ts` implement the `ServerAdapterModule` interface — they are **agent executors** (Claude / Codex / Cursor / Gemini / OpenCode / Pi / Hermes), not downstream REST API wrappers. Adding Zernio to that registry would be a category error.
-- Zernio itself ships an official **MCP server** (bundled inside the `zernio-python` SDK: `pip install zernio-sdk[mcp]`) and a **Claude Code skill** (`npx clawhub@latest install zernio-api`). Both are complementary, not required.
-
-The result: this kit runs as-is under every local IDE listed below.
-
----
-
-## Adapter Matrix
-
-| IDE / Adapter | Integration path | How to set up |
-|---|---|---|
-| **Claude Code** (CLI) | Working Directory + slash-command conventions | Point `--working-dir` at the exported kit folder; open the session and talk to `zernio-social-operator`. |
-| **Claude Desktop** | MCP server | Add Zernio's MCP server block (see `setup/install-mcp.mjs` for the JSON) to `~/Library/Application Support/Claude/claude_desktop_config.json` (Mac) or `%APPDATA%/Claude/claude_desktop_config.json` (Windows). |
-| **Codex** (OpenAI) | Working Directory | Point Codex at the exported kit folder. The operator law in `CLAUDE.md` works identically under Codex's reading model. |
-| **Cursor** | Working Directory + optional MCP | Open the exported folder as the Cursor workspace. Optionally add Zernio's MCP server to Cursor's MCP config (`~/.cursor/mcp.json`). |
-| **Gemini CLI** | Working Directory | Point Gemini at the exported kit folder. |
-| **OpenCode** | Working Directory | Point OpenCode at the exported kit folder. |
-| **Qwen Code CLI** | Working Directory | Point Qwen at the exported kit folder. |
-| **Open Agents** | Working Directory + durable runs | Wire the kit folder as the agent's workspace; `/zernio` flows map to Open Agents' prompt-session model. |
-| **Any MCP-compatible IDE** | MCP server | Use `setup/install-mcp.mjs` to print the Zernio MCP server config JSON; drop it into your IDE's MCP config file. |
-
----
-
-## The Three Integration Layers (in order of simplicity)
-
-### Layer 1 — Working Directory only (always works, zero extra install)
-
-```
-growthub kit download growthub-zernio-social-v1
-# ⇒ ~/paperclip/kits/exports/growthub-agent-worker-kit-zernio-social-v1/
-
-# Mac / Linux
-open ~/paperclip/kits/exports/growthub-agent-worker-kit-zernio-social-v1
-# Windows PowerShell
-start $HOME\paperclip\kits\exports\growthub-agent-worker-kit-zernio-social-v1
-```
-
-Then:
-
-1. Open your IDE (Claude Code, Codex, Cursor, Gemini, OpenCode, Qwen)
-2. Point the Working Directory at that folder
-3. Tell the operator: *"Plan a 30-day Instagram + LinkedIn campaign for [brand]"*
-
-That's it. The 10-step workflow in `workers/zernio-social-operator/CLAUDE.md` runs regardless of which IDE is reading it.
-
-### Layer 2 — Zernio's official MCP server (opt-in, one-time install)
-
-When your IDE supports MCP (Claude Desktop, Cursor, any MCP-compatible client), plug in Zernio's own MCP server so the agent can call Zernio endpoints directly as tool calls instead of curl.
-
-```bash
-# Python runtime needed
-pip install zernio-sdk[mcp]
-
-# Print the per-IDE MCP config JSON:
-node setup/install-mcp.mjs
-```
-
-The installer prints copy-paste blocks for:
-
-- Claude Desktop (`claude_desktop_config.json`)
-- Claude Code (`~/.claude/mcp.json`)
-- Cursor (`~/.cursor/mcp.json`)
-- Generic `servers.mcp` JSON (other MCP-compatible IDEs)
-
-Then the agent's Zernio API calls can go through MCP tool invocations in addition to — or instead of — raw HTTP fetch. Either path produces the same manifest-submission result.
-
-### Layer 3 — Zernio's Claude Code skill (Claude Code only, optional)
-
-For Claude Code users who want Zernio's API surface taught as a first-class Claude skill:
-
-```bash
-npx clawhub@latest install zernio-api
-```
-
-This installs Zernio's official Claude Code skill (docs + examples) alongside this kit. The skill teaches Claude the API shape; this kit provides the operator law, templates, and output contract. They complement each other.
-
----
-
-## Which layer should you use?
-
-| If you want... | Use |
-|---|---|
-| Simplest possible setup; agent-only mode included | Layer 1 (Working Directory) |
-| Typed tool calls from the agent to Zernio | Layer 1 + Layer 2 (MCP) |
-| First-class Zernio knowledge baked into Claude Code | Layer 1 + Layer 3 (Claude Code skill) |
-| Growthub Agentic Social Media Platform UI shell | See `docs/growthub-agentic-social-platform-ui-shell.md` |
-
-All four paths work from the same kit folder. You can layer them — they are strictly additive.
-
----
-
-## What the kit does NOT do
-
-- Does **not** ship any Zernio SDK (Node, Python, Go, Ruby, Java, PHP, .NET, Rust). The agent uses raw REST via `fetch()` so nothing is installed transitively.
-- Does **not** register a new entry in `server/src/adapters/registry.ts` or `cli/src/adapters/registry.ts`. Those registries implement the `ServerAdapterModule` / `CLIAdapterModule` contracts for agent executors; Zernio is a REST API, not an executor.
-- Does **not** fork the externally-maintained `@paperclipai/adapter-claude-local` / `adapter-codex-local` / `adapter-cursor-local` / `adapter-gemini-local` / `adapter-opencode-local` / `adapter-pi-local` / `hermes-paperclip-adapter` packages. They remain untouched.
-- Does **not** add a new entry to the `Agent Harness` discovery menu. This kit is a Worker Kit, not a harness.
-
-This keeps the diff surface minimal and the kit strictly reusable across every local IDE already supported by growthub-local.
-
----
-
-## See also
-
-- `../QUICKSTART.md` — one-command setup + per-OS notes
-- `../setup/setup.mjs` — cross-platform bootstrap
-- `../setup/install-mcp.mjs` — per-IDE MCP config printer
-- `./zernio-api-integration.md` — Zernio REST contract
-- `./growthub-agentic-social-platform-ui-shell.md` — exported-workspace UI shell guide

package/assets/worker-kits/growthub-zernio-social-v1/docs/platform-coverage.md

@@ -1,112 +0,0 @@
-# Platform Coverage
-
-**Supported Zernio platform IDs, format specs, and character limits.**
-
-**Frozen at kit creation: 2026-04-15. Confirm live with `GET /api/v1/platforms` when Zernio adds new integrations.**
-
----
-
-## Platform Reference Table
-
-| Platform | Zernio ID | Auth (Zernio-managed) | Post Types | Char Limit | Image Spec | Video Spec |
-|---|---|---|---|---|---|---|
-| X/Twitter | `twitter` | Twitter OAuth 2.0 | text, image, video, thread | 280 | 1200×675, ≤5MB | MP4/MOV, ≤2min 20s |
-| Instagram | `instagram` | Meta OAuth | image, video, reel, story, carousel | 2,200 | 1080×1080 or 1080×1350 | 1080×1920 (reels), MP4, ≤90s |
-| Facebook | `facebook` | Meta OAuth | text, image, video, reel, story, carousel | 63,206 | 1200×628, PNG/JPG | MP4, ≤240min |
-| LinkedIn | `linkedin` | LinkedIn OAuth | text, image, video, document/carousel | 3,000 | 1200×627, PNG/JPG | MP4, ≤10 min |
-| TikTok | `tiktok` | TikTok OAuth | video only | 2,200 | — | 1080×1920, MP4/MOV, 15s–10min |
-| YouTube | `youtube` | Google OAuth | video (long-form), shorts | N/A (title + description) | Thumbnail: 1280×720 | MP4, any length; Shorts ≤60s, 1080×1920 |
-| Pinterest | `pinterest` | Pinterest OAuth | image, video, idea pin | 500 | 1000×1500 (2:3) | MP4, 4s–15min |
-| Reddit | `reddit` | Reddit OAuth | text, image, video, link | Subreddit-specific | Varies by subreddit | MP4, ≤15min |
-| Bluesky | `bluesky` | AT Protocol | text, image, video | 300 | Up to 4 images, 1×1 to 3×4 | MP4, ≤60s |
-| Threads | `threads` | Meta OAuth | text, image, video, thread | 500 | 1:1 square; 4:5 portrait | MP4, ≤5min |
-| Google Business | `googlebusiness` | Google OAuth | update, offer, event | 1,500 | 720×720 minimum | MP4, ≤30s |
-| Telegram | `telegram` | Bot API token | text, image, video, document | 4,096 | JPEG, ≤10MB | MP4, ≤50MB |
-| Snapchat | `snapchat` | Snapchat Marketing API | image, video, story | 80 | 1080×1920 | MP4, ≤60s |
-| WhatsApp | `whatsapp` | WhatsApp Business API | text, image, video, document | 1,024 | JPEG/PNG, ≤5MB | MP4, ≤16MB |
-
-**Source for IDs:** Zernio platform id is the canonical slug used inside every `POST /api/v1/posts` body's `platforms[].platform` field and every `/api/v1/connect/<platform>` OAuth entrypoint.
-
----
-
-## Platform Selection Guidance
-
-### Audience Demographics (2026 data — refine per client brand kit)
-
-| Platform | Primary Demographic | Dominant Use Case |
-|---|---|---|
-| X/Twitter | 18–49 (male-skewed) | News, opinion, live commentary |
-| Instagram | 18–34 (55% female) | Visual branding, lifestyle, product showcase |
-| Facebook | 35–65 | Community groups, local business, events |
-| LinkedIn | 25–55 (professional) | B2B, thought leadership, hiring |
-| TikTok | 18–34 | Short-form entertainment, product discovery |
-| YouTube | All ages (18–49 core) | Education, reviews, entertainment |
-| Pinterest | 25–44 (female-skewed 70%) | Discovery, DIY, home, fashion, recipes |
-| Reddit | 18–49 (male-skewed) | Community discussion, niche interests |
-| Bluesky | 25–45 (tech-skewed) | Tech commentary, open-source community |
-| Threads | 18–34 | Text-first companion to Instagram audiences |
-| Google Business | Local search audience | Local business discovery, reviews |
-| Telegram | 18–44 (international) | Channels, bots, direct community |
-| Snapchat | 13–34 | Short-form, ephemeral content |
-| WhatsApp | 18+ (international, business) | Direct conversations, business messaging |
-
-### Recommended posting cadence per platform
-
-| Platform | Min / Max per week | Notes |
-|---|---|---|
-| X/Twitter | 5 / 30 | Highest-cadence platform. Multiple per day is acceptable. |
-| Instagram | 3 / 10 | Feed posts 3–5/week; Stories daily acceptable. |
-| Facebook | 3 / 10 | Mirror Instagram for B2C. |
-| LinkedIn | 3 / 5 | Never post more than 1x/day for a brand. |
-| TikTok | 3 / 21 | Daily posting drives algorithm signal. |
-| YouTube | 1 / 3 | Long-form is weekly; Shorts can be daily. |
-| Pinterest | 3 / 15 | Batch-pin from hero assets. |
-| Reddit | 1 / 5 | Subreddit etiquette outranks brand cadence. |
-| Bluesky | 3 / 14 | Text-forward; 1–2x/day is common. |
-| Threads | 3 / 14 | Pair with Instagram rhythm. |
-| Google Business | 1 / 3 | Updates + offers + events; don't over-post. |
-| Telegram | 1 / 7 | Channels tolerate quality over quantity. |
-| Snapchat | 3 / 14 | Short daily pulses work well. |
-| WhatsApp | 0 / 2 broadcast | Direct conversation first; broadcast sparingly. |
-
-### Carousel support
-
-Carousel posts are supported on: `instagram`, `linkedin`, `pinterest`, `facebook`.
-They are **not** supported on: `tiktok`, `twitter`, `bluesky`, `threads`, `youtube`, `googlebusiness`, `telegram`, `snapchat`, `whatsapp`, `reddit`.
-
-### Thread support
-
-Native thread posts are supported on: `twitter`, `bluesky`, `threads`. Everywhere else, use carousel or long-form caption.
-
-### Messaging-only platforms
-
-`telegram` and `whatsapp` require follower opt-in through the Zernio-connected account. Do not plan broadcast-style campaigns on these platforms without confirming consent flows with the client.
-
----
-
-## Per-platform Tone Snapshot
-
-| Platform | Tone | Opening-hook rule |
-|---|---|---|
-| `twitter` | Concise, punchy, declarative | First 80 chars decide re-share |
-| `instagram` | Visual-first; caption secondary | First 150 chars above the "more" fold |
-| `facebook` | Conversational, community-oriented | First sentence is the hook |
-| `linkedin` | Professional, credibility-first | Lead with outcome or lesson, not greeting |
-| `tiktok` | Casual, trend-aware | First 150 chars drive completion rate |
-| `youtube` | Benefit + specificity in title; hook in first 8 seconds of video | Title carries the weight |
-| `pinterest` | Descriptive, keyword-dense | Pin title is the hook |
-| `reddit` | Subreddit-native — no marketing voice | First line must read like a genuine user post |
-| `bluesky` | Honest, tech-fluent, link-sparse | Skip hashtags; context carries it |
-| `threads` | Casual, text-forward | Treat as "tweets for Instagram audiences" |
-| `googlebusiness` | Operational, benefit-first, local | Include location or offer specifics |
-| `telegram` | Long-form friendly, channel voice | First two lines in notification preview |
-| `snapchat` | Playful, immediate | Hook must work without audio |
-| `whatsapp` | Direct, 1:1 voice | Treat as personal message, not broadcast |
-
----
-
-## Cross-reference
-
-For caption character limits and variant rules see `docs/ai-caption-layer.md`.
-For scheduling + queue format see `docs/posts-and-queues-layer.md`.
-For API auth, endpoints, rate limits, and error codes see `docs/zernio-api-integration.md`.

package/assets/worker-kits/growthub-zernio-social-v1/docs/posts-and-queues-layer.md

@@ -1,208 +0,0 @@
-# Posts + Queues Layer
-
-This document specifies the JSON shapes the operator must produce. Every shape is a valid request body for the corresponding Zernio REST endpoint, so manifests can be piped directly into `curl` or the Zernio SDKs with no re-shaping.
-
----
-
-## Scheduling Manifest
-
-The scheduling manifest is the machine-readable record the operator writes to `output/<client-slug>/<project-slug>/scheduling-manifest.json` whenever scheduling is requested.
-
-### Top-level shape
-
-```json
-{
-  "zernioSchedulingManifest": {
-    "version": "1.0",
-    "profileId": "<ZERNIO_PROFILE_ID>",
-    "timezone": "America/New_York",
-    "dryRun": false,
-    "generatedAt": "2026-04-15T14:30:00-04:00",
-    "notes": "<free-form operator notes — kept with the manifest>",
-    "posts": [ /* post entries */ ]
-  }
-}
-```
-
-| Field | Required | Type | Notes |
-|---|---|---|---|
-| `version` | Yes | string | Manifest schema version. Current: `"1.0"`. |
-| `profileId` | Yes | string | Must be a real Zernio profile id in api-live mode. In agent-only mode may be `"placeholder"` provided `dryRun: true`. |
-| `timezone` | Yes | string | IANA name. Default: value of `ZERNIO_TIMEZONE` or the profile's default. |
-| `dryRun` | Yes | boolean | `true` in agent-only mode. `false` in api-live and hybrid modes. |
-| `generatedAt` | Yes | string | ISO 8601 with tz offset. |
-| `notes` | No | string | Free-form notes — kept with the manifest for audit. |
-| `posts` | Yes | array | 1..N entries. |
-
-### Per-post entry shape
-
-Each entry is a direct body for `POST /api/v1/posts`, with two additional fields the operator uses for bookkeeping (`clientPostId`, `status`).
-
-```json
-{
-  "clientPostId": "urban-cycle-20260501-001",
-  "content": "Launch day — shipping our spring gravel lineup. Ride it today →",
-  "scheduledFor": "2026-05-01T09:00:00-04:00",
-  "timezone": "America/New_York",
-  "media": [{ "mediaId": "med_HERO_01" }],
-  "platforms": [
-    { "platform": "instagram", "accountId": "acc_ig_UrbanCycle" },
-    { "platform": "twitter",   "accountId": "acc_x_UrbanCycle" }
-  ],
-  "status": "pending"
-}
-```
-
-| Field | Required | Type | Notes |
-|---|---|---|---|
-| `clientPostId` | Yes | string | Operator-generated id. Format: `<client-slug>-<YYYYMMDD>-<sequence>`. Used as the `Idempotency-Key` when submitting to Zernio. Not sent in the body. |
-| `content` | Yes | string | The selected caption variant. |
-| `scheduledFor` | Conditional | string | ISO 8601 with tz offset. Required unless the post is attached to a queue via `queueId`. |
-| `timezone` | Yes | string | IANA name. |
-| `media` | No | array | Array of `{ "mediaId": "<id>" }`. In api-live mode must reference real Zernio `mediaId` values obtained from `POST /api/v1/media`. |
-| `platforms` | Yes | array | 1..N `{ platform, accountId }`. Every `platform` must exist in `docs/platform-coverage.md`. |
-| `queueId` | Conditional | string | Only when the post is attached to a queue. Mutually exclusive with `scheduledFor`. |
-| `status` | Yes | string | Operator bookkeeping. Always starts at `"pending"` and transitions to `"scheduled"` / `"published"` / `"failed"` once Zernio confirms. |
-
-### Submitting a manifest
-
-Each entry becomes one Zernio POST:
-
-```bash
-curl -sS -X POST \
-  "${ZERNIO_API_URL:-https://zernio.com/api/v1}/posts" \
-  -H "Authorization: Bearer ${ZERNIO_API_KEY}" \
-  -H "Content-Type: application/json" \
-  -H "Idempotency-Key: <clientPostId>" \
-  --data-binary @- <<'JSON'
-{
-  "profileId": "prof_abc123",
-  "content": "...",
-  "scheduledFor": "2026-05-01T09:00:00-04:00",
-  "timezone": "America/New_York",
-  "media": [{ "mediaId": "med_HERO_01" }],
-  "platforms": [{ "platform": "twitter", "accountId": "acc_x_111" }]
-}
-JSON
-```
-
-The operator is responsible for issuing one request per `posts[]` entry and for retrying on 429/5xx with the same `Idempotency-Key`.
-
----
-
-## Recurring Queue Definition
-
-Queues define a repeating schedule on a profile. Posts attached to a queue auto-schedule into the next available slot.
-
-### Queue shape
-
-Body of `POST /api/v1/queues` and `PUT /api/v1/queues/<queueId>`:
-
-```json
-{
-  "profileId": "prof_abc123",
-  "name": "weekly-evergreen",
-  "timezone": "America/New_York",
-  "slots": [
-    { "day": "mon", "time": "09:00", "platforms": ["twitter", "linkedin"] },
-    { "day": "wed", "time": "12:30", "platforms": ["instagram"] },
-    { "day": "fri", "time": "17:00", "platforms": ["bluesky", "threads"] }
-  ]
-}
-```
-
-| Field | Required | Type | Notes |
-|---|---|---|---|
-| `profileId` | Yes | string | Zernio profile owning the queue. |
-| `name` | Yes | string | Lowercase kebab-case recommended. |
-| `timezone` | Yes | string | IANA name. |
-| `slots` | Yes | array | 1..N slots. |
-| `slots[].day` | Yes | string | One of `mon|tue|wed|thu|fri|sat|sun`. |
-| `slots[].time` | Yes | string | `HH:MM` 24-hour. |
-| `slots[].platforms` | Yes | array | Platforms enabled for this slot. |
-
-### Post attached to a queue
-
-```json
-{
-  "profileId": "prof_abc123",
-  "queueId": "que_xyz789",
-  "content": "Weekend builder log: three wins, one lesson.",
-  "platforms": [{ "platform": "twitter", "accountId": "acc_x_111" }]
-}
-```
-
-The request is still `POST /api/v1/posts` but with `queueId` instead of `scheduledFor`. Zernio returns the computed `scheduledFor` in the response.
-
-### Queue deliverable in the kit
-
-The operator writes a queue definition alongside the scheduling manifest as:
-
-```
-output/<client-slug>/<project-slug>/queue-<queue-name>.json
-```
-
-The file contains one JSON object — the `zernioQueue` wrapper below — so that it reads as documentation plus a ready-to-submit request body.
-
-```json
-{
-  "zernioQueue": {
-    "version": "1.0",
-    "profileId": "<ZERNIO_PROFILE_ID>",
-    "dryRun": false,
-    "queue": {
-      "profileId": "<ZERNIO_PROFILE_ID>",
-      "name": "weekly-evergreen",
-      "timezone": "America/New_York",
-      "slots": [
-        { "day": "mon", "time": "09:00", "platforms": ["twitter", "linkedin"] }
-      ]
-    }
-  }
-}
-```
-
----
-
-## Media Upload
-
-Every image or video referenced by a post must be uploaded first.
-
-```bash
-curl -sS -X POST \
-  "${ZERNIO_API_URL:-https://zernio.com/api/v1}/media" \
-  -H "Authorization: Bearer ${ZERNIO_API_KEY}" \
-  -H "Idempotency-Key: media-urban-cycle-20260501-hero-01" \
-  -F "file=@./media/urban-cycle/hero-01.png" \
-  -F "profileId=prof_abc123"
-```
-
-The response includes `mediaId`. That id is what the scheduling manifest references.
-
-In `agent-only` mode the operator emits placeholder `mediaId` values prefixed with `placeholder_` and documents the required asset in the Caption Copy Deck's "Media Notes" column. The user uploads the real media and replaces placeholders before submitting.
-
----
-
-## Idempotency Contract
-
-| Endpoint | Idempotency key source |
-|---|---|
-| `POST /api/v1/posts` | `clientPostId` from the manifest entry |
-| `POST /api/v1/queues` | `queue.name` prefixed with `queue-` |
-| `POST /api/v1/media` | `media-<client-slug>-<YYYYMMDD>-<asset-slug>` |
-
-The operator must NEVER send different bodies under the same `Idempotency-Key`. If content changes, increment the manifest version and use a new key.
-
----
-
-## Validation Rules (pre-submission)
-
-Before any submission, re-run through `validation-checklist.md`. Specifically:
-
-- Every `posts[].platforms[].platform` exists in `docs/platform-coverage.md`
-- Every `clientPostId` matches the filename conventions in `output-standards.md`
-- `scheduledFor` timestamps all fall inside the campaign window from the Social Campaign Brief
-- `dryRun` matches the declared execution mode
-- No post entry exceeds per-platform character limits from `docs/ai-caption-layer.md`
-
-Failure on any of these is a blocker — fix the manifest before submitting.