@growthub/cli 0.14.5 → 0.14.8

package/assets/worker-kits/growthub-zernio-social-v1/templates/client-proposal.md

@@ -1,98 +0,0 @@
-# Client Proposal — [Client Name] · [Campaign Name]
-
-**Kit:** `growthub-zernio-social-v1`
-**Generated:** [YYYY-MM-DD]
-**Mode:** [api-live | agent-only | hybrid]
-**Version:** `v1`
-
----
-
-## Campaign Overview
-
-| Field | Value |
-|---|---|
-| Client | [Client Name] |
-| Campaign | [Campaign Name] |
-| Window | [YYYY-MM-DD] → [YYYY-MM-DD] |
-| Primary objective | [brand awareness | lead generation | engagement | product launch | community growth] |
-| Platforms in scope | [comma-separated Zernio slugs] |
-
----
-
-## Platform Mix Rationale
-
-| Platform | Role in this campaign | Why selected |
-|---|---|---|
-| `instagram` | [Primary visual channel] | [Audience fit + content format fit] |
-| `linkedin` | [B2B thought leadership] | [Rationale] |
-| `twitter` | [Real-time voice + community] | [Rationale] |
-
----
-
-## Content Strategy
-
-- Theme pillars: [list]
-- Format mix: [Per platform]
-- Cadence: [Summary table reference to Platform Publishing Plan]
-- Caption approach: A/B/C variants per post — see Caption Copy Deck
-
----
-
-## Deliverables Scope
-
-| Deliverable | Included | Notes |
-|---|---|---|
-| Social Campaign Brief | Yes | One per campaign |
-| Content Calendar | Yes | 30 / 60 / 90 day |
-| Platform Publishing Plan | Yes | One per campaign |
-| Caption Copy Deck | Yes | A/B/C variants for every scheduled post |
-| Scheduling Manifest | Yes | Zernio-shaped JSON + submission to `POST /api/v1/posts` |
-| Recurring Queue | Optional | Only when campaign uses evergreen slots |
-| Analytics Brief | Monthly | Pulled from Zernio API |
-| Inbox reply coverage | Optional | DMs + comments + reviews via unified inbox |
-
----
-
-## Pricing Tiers
-
-| Tier | Scope | Monthly |
-|---|---|---|
-| Starter | 2 platforms, 3 posts/week, monthly analytics | $[X] |
-| Growth | 4 platforms, daily posts, biweekly analytics, inbox coverage | $[X] |
-| Scale | 6+ platforms, daily posts with queues, weekly analytics, priority inbox | $[X] |
-
-All tiers include the full deliverable set scoped to the platform count.
-
----
-
-## ROI Projection
-
-Ground every number in documented platform benchmarks (see brand kit and `docs/platform-coverage.md`). Never invent metrics.
-
-| KPI | Tier 1 target | Tier 2 target | Tier 3 target |
-|---|---|---|---|
-| Impressions / month | [N] | [N] | [N] |
-| Engagement rate | [N%] | [N%] | [N%] |
-| Follower growth | [+N] | [+N] | [+N] |
-| Link clicks | [N] | [N] | [N] |
-
----
-
-## Onboarding Plan
-
-1. Connect target social accounts inside Zernio (`/api/v1/connect/<platform>`)
-2. Confirm `ZERNIO_PROFILE_ID` and scope of the API key
-3. Review Content Theme Pillars in the Social Campaign Brief
-4. Approve the Platform Publishing Plan and cadence
-5. Approve the Caption Copy Deck (A/B/C variants)
-6. Submit the Scheduling Manifest to Zernio with `Idempotency-Key` per post
-7. Cadence review at week 4 alongside the first Analytics Brief
-
----
-
-## Terms
-
-- Ownership of all content stays with the client
-- API key and account credentials stay inside the client's Zernio account
-- The operator never stores raw Zernio API keys or OAuth tokens
-- Cancellation: [standard terms from retainer agreement]

package/assets/worker-kits/growthub-zernio-social-v1/templates/content-calendar.md

