@growthub/cli 0.3.56 → 0.3.58

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

@@ -0,0 +1,74 @@
+# Content Calendar — Growthub · Q2 2026 Agent-Native CLI Launch
+
+**Kit:** `growthub-zernio-social-v1`
+**Generated:** 2026-04-15
+**Mode:** api-live
+**Version:** `v1`
+
+---
+
+## Calendar Header
+
+| Field | Value |
+|---|---|
+| Client | Growthub |
+| Zernio profile id | prof_GRO_primary |
+| Campaign window | 2026-05-01 → 2026-05-30 |
+| Platforms | `twitter`, `linkedin`, `bluesky`, `youtube` |
+| Posting timezone | America/New_York |
+
+---
+
+## Calendar Table (first two weeks shown)
+
+| Date | Day | Platform | Account | Theme | Post Type | Caption Preview | CTA | Media Notes | Status |
+|---|---|---|---|---|---|---|---|---|---|
+| 2026-05-01 | Fri | `twitter` | acc_x_growthubai | Product Builds | thread | Q2 is here and the Agent Harness is production-ready. Here's what | Try it now | — | draft |
+| 2026-05-01 | Fri | `linkedin` | acc_li_GrowthubPage | Product Builds | text+image | Q2 is the window where Growthub's Agent Harness moves from preview | Read the docs | 1200x627 launch cover | draft |
+| 2026-05-01 | Fri | `youtube` | acc_yt_GrowthubAI | Developer Tutorials | long-form | Agent Harness end-to-end walkthrough: kits, workflows, pipelines | Subscribe for weekly builds | 1920x1080 thumbnail, 16:9 video | draft |
+| 2026-05-02 | Sat | `twitter` | acc_x_growthubai | Community | text | Weekend builder log: three wins from the week shipping Agent Harness | Drop yours | — | draft |
+| 2026-05-03 | Sun | `bluesky` | acc_bsky_growthub | Open Source | text | Sunday OSS spotlight — the one tool we couldn't have shipped without | Check it out | — | draft |
+| 2026-05-05 | Tue | `twitter` | acc_x_growthubai | Developer Tutorials | image | 30 seconds: `growthub kit download growthub-zernio-social-v1` to | Star on GitHub | Terminal demo screencap | draft |
+| 2026-05-05 | Tue | `linkedin` | acc_li_GrowthubPage | Developer Tutorials | document/carousel | Three ways agent-native CLIs change how teams ship social campaigns | Try it now | 5-slide carousel, 1080x1080 | draft |
+| 2026-05-06 | Wed | `bluesky` | acc_bsky_growthub | Product Builds | text | We chose a kit-first architecture so every workspace ships as a po | Read the docs | — | draft |
+| 2026-05-07 | Thu | `twitter` | acc_x_growthubai | Product Builds | thread | Why we ship kits, not features: the short version and the tradeoffs | Read the docs | — | draft |
+| 2026-05-07 | Thu | `youtube` | acc_yt_GrowthubAI | Developer Tutorials | short | 60s — add a Growthub kit to your workflow | Subscribe | 1080x1920, captions-on | draft |
+| 2026-05-08 | Fri | `linkedin` | acc_li_GrowthubPage | Community | text | Three user projects this week that bent our roadmap in a good way | Share yours | — | draft |
+| 2026-05-09 | Sat | `twitter` | acc_x_growthubai | Community | text | What are you building this weekend? Reply with a link — we rep the | Drop a link | — | draft |
+| 2026-05-10 | Sun | `bluesky` | acc_bsky_growthub | Community | text | Sunday show-and-tell — what's the smallest win you shipped this wee | Share it | — | draft |
+| 2026-05-12 | Tue | `twitter` | acc_x_growthubai | Open Source | image | Open source maturity ladder — where agent tooling is right now and | Keep going | Diagram 1200x675 | draft |
+| 2026-05-12 | Tue | `linkedin` | acc_li_GrowthubPage | Open Source | text+image | Open source maturity isn't about stars. It's about reproducible env | Read the guide | 1200x627 | draft |
+| 2026-05-14 | Thu | `twitter` | acc_x_growthubai | Developer Tutorials | thread | Step by step: how to ship a full social-media campaign with growth | Try it now | — | draft |
+| 2026-05-14 | Thu | `youtube` | acc_yt_GrowthubAI | Developer Tutorials | long-form | Full walkthrough: growthub-zernio-social-v1 from download to publi | Subscribe | 1920x1080, 18 min | draft |
+
+Full calendar (weeks 3–4) continues the same cadence — product builds early week, tutorial mid-week, community Fridays and weekends, OSS Sundays.
+
+---
+
+## Posting Cadence Summary
+
+| Platform | Posts / week | Best time window (America/New_York) | Notes |
+|---|---|---|---|
+| `twitter` | 7 | 08:00, 12:00, 17:00 | Anchor platform; highest-cadence |
+| `linkedin` | 3 | Tue 08:30, Thu 08:30, Fri 09:00 | Never more than 1/day |
+| `bluesky` | 3 | Wed 10:00, Sun 11:00, plus ad-hoc | Text-first, no hashtags |
+| `youtube` | 2 (1 long-form, 1 short) | Thu 12:00, Sat 10:00 | Long-form Thursdays drive weekend discovery |
+
+---
+
+## Theme Pillar Distribution
+
+| Pillar | Count | % of calendar |
+|---|---|---|
+| Product Builds | 11 | 35% |
+| Developer Tutorials | 9 | 30% |
+| Open Source | 6 | 20% |
+| Community | 5 | 15% |
+
+---
+
+## Notes
+
+- Multi-platform posts (e.g., 2026-05-01 X + LinkedIn) are spaced 45 minutes apart — X first, LinkedIn second — to avoid simultaneous-publishing optics
+- The `weekly-build-log` recurring queue handles Saturday community posts so cadence is stable through Q2
+- YouTube long-form premieres are disabled — scheduled publish only, to keep control inside Zernio

