@growthub/cli 0.14.4 → 0.14.6

package/assets/worker-kits/growthub-zernio-social-v1/growthub-meta/README.md

@@ -1,143 +0,0 @@
-# Growthub Meta — growthub-zernio-social-v1
-
----
-
-## Kit Identity
-
-| Field | Value |
-|---|---|
-| Kit ID | `growthub-zernio-social-v1` |
-| Version | `1.0.0` |
-| Schema Version | `2` |
-| Type | `worker` |
-| Family | `studio` |
-| Factory family (adapter core) | `operator` |
-| Execution Mode | `export` |
-| Activation Modes | `["export"]` |
-| Visibility | `public-open-source` |
-| Source Repo | `growthub-local` |
-| Frozen At | `2026-04-15T00:00:00.000Z` |
-| Kernel packet | [Hosted SaaS Kit Kernel Packet `v1`](../../../../docs/kernel-packets/KERNEL_PACKET_HOSTED_SAAS_KIT.md) — this kit is the canonical reference implementation |
-
----
-
-## What This Kit Does
-
-The Growthub Zernio Social Media Studio is a worker kit that wraps the [Zernio](https://zernio.com) REST API — a unified social media API for developers and AI agents — to produce AI-assisted social media campaigns, content calendars, caption copy decks, Zernio-shaped scheduling manifests, and recurring queue definitions across 14 social platforms.
-
-The kit provides a self-contained local execution environment. An operator exports the kit, points Claude Code's Working Directory at the kit root, and the `zernio-social-operator` worker handles the complete 10-step social media campaign workflow.
-
-Zernio is a hosted SaaS: there is no docker image or local fork to clone. The kit works against the hosted `https://zernio.com/api/v1` endpoint using an API key, and the exported `studio/` workspace is the user-facing UI shell.
-
----
-
-## Folder Structure
-
-```
-growthub-zernio-social-v1/
-  kit.json                              ← Kit manifest (schemaVersion: 2)
-  QUICKSTART.md                         ← Setup guide
-  .env.example                          ← Worker-kit environment template
-  skills.md                             ← Master methodology doc (read at every session)
-  output-standards.md                   ← Output naming, structure, quality bar
-  runtime-assumptions.md                ← Frozen upstream assumptions
-  validation-checklist.md               ← Pre-session + kit validation checklists
-  bundles/
-    growthub-zernio-social-v1.json      ← Bundle manifest
-  workers/
-    zernio-social-operator/
-      CLAUDE.md                         ← Agent operating instructions (entrypoint)
-  brands/
-    _template/
-      brand-kit.md                      ← Blank client brand kit template
-    growthub/
-      brand-kit.md                      ← Growthub internal reference example
-    NEW-CLIENT.md                       ← Instructions for adding new clients
-  setup/
-    setup.mjs                           ← One-command cross-platform bootstrap (Win/Mac/Linux)
-    verify-env.mjs                      ← Verifies API key, profile, reachability
-    check-deps.sh                       ← Legacy Unix bash dep check
-    check-deps.mjs                      ← Cross-platform Node dep check (Windows parity)
-    install-mcp.mjs                     ← Prints per-IDE MCP server config JSON
-  output/
-    README.md                           ← Output directory structure and naming
-  templates/                            ← 7 production-quality campaign templates
-    social-campaign-brief.md
-    content-calendar.md
-    platform-publishing-plan.md
-    caption-copy-deck.md
-    scheduling-manifest.md
-    analytics-brief.md
-    client-proposal.md
-  examples/                             ← 4 filled samples for reference
-    social-campaign-sample.md
-    content-calendar-sample.md
-    analytics-brief-sample.md
-    client-proposal-sample.md
-  docs/                                 ← 6 technical reference documents
-    zernio-api-integration.md
-    platform-coverage.md
-    ai-caption-layer.md
-    posts-and-queues-layer.md
-    growthub-agentic-social-platform-ui-shell.md ← Exported UI-shell workflow and setup truth
-    local-adapters.md                   ← Per-IDE matrix (Claude/Codex/Cursor/Gemini/OpenCode/…)
-  growthub-meta/
-    README.md                           ← This file
-    kit-standard.md                     ← Kit rules and required-files contract
-```
-
----
-
-## Activation
-
-This kit is activated in `export` mode:
-
-1. CLI exports the kit to a local folder
-2. User points Claude Code's Working Directory at the exported folder root
-3. `workers/zernio-social-operator/CLAUDE.md` is the agent entrypoint
-
-No server-side activation is required. The kit is fully self-contained.
-
----
-
-## Upstream API
-
-| Field | Value |
-|---|---|
-| Provider | Zernio |
-| Site | https://zernio.com |
-| Docs | https://docs.zernio.com |
-| API base | `https://zernio.com/api/v1` |
-| Auth | Bearer API key (`sk_` + 64 hex) via `Authorization` header |
-| Env vars used | `ZERNIO_API_KEY`, `ZERNIO_API_URL`, `ZERNIO_PROFILE_ID`, `ZERNIO_TIMEZONE` (optional), `ANTHROPIC_API_KEY` (optional) |
-| Supported platforms | 14 — see `docs/platform-coverage.md` |
-
----
-
-## Supported Output Categories
-
-| Category | Templates | Examples |
-|---|---|---|
-| Social Campaign Briefs | `templates/social-campaign-brief.md` | `examples/social-campaign-sample.md` |
-| Content Calendars | `templates/content-calendar.md` | `examples/content-calendar-sample.md` |
-| Platform Publishing Plans | `templates/platform-publishing-plan.md` | — |
-| Caption Copy Decks | `templates/caption-copy-deck.md` | — |
-| Scheduling Manifests | `templates/scheduling-manifest.md` | — |
-| Analytics Briefs | `templates/analytics-brief.md` | `examples/analytics-brief-sample.md` |
-| Client Proposals | `templates/client-proposal.md` | `examples/client-proposal-sample.md` |
-
----
-
-## Related Kits
-
-| Kit | Family | Purpose |
-|---|---|---|
-| `creative-strategist-v1` | workflow | Campaign strategy and creative briefs |
-| `growthub-email-marketing-v1` | operator | Email marketing campaigns |
-| `growthub-open-higgsfield-studio-v1` | studio | AI video generation via Open Higgsfield |
-| `growthub-geo-seo-v1` | studio | GEO + SEO auditing |
-| `growthub-zernio-social-v1` | studio | Social media via hosted Zernio REST API (this kit) |
-
-### Exported Workspace Truth
-
-The exported worker kit is the only user-facing workspace. Inside that exported folder, `studio/` is the Vite UI shell and the rest of the kit provides the Zernio operator law, templates, setup scripts, and API contract. The CLI is responsible only for exporting this workspace cleanly.

package/assets/worker-kits/growthub-zernio-social-v1/growthub-meta/kit-standard.md

@@ -1,120 +0,0 @@
-# Kit Standard — growthub-zernio-social-v1
-
-**These rules govern the kit's structure, agent behavior, and output contract. All operators and maintainers must follow them.**
-
----
-
-## Required Files Contract
-
-The following files must be present in every valid kit installation. Any missing file constitutes a broken kit.
-
-| File | Purpose | Can Be Empty? |
-|---|---|---|
-| `kit.json` | Kit manifest | No — must be valid JSON with `schemaVersion: 2` |
-| `QUICKSTART.md` | User-facing setup guide | No |
-| `.env.example` | Environment template | No |
-| `skills.md` | Master methodology doc | No — must contain all 10 steps |
-| `output-standards.md` | Output rules | No |
-| `runtime-assumptions.md` | Upstream assumptions | No |
-| `validation-checklist.md` | Pre-session checklist | No |
-| `workers/zernio-social-operator/CLAUDE.md` | Agent entrypoint | No |
-| `brands/_template/brand-kit.md` | Blank brand kit template | No |
-| `brands/growthub/brand-kit.md` | Example brand kit | No |
-| `brands/NEW-CLIENT.md` | New client instructions | No |
-| `setup/verify-env.mjs` | Environment verification | No |
-| `setup/check-deps.sh` | Dependency check | No |
-| `output/README.md` | Output directory guide | No |
-| All 7 template files | Campaign output templates | No — each must have all sections |
-| All 4 example files | Reference samples | No — must contain realistic filled data |
-| All 6 doc files | Technical reference | No |
-| `bundles/growthub-zernio-social-v1.json` | Bundle manifest | No |
-| `growthub-meta/README.md` | Kit metadata | No |
-| `growthub-meta/kit-standard.md` | This file | No |
-
----
-
-## Bundle Contract
-
-| Requirement | Rule |
-|---|---|
-| Bundle ID | Must match kit ID: `growthub-zernio-social-v1` |
-| Kit ID in bundle | Must be `growthub-zernio-social-v1` |
-| Worker ID in bundle | Must be `zernio-social-operator` |
-| Schema version | Must be `2` |
-| `requiredFrozenAssets` | Must list all files in `kit.json` `frozenAssetPaths` |
-| Export folder name | `growthub-agent-worker-kit-zernio-social-v1` |
-| Export zip name | `growthub-agent-worker-kit-zernio-social-v1.zip` |
-
----
-
-## Agent Rules
-
-### Workflow Order
-
-The operator must follow the 10-step workflow in `workers/zernio-social-operator/CLAUDE.md` strictly. Steps must not be skipped or reordered. The environment gate (Step 0) must run before anything else.
-
-### Platform IDs
-
-The operator must only use Zernio platform IDs from `docs/platform-coverage.md`. Invented platform slugs are not acceptable. If the user requests a platform not in the coverage doc, the operator must note it as unsupported in the current Zernio instance and suggest the nearest supported alternative.
-
-### Caption Variants
-
-Every post in the Caption Copy Deck must have exactly 3 variants (A, B, C). The variants must be meaningfully different in opening hook and structure — not minor word substitutions. Character limits must be checked and documented for every variant.
-
-### Scheduling Manifest
-
-When a scheduling manifest is produced:
-
-- `dryRun` must be `true` in agent-only mode
-- All `scheduledFor` values must be ISO 8601 with explicit timezone offset
-- All `clientPostId` values must follow the naming convention
-- Every `platforms[].platform` must exist in `docs/platform-coverage.md`
-- Every `platforms[].accountId` must be a real Zernio account id (live mode) or a clearly-placeholdered handle (agent-only mode)
-- No manifest may reference a platform not confirmed via `GET /api/v1/accounts` in live mode
-
-### Idempotency
-
-Every write request to Zernio must carry an `Idempotency-Key` header. The operator uses `clientPostId` from the manifest as that key. Queues use `queue-<name>`. Media uploads use `media-<client-slug>-<YYYYMMDD>-<asset-slug>`.
-
-### No Secrets in Outputs
-
-The operator must never include `ZERNIO_API_KEY`, `ANTHROPIC_API_KEY`, OAuth tokens, or raw auth headers in any output file. `.env.example` uses placeholder comments only.
-
-### Template-Bound Outputs
-
-All output artifacts must use the templates in `templates/`. The operator must not invent new template schemas or change the required section structure.
-
----
-
-## Runtime Rules
-
-### Three Execution Modes Are First-Class
-
-`api-live`, `agent-only`, and `hybrid` are all valid execution modes. The kit must never require `api-live` mode for a session to produce valid campaign outputs. Agent-only mode is always a valid fallback for campaign planning, caption drafting, and dry-run scheduling manifests.
-
-### Zernio Is the Reference Substrate
-
-The platform integrations, queue model, and API contract at `https://zernio.com/api/v1` are the source of truth for scheduling behavior. The kit documents and wraps that behavior — it does not redefine it. When the Zernio API changes, `docs/zernio-api-integration.md` and `runtime-assumptions.md` must be updated.
-
-### Markdown Is the Primary Output Format
-
-All campaign artifacts are Markdown files. The scheduling manifest is a JSON file. Queue definitions are JSON files. No other formats are produced by this kit unless explicitly requested.
-
----
-
-## Versioning Rules
-
-| Scenario | Action |
-|---|---|
-| Bug fix in a template or doc file | Patch version bump: `1.0.0` → `1.0.1` |
-| New template or platform added | Minor version bump: `1.0.0` → `1.1.0` |
-| Workflow restructured or output schema changed | Major version bump: `1.0.0` → `2.0.0` |
-| Zernio adds a new platform integration | Minor bump + update `runtime-assumptions.md` and `docs/platform-coverage.md` |
-| Zernio changes the REST contract | Major bump if breaking + update `docs/zernio-api-integration.md` and `runtime-assumptions.md` |
-
-Version bumps must update:
-
-- `kit.json` → `kit.version`
-- `bundles/growthub-zernio-social-v1.json` → `bundle.version`
-- `growthub-meta/README.md` → Version field
-- `runtime-assumptions.md` → Frozen date and changelog note

package/assets/worker-kits/growthub-zernio-social-v1/helpers/README.md

@@ -1,29 +0,0 @@
-# `helpers/` — safe shell tool layer (primitive #6)
-
-A **helper** is a small, deterministic script an agent invokes via one shell call instead of reconstructing a raw pipeline inline. Helpers are reviewable, deterministic, and safer than raw commands.
-
-## Convention
-
-```
-helpers/
-├── README.md                 # this file
-├── <verb>.sh                 # single-purpose shell scripts
-├── <verb>.mjs                # optional: Node-based helper
-└── <verb>.py                 # optional: Python-based helper
-```
-
-Every helper:
-
-1. Carries a one-line header comment: what it does + how to invoke it.
-2. Uses `set -euo pipefail` (or equivalent) — no silent failures.
-3. Has a matching row in the parent `SKILL.md`'s `helpers[]` frontmatter.
-4. Is referenced from `skills.md` at the step the agent should invoke it (no duplicated shell bodies).
-
-## When to promote an inline snippet
-
-- Appears more than once in `skills.md`.
-- Has fragile quoting or path interpolation.
-- Calls a side-effecting binary (ffmpeg, git, gh, npm install).
-- Multiple sub-skills invoke it.
-
-See the parent `SKILL.md` `helpers[]` array for the current roster.

package/assets/worker-kits/growthub-zernio-social-v1/kit.json

@@ -1,151 +0,0 @@
-{
-  "schemaVersion": 2,
-  "kit": {
-    "id": "growthub-zernio-social-v1",
-    "version": "1.0.0",
-    "name": "Growthub Agent Worker Kit \u2014 Zernio Social Media Studio",
-    "description": "Self-contained local execution environment for Zernio, the unified social media REST API for developers and AI agents. Produces implementation-ready social media campaigns, content calendars, multi-platform publishing plans, AI-assisted captions, Zernio-shaped scheduling manifests, recurring queue definitions, inbox reply plans, and analytics briefings across 14 platforms including X/Twitter, Instagram, Facebook, LinkedIn, TikTok, YouTube, Pinterest, Reddit, Bluesky, Threads, Google Business, Telegram, Snapchat, and WhatsApp.",
-    "type": "worker",
-    "visibility": "public-open-source",
-    "sourceRepo": "growthub-local",
-    "family": "studio"
-  },
-  "entrypoint": {
-    "workerId": "zernio-social-operator",
-    "path": "workers/zernio-social-operator/CLAUDE.md"
-  },
-  "workerIds": [
-    "zernio-social-operator"
-  ],
-  "agentContractPath": "workers/zernio-social-operator/CLAUDE.md",
-  "brandTemplatePath": "brands/_template/brand-kit.md",
-  "publicExampleBrandPaths": [
-    "brands/growthub/brand-kit.md"
-  ],
-  "frozenAssetPaths": [
-    "QUICKSTART.md",
-    ".env.example",
-    "skills.md",
-    "output-standards.md",
-    "runtime-assumptions.md",
-    "validation-checklist.md",
-    "workers/zernio-social-operator/CLAUDE.md",
-    "brands/_template/brand-kit.md",
-    "brands/growthub/brand-kit.md",
-    "brands/NEW-CLIENT.md",
-    "setup/setup.mjs",
-    "setup/verify-env.mjs",
-    "setup/check-deps.sh",
-    "setup/check-deps.mjs",
-    "setup/install-mcp.mjs",
-    "output/README.md",
-    "templates/social-campaign-brief.md",
-    "templates/content-calendar.md",
-    "templates/platform-publishing-plan.md",
-    "templates/caption-copy-deck.md",
-    "templates/analytics-brief.md",
-    "templates/scheduling-manifest.md",
-    "templates/client-proposal.md",
-    "examples/social-campaign-sample.md",
-    "examples/content-calendar-sample.md",
-    "examples/analytics-brief-sample.md",
-    "examples/client-proposal-sample.md",
-    "docs/zernio-api-integration.md",
-    "docs/platform-coverage.md",
-    "docs/ai-caption-layer.md",
-    "docs/posts-and-queues-layer.md",
-    "docs/growthub-agentic-social-platform-ui-shell.md",
-    "docs/local-adapters.md",
-    "studio/.env.example",
-    "studio/serve.mjs",
-    "studio/index.html",
-    "studio/package.json",
-    "studio/package-lock.json",
-    "studio/vite.config.js",
-    "studio/dist/index.html",
-    "studio/dist/assets/index-DTmBMuXr.js",
-    "studio/dist/assets/index-gHr-nTMF.css",
-    "studio/src/App.jsx",
-    "studio/src/api.js",
-    "studio/src/app.css",
-    "studio/src/lib/rules.js",
-    "studio/src/lib/templates.js",
-    "studio/src/main.jsx",
-    "studio/src/views/Accounts.jsx",
-    "studio/src/views/Agent.jsx",
-    "studio/src/views/Analytics.jsx",
-    "studio/src/views/ApiKeys.jsx",
-    "studio/src/views/Automations.jsx",
-    "studio/src/views/CommentRules.jsx",
-    "studio/src/views/Compose.jsx",
-    "studio/src/views/Dashboard.jsx",
-    "studio/src/views/Inbox.jsx",
-    "studio/src/views/Queues.jsx",
-    "studio/src/views/Scheduled.jsx",
-    "studio/src/views/Sequences.jsx",
-    "studio/src/views/Templates.jsx",
-    "growthub-meta/README.md",
-    "growthub-meta/kit-standard.md",
-    "SKILL.md",
-    "templates/project.md",
-    "templates/self-eval.md",
-    "helpers/README.md",
-    "skills/README.md"
-  ],
-  "setupPaths": {
-    "quickstart": "QUICKSTART.md",
-    "setupDir": "setup/",
-    "outputDir": "output/"
-  },
-  "outputStandard": {
-    "type": "working-directory",
-    "description": "Exported folder is intended to be pointed at directly by the agent Working Directory. All outputs are Markdown files written to output/<client-slug>/<project-slug>/ alongside a machine-readable scheduling-manifest.json shaped for POST https://zernio.com/api/v1/posts.",
-    "requiredPaths": [
-      "QUICKSTART.md",
-      "kit.json",
-      ".env.example",
-      "bundles/growthub-zernio-social-v1.json",
-      "skills.md",
-      "workers/zernio-social-operator/CLAUDE.md",
-      "brands/_template/brand-kit.md",
-      "brands/growthub/brand-kit.md",
-      "brands/NEW-CLIENT.md",
-      "setup/verify-env.mjs",
-      "setup/check-deps.sh",
-      "output/README.md",
-      "studio",
-      "studio/dist",
-      "templates",
-      "docs",
-      "growthub-meta",
-      "SKILL.md",
-      "templates/project.md",
-      "templates/self-eval.md",
-      "helpers",
-      "helpers/README.md",
-      "skills",
-      "skills/README.md"
-    ]
-  },
-  "bundles": [
-    {
-      "id": "growthub-zernio-social-v1",
-      "version": "1.0.0",
-      "path": "bundles/growthub-zernio-social-v1.json"
-    }
-  ],
-  "executionMode": "export",
-  "activationModes": [
-    "export"
-  ],
-  "compatibility": {
-    "cliMinVersion": "0.3.53"
-  },
-  "provenance": {
-    "sourceRepo": "growthub-local",
-    "frozenAt": "2026-04-15T00:00:00.000Z"
-  },
-  "workspaceVisibility": "addon",
-  "workspaceCompatible": false,
-  "workspaceCategory": "social-media"
-}

package/assets/worker-kits/growthub-zernio-social-v1/output/README.md

@@ -1,63 +0,0 @@
-# Output Directory
-
-This directory is where all campaign deliverables are written.
-
----
-
-## Structure
-
-```
-output/
-  <client-slug>/
-    <project-slug>/
-      SocialCampaignBrief_v<N>_<YYYYMMDD>.md
-      ContentCalendar_v<N>_<YYYYMMDD>.md
-      PlatformPublishingPlan_v<N>_<YYYYMMDD>.md
-      CaptionCopyDeck_v<N>_<YYYYMMDD>.md
-      SchedulingManifest_v<N>_<YYYYMMDD>.md    (if scheduling requested)
-      AnalyticsBrief_v<N>_<YYYYMMDD>.md        (if analytics data provided)
-      ClientProposal_v<N>_<YYYYMMDD>.md        (if requested)
-      scheduling-manifest.json                  (machine-readable, for Zernio POST /api/v1/posts)
-      queue-<queue-name>.json                   (machine-readable, for Zernio POST /api/v1/queues)
-```
-
----
-
-## Naming Convention
-
-```
-<ClientSlug>_<OutputType>_v<N>_<YYYYMMDD>.md
-```
-
-- **ClientSlug:** TitleCase, no spaces (`UrbanCycle`, not `Urban Cycle`)
-- **OutputType:** CamelCase (`SocialCampaignBrief`, `ContentCalendar`, etc.)
-- **Version:** `v1`, `v2`, etc.
-- **Date:** `YYYYMMDD` format
-
-**Example:** `UrbanCycle_ContentCalendar_v1_20260415.md`
-
----
-
-## Adding a New Project
-
-When starting a campaign for a new client or a new project for an existing client:
-
-```bash
-mkdir -p output/<client-slug>/<project-slug>
-```
-
-The operator will write all deliverables to this directory and log the project in the brand kit DELIVERABLES LOG.
-
----
-
-## Git and Version Control
-
-The `output/` directory is excluded from kit exports. Do not commit client deliverables to the kit repository. Keep outputs in your local working directory or a separate client delivery folder.
-
-If you are version-controlling client outputs separately, use the project slug as the branch or folder name.
-
----
-
-## Secret Hygiene
-
-`scheduling-manifest.json` and `queue-*.json` never contain `ZERNIO_API_KEY` or any OAuth tokens. They reference Zernio resource ids only (`profileId`, `accountId`, `mediaId`). If you see a raw API key in an output file, treat it as a bug and scrub it before sharing.

package/assets/worker-kits/growthub-zernio-social-v1/output-standards.md

@@ -1,132 +0,0 @@
-# Output Standards
-
-**All Zernio Social Media Operator outputs must meet these standards before being delivered to a client.**
-
----
-
-## Output Directory Structure
-
-```
-output/
-  <client-slug>/
-    <project-slug>/
-      SocialCampaignBrief_v<N>_<YYYYMMDD>.md
-      ContentCalendar_v<N>_<YYYYMMDD>.md
-      PlatformPublishingPlan_v<N>_<YYYYMMDD>.md
-      CaptionCopyDeck_v<N>_<YYYYMMDD>.md
-      SchedulingManifest_v<N>_<YYYYMMDD>.md    (if scheduling requested)
-      AnalyticsBrief_v<N>_<YYYYMMDD>.md        (if analytics data available)
-      ClientProposal_v<N>_<YYYYMMDD>.md        (if requested)
-      scheduling-manifest.json                  (always when scheduling — powers Zernio POST /api/v1/posts)
-```
-
----
-
-## File Naming Convention
-
-```
-<ClientSlug>_<OutputType>_v<N>_<YYYYMMDD>.md
-```
-
-| Part | Rules | Example |
-|---|---|---|
-| ClientSlug | TitleCase, no spaces, no special chars | `UrbanCycle` |
-| OutputType | CamelCase from the list below | `ContentCalendar` |
-| Version | `v` + integer, starting at 1 | `v1` |
-| Date | `YYYYMMDD` format | `20260415` |
-
-**Output type names:**
-
-| Artifact | OutputType string |
-|---|---|
-| Social Campaign Brief | `SocialCampaignBrief` |
-| Content Calendar | `ContentCalendar` |
-| Platform Publishing Plan | `PlatformPublishingPlan` |
-| Caption Copy Deck | `CaptionCopyDeck` |
-| Scheduling Manifest | `SchedulingManifest` |
-| Analytics Brief | `AnalyticsBrief` |
-| Client Proposal | `ClientProposal` |
-
----
-
-## Required Sections Per Artifact
-
-Each artifact must include all sections from its template. Incomplete sections must be marked `<!-- data-gap: reason -->` — never left blank without explanation.
-
-| Artifact | Minimum Required Sections |
-|---|---|
-| SocialCampaignBrief | Project Overview, Campaign Objective, Target Platforms, Audience Profile, KPI Targets, Content Theme Pillars, Brand Voice |
-| ContentCalendar | Calendar Header (client, period, platforms, profile id), Calendar Table (all rows with all columns), Posting Cadence Summary |
-| PlatformPublishingPlan | Per-platform rows (all selected platforms), Format spec, Frequency, Best posting times, Content mix ratio |
-| CaptionCopyDeck | Per-post entries (A/B/C variants each), Hashtag sets, Character counts, Media asset notes |
-| SchedulingManifest | Manifest header (profileId, timezone, dryRun), All post entries (clientPostId, content, scheduledFor, platforms[], media[], status) |
-| AnalyticsBrief | Period summary, Per-platform metrics table, Top 3 posts, Bottom 3 posts, Recommendations |
-| ClientProposal | Campaign Overview, Platform Mix rationale, Content Strategy, Deliverables scope, Pricing (3 tiers), ROI Projection |
-
----
-
-## Quality Bar
-
-### Platform-Accurate
-
-- All platform IDs must match the official list in `docs/platform-coverage.md`
-- Character limits must be respected for every caption variant
-- Post types must be valid for the target platform (e.g., no carousels on TikTok or X)
-
-### Caption Quality
-
-- Every caption must have an explicit CTA — "Learn more" is acceptable; blank is not
-- All 3 variants (A/B/C) must be meaningfully different — not minor word swaps
-- Hashtags must be relevant to the content — no generic filler unless platform context demands it
-
-### Scheduling Manifest
-
-- `scheduledFor` timestamps must be ISO 8601 format with timezone offset
-- `clientPostId` must follow the naming convention: `<client-slug>-<YYYYMMDD>-<sequence>`
-- All posts in the manifest must have a corresponding entry in the ContentCalendar
-- `profileId` must be present (non-empty) — never hardcode to a placeholder string without also setting `dryRun: true`
-- Every `platforms[].platform` value must exist in `docs/platform-coverage.md`
-- Every `platforms[].accountId` must either be a real Zernio account id (live mode) or a documented placeholder tagged with the handle (agent-only mode)
-
-### No Filler
-
-- Every sentence must either present data, explain a constraint, or specify an action
-- Remove phrases like "Great content is key" — replace with the actual content specification
-- Recommendations must be specific: name the exact platform, posting time, content format, and expected impact
-
-### Actionable
-
-- Every post entry in the ContentCalendar must have a ready-to-use caption variant
-- Every platform in the PlatformPublishingPlan must have a posting time recommendation
-- Every finding in the AnalyticsBrief must have a corresponding action item
-
-### Consistent
-
-- Platform names in all artifacts must use the same slug format from `docs/platform-coverage.md`
-- Dates must be consistent across all artifacts
-- Client name must match the brand kit exactly
-
----
-
-## Versioning Rules
-
-| Scenario | Action |
-|---|---|
-| First campaign for a client | All files at v1 |
-| Campaign revised post-approval | Increment all files to v2 |
-| Partial update (one artifact revised) | Increment only the revised artifact's version |
-| New campaign, same client | Start new project-slug, all files at v1 |
-
----
-
-## scheduling-manifest.json
-
-This file must always be written to the output directory when scheduling is requested. It is the machine-readable record required for:
-
-- Zernio API scheduled post creation (one `POST /api/v1/posts` per entry or a batched sequence)
-- Manual review before submitting to Zernio
-- Campaign audit trail
-
-See `templates/scheduling-manifest.md` and `docs/posts-and-queues-layer.md` for the complete format with all required fields.
-
-Every write request to Zernio must include an `Idempotency-Key` header — the operator must instruct the downstream executor to use the `clientPostId` as that key so re-submissions are safe.