@@ -1,70 +0,0 @@
-# Content Calendar — [Client Name] · [Project Name]
-
-**Kit:** `growthub-zernio-social-v1`
-**Generated:** [YYYY-MM-DD]
-**Mode:** [api-live | agent-only | hybrid]
-**Version:** `v1`
-
----
-
-## Calendar Header
-
-| Field | Value |
-|---|---|
-| Client | [Client Name] |
-| Zernio profile id | [prof_... or placeholder] |
-| Campaign window | [YYYY-MM-DD] → [YYYY-MM-DD] |
-| Platforms | [comma-separated Zernio platform slugs] |
-| Posting timezone | [IANA tz] |
-
----
-
-## Calendar Table
-
-Column contract (one row per scheduled post):
-
-| Date | Day | Platform | Account | Theme | Post Type | Caption Preview | CTA | Media Notes | Status |
-|---|---|---|---|---|---|---|---|---|---|
-| YYYY-MM-DD | Mon | `instagram` | [@handle or accountId] | [Pillar] | image | [first 100 chars of variant A] | [CTA] | [dims, duration, overlays] | draft |
-| YYYY-MM-DD | Mon | `twitter` | [@handle or accountId] | [Pillar] | text | [first 100 chars] | [CTA] | — | draft |
-| YYYY-MM-DD | Tue | `linkedin` | [page id or accountId] | [Pillar] | carousel | [first 100 chars] | [CTA] | [slide count + order] | draft |
-| ... | | | | | | | | | |
-
-### Rules
-
-- One row per scheduled post
-- `Platform` values must exist in `docs/platform-coverage.md`
-- `Post Type` must be valid for the platform
-- `Caption Preview` is the first 100 characters of the selected variant — full captions live in the Caption Copy Deck
-- `CTA` is required and non-empty
-- `Media Notes` are required for image/video/carousel/reel/short/story
-- `Status` defaults to `draft` and moves to `scheduled` once the manifest is submitted
-
----
-
-## Posting Cadence Summary
-
-| Platform | Posts / week | Best time window | Notes |
-|---|---|---|---|
-| `instagram` | [3] | [12:00–13:00 local] | [rationale] |
-| `linkedin` | [3] | [08:00–09:30 local] | [rationale] |
-| `twitter` | [7] | [spread: 08:00, 12:00, 17:00] | [rationale] |
-
----
-
-## Theme Pillar Distribution
-
-| Pillar | Count | % of calendar |
-|---|---|---|
-| [Pillar 1] | [N] | [40%] |
-| [Pillar 2] | [N] | [30%] |
-| [Pillar 3] | [N] | [20%] |
-| [Pillar 4] | [N] | [10%] |
-
----
-
-## Notes
-
-- Cadence must match the Platform Publishing Plan
-- Multi-platform posts spaced ≥30 minutes apart to avoid simultaneous-publishing optics
-- Weekend slots default to community / engagement pillars unless client overrides

package/assets/worker-kits/growthub-zernio-social-v1/templates/platform-publishing-plan.md