package/assets/worker-kits/growthub-zernio-social-v1/examples/social-campaign-sample.md

@@ -0,0 +1,105 @@
+# Social Campaign Brief — Growthub · Q2 2026 Agent-Native CLI Launch
+
+**Kit:** `growthub-zernio-social-v1`
+**Generated:** 2026-04-15
+**Mode:** api-live
+**Version:** `v1`
+
+---
+
+## Project Overview
+
+| Field | Value |
+|---|---|
+| Client | Growthub |
+| Project | Q2 2026 Agent-Native CLI Launch |
+| Campaign window | 2026-05-01 → 2026-05-30 |
+| Zernio profile id | prof_GRO_primary |
+| Posting timezone | America/New_York |
+
+---
+
+## Campaign Objective
+
+**Primary:** community growth with a strong secondary for lead generation
+
+**Why this objective:** Growthub's flywheel is developer adoption. The CLI ships daily; every release earns a round of organic developer commentary on X, Bluesky, and LinkedIn. Q2 is the first window where the newly-shipped Agent Harness is production-ready, and the campaign goal is to convert that community interest into measurable open-source adoption (CLI downloads, GitHub stars, waitlist signups).
+
+---
+
+## Target Platforms
+
+| Platform | Zernio ID | Account | Rationale |
+|---|---|---|---|
+| X/Twitter | `twitter` | acc_x_growthubai | Highest-signal developer community for agent tooling; lives for technical threads |
+| LinkedIn | `linkedin` | acc_li_GrowthubPage | Hiring signal + thought leadership; partners and enterprise-adjacent audience |
+| Bluesky | `bluesky` | acc_bsky_growthub | Tech-fluent early adopters; text-first format fits our voice |
+| YouTube | `youtube` | acc_yt_GrowthubAI | Long-form CLI walkthroughs and shorts for each release |
+
+Max 5 platforms. Fifth (Instagram) deferred — team capacity insufficient for sustained visual production this cycle.
+
+---
+
+## Audience Profile
+
+### Primary
+
+| Attribute | Value |
+|---|---|
+| Age range | 25–45 |
+| Geography | North America + Europe, English-first |
+| Interests | AI agents, developer tools, automation, local-first infra |
+| Pain points | Agent orchestration sprawl, tool fatigue, SaaS lock-in |
+| Content preferences | Technical threads, CLI walkthroughs, architecture posts, build-in-public behind the scenes |
+
+### Secondary
+
+| Attribute | Value |
+|---|---|
+| Age range | 18–25 |
+| Platforms | X/Twitter, Bluesky, GitHub |
+| Interests | Open source, indie hacking, learning agent development |
+
+---
+
+## KPI Targets
+
+| KPI | Metric | Target | Timeline |
+|---|---|---|---|
+| Developer awareness | GitHub stars | +500 | By 2026-05-30 |
+| Community growth | X followers | +400 | Rolling through Q2 |
+| Thought leadership | LinkedIn impressions | 25,000 / month | May 2026 |
+| Open-source adoption | CLI downloads (npm) | +2,000 / month | May 2026 |
+
+---
+
+## Content Theme Pillars
+
+| Pillar | Description | % of calendar | Primary platforms |
+|---|---|---|---|
+| Product Builds | Behind-the-scenes of shipping kits and CLI features | 35% | X, LinkedIn, YouTube |
+| Developer Tutorials | How to use kits, commands, workflows end-to-end | 30% | X, Bluesky, YouTube |
+| Open Source | OSS culture, contributions, partner projects | 20% | X, Bluesky |
+| Community | User projects, shoutouts, Q&A, polls | 15% | X, LinkedIn |
+
+---
+
+## Brand Voice Summary
+
+| Attribute | Spec |
+|---|---|
+| Tone | Direct, technically credible, approachable. Explains without condescension. Ships without bragging. |
+| Words to use | "build", "ship", "run", "local", "open", "agent", "workflow", "kit", "workspace" |
+| Words to avoid | "disruptive", "AI-powered", "revolutionary", "hack" |
+| Emoji rule | 0–1 on LinkedIn, 0–2 on X, none on Bluesky |
+| CTA style | Action verbs with immediate value: "Try it now", "Clone and run", "Read the docs", "Star on GitHub" |
+
+---
+
+## Execution Notes
+
+- Caption variants: 3 per post (A direct, B narrative, C question)
+- Every `POST /api/v1/posts` call uses `Idempotency-Key = clientPostId` (shape `growthub-YYYYMMDD-NNN`)
+- `dryRun` is `false` — api-live mode, profile `prof_GRO_primary`
+- Manifest submission order: media uploads → posts → recurring `weekly-build-log` queue creation
+- YouTube long-form videos scheduled via Zernio with premieres disabled; Shorts scheduled via queue

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