@@ -1,86 +0,0 @@
-# Platform Publishing Plan — [Client Name] · [Project Name]
-
-**Kit:** `growthub-zernio-social-v1`
-**Generated:** [YYYY-MM-DD]
-**Mode:** [api-live | agent-only | hybrid]
-**Version:** `v1`
-
----
-
-## Per-Platform Rows
-
-Produce one row per platform in scope. Every field is required.
-
-### [Platform — e.g., Instagram]
-
-| Field | Value |
-|---|---|
-| Zernio platform id | `instagram` |
-| Zernio account id | [acc_ig_... or `placeholder_@handle` in agent-only] |
-| Format mix | [e.g., 40% reels, 30% carousel, 20% single image, 10% story] |
-| Posting frequency | [e.g., 3/week + daily stories] |
-| Best posting times (local) | [e.g., Tue 12:00, Thu 12:00, Sat 10:30] |
-| Primary theme pillars | [pillar names] |
-| Caption length target | [e.g., 125–150 chars above the fold] |
-| Hashtag count | [e.g., 3–5 primary] |
-| Content mix rationale | [One paragraph: why this mix fits the audience and objective] |
-
-### [Platform — e.g., LinkedIn]
-
-| Field | Value |
-|---|---|
-| Zernio platform id | `linkedin` |
-| Zernio account id | [page id or accountId] |
-| Format mix | [e.g., 50% text+image, 30% document carousel, 20% video] |
-| Posting frequency | [e.g., 3/week] |
-| Best posting times (local) | [e.g., Tue 08:30, Wed 08:30, Thu 08:30] |
-| Primary theme pillars | [pillar names] |
-| Caption length target | [e.g., 1,200–2,000 chars for thought leadership] |
-| Hashtag count | [e.g., 3–5 professional] |
-| Content mix rationale | [One paragraph] |
-
-### [Platform — e.g., X/Twitter]
-
-| Field | Value |
-|---|---|
-| Zernio platform id | `twitter` |
-| Zernio account id | [acc_x_...] |
-| Format mix | [e.g., 60% text, 25% image, 15% thread] |
-| Posting frequency | [e.g., 7/week] |
-| Best posting times (local) | [e.g., 08:00, 12:00, 17:00] |
-| Primary theme pillars | [pillar names] |
-| Caption length target | [e.g., 200–240 chars] |
-| Hashtag count | [1–2] |
-| Content mix rationale | [One paragraph] |
-
----
-
-## Cross-Platform Orchestration
-
-| Rule | Value |
-|---|---|
-| Minimum gap between simultaneous posts | 30 minutes |
-| Collision check | Run against `GET /api/v1/posts?status=scheduled` before submission |
-| Queue in use | [queue name or `none`] |
-| Default timezone | [IANA tz] |
-
----
-
-## Queue Coverage (if applicable)
-
-| Queue name | Platforms covered | Slots per week |
-|---|---|---|
-| [weekly-evergreen] | [twitter, linkedin] | [3] |
-| [daily-visual] | [instagram] | [5] |
-
-If queues are used, posts scheduled into a queue omit `scheduledFor` from the Zernio body and include `queueId` — see `docs/posts-and-queues-layer.md`.
-
----
-
-## Go-Live Checklist
-
-- [ ] Every platform in this plan is connected on the Zernio profile
-- [ ] Every `accountId` is a real Zernio id (live mode) or a documented placeholder (agent-only)
-- [ ] Posting windows cross-checked against existing scheduled posts
-- [ ] Hashtag and caption rules match `docs/ai-caption-layer.md`
-- [ ] Client approved the plan before any write requests are issued

package/assets/worker-kits/growthub-zernio-social-v1/templates/project.md

@@ -1,48 +0,0 @@
----
-# .growthub-fork/project.md — session memory primitive (v1)
-#
-# Written by the CLI at init/import time. Append-only, human-readable; sits
-# alongside the machine-readable `trace.jsonl`. Approvals, self-eval outcomes,
-# and sub-skill runs all record here.
-#
-# Replaceable tokens (seeded at init time):
-#   {{KIT_ID}}   {{FORK_ID}}   {{STARTED_AT}}   {{SOURCE}}   {{SOURCE_REF}}
-
-kitId: "{{KIT_ID}}"
-forkId: "{{FORK_ID}}"
-startedAt: "{{STARTED_AT}}"
-source: "{{SOURCE}}"
-sourceRef: "{{SOURCE_REF}}"
-skillManifestVersion: 1
-approvals: []
-selfEvalHistory: []
-subSkillRuns: []
----
-
-# Project journal — fork `{{FORK_ID}}`
-
-Baseline primitive: `{{KIT_ID}}`. Seeded at `{{STARTED_AT}}` from `{{SOURCE}}` (`{{SOURCE_REF}}`).
-
-This is your cross-session continuity surface. Read the last few entries before every session; append after every material change, approval, and self-eval boundary.
-
-## How to use this file
-
-1. **Session start.** Read the last 3 entries + tail 20 events in `.growthub-fork/trace.jsonl`. State your plan.
-2. **Material change.** Record as a dated bullet (what, why, outcome). Simultaneously append a typed event to `trace.jsonl` via the Fork Sync Agent — never bypass.
-3. **Approval boundary.** Add a row to `approvals` in the frontmatter (verbatim decision).
-4. **Self-eval boundary.** Append to `selfEvalHistory`: `attempt`, `criteria`, `outcome`, `notes`. Enforce `maxRetries: 3`.
-5. **Sub-skill spawn.** Append to `subSkillRuns`: `subSkill`, `startedAt`, `result`.
-
-## Session log
-
-<!-- Append newest entries at the bottom. Format:
-
-### {{YYYY-MM-DD HH:mm UTC}} · {{skill-slug}}
-- **Plan.** What you intend to do.
-- **Changes.** Material changes (each must correspond to a trace event).
-- **Outcome.** Pass / fail / parked. Reference self-eval criteria.
-- **Next.** What the next session should pick up.
-
--->
-
-_No sessions recorded yet. Populated as the fork is operated._

package/assets/worker-kits/growthub-zernio-social-v1/templates/scheduling-manifest.md

@@ -1,92 +0,0 @@
-# Scheduling Manifest — [Client Name] · [Project Name]
-
-**Kit:** `growthub-zernio-social-v1`
-**Generated:** [YYYY-MM-DD]
-**Mode:** [api-live | agent-only | hybrid]
-**Version:** `v1`
-
----
-
-## Purpose
-
-This file documents the Zernio-shaped scheduling manifest for this campaign. The machine-readable companion is `scheduling-manifest.json` in the same folder — the operator writes that file alongside this Markdown record.
-
-Manifest shape is fully specified in `docs/posts-and-queues-layer.md`. Every post entry is a valid `POST /api/v1/posts` body (minus the two bookkeeping fields `clientPostId` and `status`).
-
----
-
-## Manifest Header
-
-| Field | Value |
-|---|---|
-| `version` | `1.0` |
-| `profileId` | [prof_... or `placeholder`] |
-| `timezone` | [IANA tz, e.g., `America/New_York`] |
-| `dryRun` | [true in agent-only mode, false otherwise] |
-| `generatedAt` | [ISO 8601 with tz offset] |
-| Post count | [N entries] |
-
----
-
-## Post Entries (reference table)
-
-| clientPostId | scheduledFor | platforms (count) | media (count) | status |
-|---|---|---|---|---|
-| `urban-cycle-20260501-001` | 2026-05-01T09:00:00-04:00 | 2 | 1 | pending |
-| `urban-cycle-20260501-002` | 2026-05-01T12:30:00-04:00 | 1 | 0 | pending |
-
-Full JSON lives in `scheduling-manifest.json` beside this file.
-
----
-
-## Reference JSON Block
-
-```json
-{
-  "zernioSchedulingManifest": {
-    "version": "1.0",
-    "profileId": "prof_abc123",
-    "timezone": "America/New_York",
-    "dryRun": false,
-    "generatedAt": "2026-04-15T14:30:00-04:00",
-    "posts": [
-      {
-        "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"
-      }
-    ]
-  }
-}
-```
-
----
-
-## Submission Sequence
-
-1. Upload every referenced media asset via `POST /api/v1/media`, capturing each returned `mediaId`
-2. Replace placeholder media IDs in `scheduling-manifest.json`
-3. Iterate `posts[]`, issuing one `POST /api/v1/posts` per entry with `Idempotency-Key: <clientPostId>`
-4. Update each entry's `status` from `pending` to `scheduled` on 2xx, or `failed` on non-2xx with the Zernio `requestId`
-5. If the campaign uses a recurring queue, submit `POST /api/v1/queues` first so its id can be referenced by queued post entries
-
----
-
-## Validation Before Submit
-
-- [ ] Every post in the manifest also exists in the Content Calendar
-- [ ] Every caption is the selected variant from the Caption Copy Deck
-- [ ] Every platform exists in `docs/platform-coverage.md`
-- [ ] Every `scheduledFor` is ISO 8601 with timezone offset
-- [ ] Every `clientPostId` follows `<client-slug>-<YYYYMMDD>-<sequence>`
-- [ ] In api-live mode, every `accountId` is confirmed via `GET /api/v1/accounts`
-- [ ] `dryRun` matches the execution mode declared in the Social Campaign Brief
-
-Failure on any of these blocks submission.