@@ -0,0 +1,146 @@
+# 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.
+
+Unlike the Postiz kit (self-hosted fork), Zernio is a hosted SaaS: there is no docker / fork to clone. The kit works against the hosted `https://zernio.com/api/v1` endpoint using an API key.
+
+---
+
+## Folder Structure
+
+```
+growthub-zernio-social-v1/
+  kit.json                              ← Kit manifest (schemaVersion: 2)
+  QUICKSTART.md                         ← Setup guide
+  .env.example                          ← 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
+    postiz-ui-shell-integration.md      ← Optional — pair with the Postiz UI kit
+    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-postiz-social-v1` | studio | Social media via self-hosted Postiz |
+| `growthub-zernio-social-v1` | studio | Social media via hosted Zernio REST API (this kit) |
+
+### Recommended Pairing — Social Media Stack
+
+`growthub-postiz-social-v1` (UI shell) + `growthub-zernio-social-v1` (engine) form a first-class paired environment. Postiz provides calendar, compose, analytics shell, and team workspace. Zernio provides the 14-platform transport, queues, media, inbox, and analytics against a single bearer-token REST API — no per-platform OAuth dance, no regional secrets sprayed across the kit.
+
+See `docs/postiz-ui-shell-integration.md` in this kit for the 7-module bridge recipe.

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

@@ -0,0 +1,120 @@
+# 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 4 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/kit.json

@@ -0,0 +1,104 @@
+{
+  "schemaVersion": 2,
+  "kit": {
+    "id": "growthub-zernio-social-v1",
+    "version": "1.0.0",
+    "name": "Growthub Agent Worker Kit — 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",
+    "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/postiz-ui-shell-integration.md",
+    "docs/local-adapters.md",
+    "growthub-meta/README.md",
+    "growthub-meta/kit-standard.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",
+      "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",
+      "templates",
+      "docs",
+      "growthub-meta"
+    ]
+  },
+  "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"
+  }
+}

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

@@ -0,0 +1,63 @@
+# 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.