package/assets/worker-kits/growthub-zernio-social-v1/templates/self-eval.md

@@ -1,67 +0,0 @@
-# Self-evaluation template — v1 primitive (Growthub, capability-agnostic)
-
-A skill's `selfEval` contract declares **what good looks like** (`criteria[]`) and **the retry ceiling** (`maxRetries`). The agent drives the loop; this file is the pattern the agent follows at every unit of work.
-
-The contract is defined in `@growthub/api-contract/skills::SkillSelfEval` and is **capability-agnostic** — the same primitive applies to code edits, copy drafts, CRM rules, API payloads, asset renders, audit passes, and every other domain. The "unit of work" is the smallest reversible change the skill operates on; concrete boundaries are defined in the kit's own `skills.md` operator runbook, not here.
-
-## Loop
-
-```
-for attempt in 1..maxRetries:          # default maxRetries = 3
-  generate       — produce a proposal (whatever the skill produces)
-  apply          — materialise the proposal against the fork
-  self-evaluate  — for each criterion in skill.selfEval.criteria:
-                     check → pass / fail / needs-confirmation
-  record         — append to project.md (human) + trace.jsonl (machine)
-
-  if all criteria pass: break
-  if attempt == maxRetries: park with needs_confirmation note. Stop.
-```
-
-## What each attempt writes
-
-### Human row — append to `.growthub-fork/project.md` "Session log"
-
-```md
-### 2026-04-23 18:40 UTC · <skill-slug>
-- **Plan.** What you intend to do this unit of work.
-- **Changes.** Material change applied (must correspond to a trace event).
-- **Self-eval.** attempt 2/3 — criterion "<one of skill.selfEval.criteria>" ✗ (<note>). Retrying.
-- **Outcome.** retry-pending / pass / parked.
-- **Next.** What the next attempt (or next session) should pick up.
-```
-
-### Machine row — append to `.growthub-fork/trace.jsonl` (via `appendKitForkTraceEvent`)
-
-```json
-{
-  "ts": "2026-04-23T18:40:00.000Z",
-  "forkId": "<fork-id>",
-  "kitId": "<kit-id>",
-  "type": "self_eval_recorded",
-  "summary": "attempt 2/3 failed on <criterion>",
-  "detail": {
-    "skill": "<skill-slug>",
-    "attempt": 2,
-    "maxRetries": 3,
-    "criterion": "<one of skill.selfEval.criteria>",
-    "outcome": "fail",
-    "notes": "<short explanation>"
-  }
-}
-```
-
-## Hard rules
-
-1. **Never exceed `maxRetries`.** At the ceiling, park with a `needs_confirmation` note and stop. Do not loop forever.
-2. **Record every attempt.** Even the first pass. Continuity depends on a complete journal.
-3. **Keep `project.md` and `trace.jsonl` in sync.** One without the other is a protocol violation.
-4. **Preserve prior entries.** Append-only. Never rewrite history.
-
-## Bound the blast radius
-
-Evaluate at the smallest unit of work the skill operates on, not only at the end of a multi-step run. The retry ceiling applies to that unit — so a bad attempt does not sink the whole job.
-
-What counts as a "unit of work" is **kit-specific** and lives in that kit's `skills.md` operator runbook — not in this agnostic template. A kit picks its own smallest reversible boundary and documents it in `skills.md`; this template does not prescribe one.
-
-The agnostic SDK (`@growthub/api-contract/skills::SkillSelfEval`) does not encode any domain-specific boundaries — it only carries `criteria[]`, `maxRetries`, and `traceTo`. See `SKILL.md::selfEval.criteria` in this kit for the concrete checks, and `skills.md` for the kit-specific unit of work.

package/assets/worker-kits/growthub-zernio-social-v1/templates/social-campaign-brief.md

@@ -1,102 +0,0 @@
-# Social Campaign Brief — [Client Name] · [Project Name]
-
-**Kit:** `growthub-zernio-social-v1`
-**Generated:** [YYYY-MM-DD]
-**Mode:** [api-live | agent-only | hybrid]
-**Version:** `v1`
-
----
-
-## Project Overview
-
-| Field | Value |
-|---|---|
-| Client | [Client Name] |
-| Project | [Project Name] |
-| Campaign window | [YYYY-MM-DD] → [YYYY-MM-DD] |
-| Zernio profile id | [prof_...] or `placeholder` in agent-only mode |
-| Posting timezone | [IANA tz name, e.g., America/New_York] |
-
----
-
-## Campaign Objective
-
-**Primary:** [brand awareness | lead generation | engagement | product launch | community growth]
-
-**Why this objective:** [One paragraph grounded in the brand kit's current stage and retainer context.]
-
----
-
-## Target Platforms
-
-| Platform | Zernio ID | Account | Rationale |
-|---|---|---|---|
-| [Instagram] | `instagram` | [@handle or accountId] | [Why selected — demographics, format fit, client capacity] |
-| [LinkedIn]  | `linkedin`  | [company page or accountId] | [Why selected] |
-| [X/Twitter] | `twitter`   | [@handle] | [Why selected] |
-
-Max 5 platforms unless the brand kit documents the team capacity to support more.
-
----
-
-## Audience Profile
-
-### Primary
-
-| Attribute | Value |
-|---|---|
-| Age range | [range] |
-| Geography | [regions or countries] |
-| Interests | [top 3–5] |
-| Pain points | [top 3] |
-| Content preferences | [formats + topics] |
-
-### Secondary
-
-| Attribute | Value |
-|---|---|
-| Age range | [range] |
-| Platforms | [where they are concentrated] |
-| Interests | [top 2–3] |
-
----
-
-## KPI Targets
-
-| KPI | Metric | Target | Timeline |
-|---|---|---|---|
-| [Brand awareness] | [Impressions] | [50,000/month] | [Month 1] |
-| [Engagement] | [Engagement rate] | [≥3%] | [Rolling] |
-| [Lead generation] | [Link clicks] | [200/month] | [Month 1] |
-
----
-
-## Content Theme Pillars
-
-| Pillar | Description | % of calendar | Primary platforms |
-|---|---|---|---|
-| [Pillar 1] | [One-sentence definition] | [40%] | [platforms] |
-| [Pillar 2] | [Definition] | [30%] | [platforms] |
-| [Pillar 3] | [Definition] | [20%] | [platforms] |
-| [Pillar 4] | [Definition] | [10%] | [platforms] |
-
----
-
-## Brand Voice Summary
-
-| Attribute | Spec |
-|---|---|
-| Tone | [From brand kit] |
-| Words to use | [Top 5–8] |
-| Words to avoid | [Top 5–8] |
-| Emoji rule | [Per platform] |
-| CTA style | [From brand kit] |
-
----
-
-## Execution Notes
-
-- Caption variants: 3 per post (A direct, B narrative, C question/hook)
-- Every write request to Zernio uses `Idempotency-Key = clientPostId`
-- `dryRun` is `[true/false]` based on execution mode
-- Manifest submission order: media uploads → posts → (optional) queue creation

package/assets/worker-kits/growthub-zernio-social-v1/validation-checklist.md

@@ -1,85 +0,0 @@
-# Validation Checklist — growthub-zernio-social-v1
-
-**Run through this checklist before starting every operator session and before delivering any artifact package.**
-
----
-
-## Pre-Session Checklist
-
-### Environment Gate
-
-- [ ] Node.js 18+ is installed (`node --version` returns 18+)
-- [ ] `curl` is installed (used for Zernio healthchecks)
-- [ ] Git is installed (`git --version`)
-
-### Api-Live Mode (skip if agent-only)
-
-- [ ] `ZERNIO_API_KEY` is set in `.env` and matches `sk_` + 64 hex format
-- [ ] `ZERNIO_API_URL` is set (default `https://zernio.com/api/v1`)
-- [ ] `GET /api/v1/profiles` returns 200 with the API key
-- [ ] `ZERNIO_PROFILE_ID` is set and exists on the account
-- [ ] At least one platform account is connected on the profile (`GET /api/v1/accounts`)
-- [ ] API key scope is `read-write` (required for scheduling)
-
-### Agent-Only Mode (skip if api-live)
-
-- [ ] Mode is confirmed with the user and documented as `agent-only` at the top of all outputs
-- [ ] Scheduling manifests are marked as `"dryRun": true` in the manifest header
-- [ ] Every `platforms[].accountId` is flagged as placeholder tagged with the account handle
-
-### Context
-
-- [ ] Brand kit exists for the active client (`brands/<client-slug>/brand-kit.md`)
-- [ ] Campaign objective is confirmed (one of: brand awareness / lead generation / engagement / product launch / community growth)
-- [ ] Target platforms are confirmed and in the supported list (`docs/platform-coverage.md`)
-- [ ] Campaign timeframe and posting cadence are confirmed
-
----
-
-## Pre-Delivery Checklist
-
-### Content Calendar
-
-- [ ] All calendar rows have dates within the campaign window
-- [ ] All platform slugs match `docs/platform-coverage.md`
-- [ ] All post types are valid for their target platform
-- [ ] Every row has a non-empty CTA
-- [ ] Media asset notes are present for all image/video/carousel posts
-
-### Caption Copy Deck
-
-- [ ] All 3 variants (A/B/C) are present for every post entry
-- [ ] All captions respect platform character limits
-- [ ] Hashtag counts are within platform-recommended ranges
-- [ ] No placeholder text remains (no `[INSERT CAPTION HERE]` style fragments)
-
-### Scheduling Manifest
-
-- [ ] Shape matches `POST /api/v1/posts` body expectations (see `docs/posts-and-queues-layer.md`)
-- [ ] All `scheduledFor` timestamps are ISO 8601 with explicit timezone offset
-- [ ] All `clientPostId` values follow the naming convention
-- [ ] `profileId` is present (or the manifest is `"dryRun": true`)
-- [ ] `platforms[].platform` values all exist in `docs/platform-coverage.md`
-- [ ] Every post in the manifest has a corresponding entry in the ContentCalendar
-
-### Output Files
-
-- [ ] All files follow the naming convention (`ClientSlug_OutputType_v<N>_<YYYYMMDD>.md`)
-- [ ] All files are saved to `output/<client-slug>/<project-slug>/`
-- [ ] Deliverable is logged in the brand kit DELIVERABLES LOG
-- [ ] No API keys, tokens, or credentials appear in any output file
-- [ ] No partial Zernio request responses with raw auth headers are included
-
----
-
-## Kit Integrity Checklist (run after kit changes)
-
-- [ ] `kit.json` is valid JSON with `schemaVersion: 2`
-- [ ] All paths in `frozenAssetPaths` exist on disk
-- [ ] All paths in `outputStandard.requiredPaths` exist on disk
-- [ ] Bundle manifest `bundles/growthub-zernio-social-v1.json` exists and matches kit.json
-- [ ] `bundle.kitId` in bundle manifest matches `kit.id` in kit.json
-- [ ] `bundle.workerId` in bundle manifest matches `entrypoint.workerId` in kit.json
-- [ ] All paths in `requiredFrozenAssets` in bundle manifest exist on disk
-- [ ] `node scripts/check-worker-kits.mjs` passes
-- [ ] `bash scripts/check-custom-workspace-kernel.sh` passes