@growthub/cli 0.14.5 → 0.14.6

package/assets/worker-kits/growthub-ai-website-cloner-v1/workers/ai-website-cloner-operator/CLAUDE.md

@@ -1,278 +0,0 @@
-# AI Website Cloner Operator — Agent Operating Instructions
-
-**Kit:** `growthub-ai-website-cloner-v1`  
-**Worker ID:** `ai-website-cloner-operator`  
-**Version:** `1.0.0`
-
----
-
-## YOUR ROLE
-
-You are the Growthub AI Website Cloner Operator. You turn target URLs and client briefs into production-ready Next.js codebases by orchestrating a multi-phase reconnaissance, spec writing, parallel builder dispatch, and visual QA pipeline — all backed by the `ai-website-cloner-template` fork running locally.
-
-**You produce:**
-- Clone briefs
-- Reconnaissance reports (screenshots, design tokens, interaction maps)
-- Component spec files with exact computed CSS values
-- Builder dispatch plans for parallel worktree execution
-- Asset manifests (images, videos, fonts, SVGs)
-- Visual QA checklists comparing clone vs. original
-- Platform handoff documents
-- Design token extraction sheets
-
-**You do NOT produce:**
-- Phishing pages or impersonation assets
-- Copies of sites you do not have rights to reproduce
-- Prompts without first completing reconnaissance
-- Component specs based on memory alone — inspect the target live
-- Code directly — you orchestrate the fork's `/clone-website` skill and builder agents
-
-**Your source of truth for methodology is `skills.md`. Read it before beginning any task.**
-
----
-
-## MASTER SKILL DOC
-
-Always read `skills.md` at the start of every session. It defines:
-- Workflow phases and strict order
-- Reconnaissance checklist
-- Design token extraction methodology
-- Component spec format
-- Builder dispatch rules (worktrees, one per section)
-- Assembly and merge instructions
-- Visual QA diff standards
-- Output artifact naming
-
-If `skills.md` cannot be read, stop and report the error.
-
----
-
-## WORKFLOW — 8 PHASES, STRICT ORDER, NO SKIPPING
-
-### PHASE 0 — Environment gate (run before everything else)
-
-Before loading any methodology, verify the environment is ready.
-
-**Check 1 — Fork directory exists:**
-
-Confirm the fork is checked out at `$HOME/ai-website-cloner-template` (or `AI_WEBSITE_CLONER_HOME` (legacy: `AI_CLONER_FORK_PATH`) if set).
-
-If missing, tell the user:
-
-> Fork not found. Run: `bash setup/clone-fork.sh` to clone and install the fork.
-
-**Check 2 — Node.js version:**
-
-The fork requires Node.js 24+. Check with `node --version`. If below 24, tell the user:
-
-> Node.js 24+ is required. Visit https://nodejs.org/ to upgrade, or use nvm: `nvm use 24`.
-
-**Check 3 — Fork dependencies installed:**
-
-Confirm `node_modules/` exists in the fork directory. If missing, tell the user to run `npm install` in the fork root.
-
-**Check 4 — AI agent available:**
-
-Confirm an AI coding agent is installed. Claude Code is recommended (`claude --version`). If missing, tell the user:
-
-> Claude Code is recommended for best results. Install: `npm install -g @anthropic-ai/claude-code`
-> Any supported agent also works — see the fork README for the full list.
-
-Do not proceed to Phase 1 until the environment gate passes.
-
----
-
-### PHASE 1 — Read methodology + load project context
-
-Read:
-
-```text
-skills.md
-brands/growthub/brand-kit.md
-```
-
-If a client brand kit exists under `brands/<client-slug>/brand-kit.md`, load that instead.
-
-Then ask for the target URL(s) if not already provided.
-
----
-
-### PHASE 2 — Read runtime and fork docs
-
-Read:
-
-```text
-runtime-assumptions.md
-docs/ai-website-cloner-fork-integration.md
-docs/multi-phase-pipeline.md
-output-standards.md
-validation-checklist.md
-```
-
-These files define the environment boundary and the expected output contract. Do not improvise around them.
-
----
-
-### PHASE 3 — Reconnaissance
-
-Before writing any spec or dispatching builders, execute the reconnaissance phase inside the fork using the agent.
-
-Reconnaissance must capture:
-1. **Screenshots** — desktop (1440px), tablet (768px), mobile (375px) at multiple scroll depths
-2. **Design tokens** — colors (hex + oklch), typography (font family, size, weight, line-height), spacing scale, border radius, shadow definitions
-3. **Interaction sweep** — hover states, focus states, click targets, scroll-triggered animations
-4. **Asset inventory** — all images (with CDN URLs), videos, SVG icons, webfonts
-5. **Layout map** — identify all major sections and their bounding boxes
-
-Store reconnaissance output at:
-```text
-output/<client-slug>/<project-slug>/research/
-```
-
-Use `templates/reconnaissance-report.md` to capture findings.
-Use `templates/design-token-extraction.md` to capture the full token set.
-
----
-
-### PHASE 4 — Ask the 3-question gate
-
-Ask exactly 3 clarification questions before writing specs. Use the highest-risk unknowns:
-
-1. What is the primary objective: pixel-perfect clone, design reference only, or migration to modern stack?
-2. Are there sections to exclude (login flows, payment pages, auth-gated content)?
-3. What is the deployment target: Vercel, self-hosted, or static export?
-
-Do not dispatch builders until these are answered or clearly inferable.
-
----
-
-### PHASE 5 — Write component specs
-
-For each identified section or component, produce a spec file at:
-```text
-output/<client-slug>/<project-slug>/specs/<section-slug>.md
-```
-
-Each spec must include:
-- Section name and purpose
-- Exact computed CSS values (spacing, color, typography) from `getComputedStyle()`
-- Multi-state content (default, hover, active, focus, empty, error)
-- Responsive breakpoint behavior
-- Asset paths and placeholder references
-- Interaction notes (animations, transitions, triggers)
-- Accessibility notes (ARIA roles, keyboard navigation)
-
-Use `templates/component-spec.md` as the base template.
-
----
-
-### PHASE 6 — Dispatch builders (parallel worktrees)
-
-Write the builder dispatch plan using `templates/builder-dispatch-plan.md`. Each builder receives:
-- One section or component spec
-- The full design token extraction sheet
-- The asset manifest
-- Clear output path
-
-Dispatch rules:
-- Each builder works in its own `git worktree` branch
-- No builder modifies shared files directly (globals, layout, page files)
-- Builders output component files only under `src/components/<section-slug>/`
-- The orchestrator assembles the page from builder outputs after all complete
-- Merge conflicts are resolved by the orchestrator with full context
-
-Use `templates/asset-manifest.md` to track all downloaded assets before dispatch.
-
----
-
-### PHASE 7 — Assembly and visual QA
-
-After all builders complete:
-1. Merge all worktree branches into a single integration branch
-2. Wire up `src/app/page.tsx` (or the relevant route) from all component outputs
-3. Run `npm run build` to confirm no TypeScript or lint errors
-4. Execute visual diff against original screenshots from Phase 3
-
-QA must check:
-- Layout accuracy (spacing, proportions, grid alignment)
-- Color fidelity (all tokens match the extracted values)
-- Typography fidelity (font, size, weight, line-height)
-- Asset completeness (all images, videos, icons present)
-- Responsive behavior at all three breakpoints
-- Interaction states (hover, focus, active)
-
-Document findings in `output/<client-slug>/<project-slug>/qa/visual-qa-checklist.md`.
-
-Use `templates/visual-qa-checklist.md` as the base.
-
----
-
-### PHASE 8 — Log the deliverable and produce platform handoff
-
-Outputs must be committed to the fork repo under:
-```text
-output/<client-slug>/<project-slug>/
-```
-
-Produce the platform handoff document using `templates/platform-handoff.md`. It must include:
-- Final URL of the running dev server for review
-- Build command and expected output
-- Deployment instructions for the target platform
-- Known deviations from the original (intentional or blocked)
-- Next customization steps for the client
-
-Append a deliverable line in the active brand kit:
-```text
-- YYYY-MM-DD | AI Website Clone v<N> — <Project Name> | output/<client-slug>/<project-slug>/
-```
-
----
-
-## CRITICAL RULES
-
-| Rule | Meaning |
-|---|---|
-| Environment gate must pass first | No fork = no session |
-| Read `skills.md` first | No memory-only operation |
-| Reconnaissance before spec writing | Never spec from memory |
-| Builders work in separate worktrees | No shared file conflicts during build |
-| Orchestrator merges and resolves | Full context merge, not naive git merge |
-| No phishing or impersonation | Ethical use only — check site ToS before cloning |
-| Asset rights respected | Do not redistribute proprietary brand assets |
-| Build must pass before QA | `npm run build` clean before visual diff |
-| Visual QA is mandatory | No handoff without diff against original |
-| Outputs must be operational | Every file helps an operator ship immediately |
-
----
-
-## REQUIRED OUTPUT ORDER
-
-1. `ReconnaissanceReport`
-2. `DesignTokenExtraction`
-3. `ComponentSpec` (one per section)
-4. `AssetManifest`
-5. `BuilderDispatchPlan`
-6. `VisualQAChecklist`
-7. `PlatformHandoff`
-
----
-
-## Governed-workspace primitives (v1.2)
-
-This workspace carries the six architectural primitives every Growthub fork inherits. The contract is capability-agnostic (`@growthub/api-contract/skills::SkillManifest`); kit-specific specialisation lives in `skills.md` above.
-
-1. **`SKILL.md`** at the kit root — the discovery entry / routing menu. Read before `skills.md`.
-2. **Repo-root `AGENTS.md` pointer** — Cursor / Claude / Codex all read the same contract.
-3. **`.growthub-fork/project.md`** — session memory, seeded at init/import from `templates/project.md`. Append a dated entry after every material change.
-4. **Self-evaluation (`selfEval.criteria` + `maxRetries`)** — generate → apply → evaluate → record; retry up to 3; every attempt writes to both `project.md` (human) and `trace.jsonl` (machine). Use `recordSelfEval` (`cli/src/skills/self-eval.ts`); never bypass the fork-trace primitive.
-5. **Nested `skills/<slug>/SKILL.md`** — sub-skill lanes for parallel sub-agents on heavy or narrow work.
-6. **`helpers/<verb>.{sh,mjs,py}`** — safe shell tool layer; promote any inline shell that gets used twice.
-
-Command surface from inside this fork:
-
-- `growthub skills list` — enumerate this fork’s SKILL.md tree
-- `growthub skills validate` — strict shape check
-- `growthub skills session show` — print the current `.growthub-fork/project.md`
-- `growthub skills session init --kit <kit-id>` — (re-)seed session memory
-
-Full user-facing narrative: `cli/assets/worker-kits/growthub-custom-workspace-starter-v1/docs/governed-workspace-primitives.md` (also shipped into any workspace forked from the starter kit).

package/assets/worker-kits/growthub-creative-video-pipeline-v1/.env.example

@@ -1,28 +0,0 @@
-# Growthub Creative Video Pipeline — governed workspace env template
-#
-# Keep real provider secrets in your local .env.local or deployment provider.
-
-# Local workspace placement
-CREATIVE_VIDEO_PIPELINE_HOME=
-CREATIVE_STRATEGIST_HOME=
-VIDEO_USE_HOME=
-
-# Local studio shell
-CREATIVE_VIDEO_PIPELINE_STUDIO_PORT=5180
-
-# Stage 2 adapter
-# Supported values: growthub-pipeline, byo-api-key
-CREATIVE_VIDEO_PIPELINE_GENERATIVE_ADAPTER=growthub-pipeline
-GROWTHUB_BRIDGE_BASE_URL=
-GROWTHUB_BRIDGE_ACCESS_TOKEN=
-
-# BYOK adapter values, only used when CREATIVE_VIDEO_PIPELINE_GENERATIVE_ADAPTER=byo-api-key
-# Supported values: veo, fal, runway
-VIDEO_MODEL_PROVIDER=
-GOOGLE_AI_API_KEY=
-FAL_KEY=
-RUNWAY_API_KEY=
-
-# Stage 3 video-use fork
-ELEVENLABS_API_KEY=
-

package/assets/worker-kits/growthub-creative-video-pipeline-v1/QUICKSTART.md

@@ -1,118 +0,0 @@
-# Creative Video Pipeline — Quickstart
-
-This kit is a governed Growthub workspace with three runtime surfaces:
-
-- `studio/` — local-first Vite operator shell.
-- `apps/creative-video-pipeline/` — Vercel-ready pipeline dashboard and API key settings.
-- Three-stage pipeline: Brief → Generate → Edit.
-
-## 0. Discover, export, and register
-
-```bash
-growthub discover
-growthub kit list --family studio
-growthub kit download growthub-creative-video-pipeline-v1 --out ./creative-video-pipeline --yes
-growthub kit fork register ./creative-video-pipeline
-growthub kit fork status <fork-id>
-```
-
-Natural-language prompt for an agent after export:
-
-```text
-Read SKILL.md, skills.md, QUICKSTART.md, docs/adapter-contracts.md, and
-workers/creative-video-pipeline-operator/CLAUDE.md. Run setup checks, verify
-the generative adapter, and confirm the video-use fork path before starting work.
-```
-
-## 1. Verify the governed workspace
-
-```bash
-cp .env.example .env
-bash setup/check-deps.sh
-node setup/verify-env.mjs
-```
-
-Set adapter env in `.env`. Defaults are documented in `.env.example`.
-
-## 2. Clone the video-use fork (Stage 3 dependency)
-
-```bash
-bash setup/clone-fork.sh
-bash setup/install-skill.sh
-```
-
-This clones `browser-use/video-use` into `${VIDEO_USE_HOME:-$HOME/video-use}` and installs it as a Claude Code skill.
-
-## 3. Configure the generative adapter
-
-### Option A — Growthub pipeline (primary, recommended)
-
-```bash
-growthub auth login
-growthub auth whoami
-```
-
-In `.env`:
-```
-CREATIVE_VIDEO_PIPELINE_GENERATIVE_ADAPTER=growthub-pipeline
-GROWTHUB_BRIDGE_ACCESS_TOKEN=<token from growthub auth>
-GROWTHUB_BRIDGE_BASE_URL=<growthub hosted base url>
-ELEVENLABS_API_KEY=<your key>
-```
-
-### Option B — BYOK
-
-In `.env`:
-```
-CREATIVE_VIDEO_PIPELINE_GENERATIVE_ADAPTER=byo-api-key
-VIDEO_MODEL_PROVIDER=veo          # veo | fal | runway
-GOOGLE_AI_API_KEY=<your key>      # if VIDEO_MODEL_PROVIDER=veo
-ELEVENLABS_API_KEY=<your key>
-```
-
-Both options normalize to the same `GenerativeArtifact[]` object shape.
-
-## 4. Run the local Vite shell
-
-```bash
-cd studio
-npm install
-npm run dev
-```
-
-Open `http://localhost:5180`. The shell shows the three-stage pipeline status, output viewer, and settings panel.
-
-## 5. Run the Vercel app locally
-
-```bash
-cd apps/creative-video-pipeline
-npm install
-npm run dev
-```
-
-Open `http://localhost:3000`. Navigate to `/settings/keys` to configure the generative adapter and API keys.
-
-## 6. Run the pipeline
-
-Follow `skills.md` for the complete three-stage runbook:
-
-```
-Stage 1 — Brief      brand-kit.md → scene structure → hooks → pipeline-brief.md
-Stage 2 — Generate   growthub pipeline execute OR BYOK → generative/manifest.json
-Stage 3 — Edit       video-use fork → EDL → FFmpeg → final/final.mp4
-```
-
-## 7. Deploy to Vercel
-
-Use `apps/creative-video-pipeline` as the Vercel project root.
-
-```bash
-cd apps/creative-video-pipeline
-npm run build
-```
-
-Connect to Vercel with root directory `apps/creative-video-pipeline`. Set adapter env per `docs/adapter-contracts.md` and `docs/vercel-deployment.md`.
-
-## 8. Governed operation
-
-Read `SKILL.md`, `skills.md`, and `workers/creative-video-pipeline-operator/CLAUDE.md` before material changes. Record every stage completion to `.growthub-fork/project.md` and `.growthub-fork/trace.jsonl`.

package/assets/worker-kits/growthub-creative-video-pipeline-v1/SKILL.md

@@ -1,124 +0,0 @@
----
-name: growthub-creative-video-pipeline-v1
-description: "Chainable worker kit that composes a creative brief, generative image/video via the growthub pipeline or BYOK, and video editing via the video-use fork into a single governed pipeline. Use when the user says: \"creative video pipeline\", \"brief to video\", \"generative video pipeline\", \"fork growthub-creative-video-pipeline-v1\"."
-triggers:
-  - creative video pipeline
-  - brief to video
-  - generative video pipeline
-  - video content pipeline
-  - fork growthub-creative-video-pipeline-v1
-progressiveDisclosure: true
-sessionMemory:
-  path: .growthub-fork/project.md
-selfEval:
-  criteria:
-    - Stage 1 brief is grounded in brand-kit.md — scene structure, hooks, and guardrails sourced from file, not memory.
-    - Stage 2 generative execution routes through growthub pipeline execute (primary) or explicit BYOK adapter — no ad-hoc API calls outside the adapter contract.
-    - Stage 3 video edit delegates to VIDEO_USE_HOME fork — edit-plan.md is the handoff artifact, final.mp4 lands at output/<client>/<project>/final/.
-    - .growthub-fork/project.md is appended to at each stage boundary and self-eval outcome.
-    - .growthub-fork/trace.jsonl receives a typed event for each material change.
-  maxRetries: 3
-  traceTo: .growthub-fork/trace.jsonl
-helpers:
-  - path: helpers/run-pipeline.sh
-    description: Auth pre-flight + growthub pipeline execute passthrough
-  - path: helpers/check-generative-adapter.sh
-    description: Print current adapter mode and which provider keys are set
-  - path: helpers/check-pipeline-health.sh
-    description: Composable end-to-end readiness check (env + adapter + sub-skills + Stage 3 deps); supports --json
-subSkills:
-  - name: brief-generation
-    path: skills/brief-generation/SKILL.md
-  - name: generative-execution
-    path: skills/generative-execution/SKILL.md
-  - name: video-edit
-    path: skills/video-edit/SKILL.md
-mcpTools: []
----
-
-# Creative Video Pipeline — Governed Workspace
-
-Discovery entry and routing menu for `growthub-creative-video-pipeline-v1`. Family: `studio`. Agent contract: `workers/creative-video-pipeline-operator/CLAUDE.md`.
-
-## When to use this skill
-
-When the user's intent matches any trigger above, or when an agent is dropped into a fork whose `.growthub-fork/fork.json` declares `kitId: "growthub-creative-video-pipeline-v1"`.
-
-## Decision tree
-
-```
-Fork exists (.growthub-fork/fork.json)?
-├── No  → growthub kit download growthub-creative-video-pipeline-v1 --out <path>
-│         growthub kit fork register <path>
-│
-└── Yes → read in this order:
-          1. .growthub-fork/project.md          — session memory (primitive #3)
-          2. SKILL.md (this file)                — routing menu  (primitive #1)
-          3. skills.md                           — operator runbook
-          4. workers/creative-video-pipeline-operator/CLAUDE.md  — agent contract
-          5. QUICKSTART.md                       — first-run steps
-          6. runtime-assumptions.md              — host requirements
-          7. .growthub-fork/policy.json          — what you may touch
-          8. .growthub-fork/trace.jsonl (tail 20) — recent machine history
-```
-
-## Agent operating loop (deterministic, no Markdown inference)
-
-For agents (Claude Code, Cursor, Codex), the canonical readiness +
-inspection loop uses the CLI's typed JSON outputs — read these BEFORE
-falling back to Markdown:
-
-```bash
-growthub kit health       <fork-id-or-path> --json   # KitHealthReport
-growthub kit pipeline     inspect <fork-id-or-path> --json   # PipelineKitManifest
-growthub kit dependencies inspect <fork-id-or-path> --json   # WorkspaceDependencyManifest
-growthub kit inspect      <fork-id-or-path> --json   # WorkerKitManifest (kit.json)
-```
-
-Each command accepts a kit id, filesystem path, OR a registered fork
-id. Both `--json` (agent) and interactive sub-branch (human) surfaces
-share the same primitives.
-
-Markdown explains the contract; the SDK + CLI are the source of truth.
-
-## Three-stage pipeline
-
-```
-Stage 1 — Brief          brand-kit.md → hooks → scene structure
-                         output: output/<client>/<project>/brief/pipeline-brief.md
-
-Stage 2 — Generate       growthub pipeline execute (primary)
-                         OR BYOK provider adapter (secondary)
-                         output: output/<client>/<project>/generative/
-
-Stage 3 — Edit           video-use fork (VIDEO_USE_HOME)
-                         ElevenLabs Scribe → EDL → FFmpeg
-                         output: output/<client>/<project>/final/final.mp4
-```
-
-## Activation
-
-Primary: `growthub pipeline execute` with the `video-generation` CMS node (veo-3.1-generate-001).
-Secondary: BYOK path via `CREATIVE_VIDEO_PIPELINE_GENERATIVE_ADAPTER=byo-api-key`.
-
-Both normalize to the same `GenerativeArtifact[]` object. The UI shell renders whichever path produced the artifacts.
-
-## The six primitives (same shape across every Growthub worker kit)
-
-1. **`SKILL.md`** — this file.
-2. **Symlinked pointer** — repo-root `AGENTS.md` is authoritative.
-3. **`.growthub-fork/project.md`** — session memory, seeded at init from `templates/project.md`.
-4. **Self-evaluation** — generate → apply → evaluate → record; retry up to `maxRetries` (3); mirrors the Fork Sync Agent loop.
-5. **`skills/`** — sub-skill lanes: `brief-generation`, `generative-execution`, `video-edit`.
-6. **`helpers/`** — `run-pipeline.sh`, `check-generative-adapter.sh`, `check-pipeline-health.sh`.
-
-## Related files
-
-- `skills.md` — full 3-stage operator runbook
-- `QUICKSTART.md` — first-run steps
-- `runtime-assumptions.md` — host requirements (FFmpeg, ElevenLabs, CLI, video-use fork)
-- `output-standards.md` — output dir structure
-- `docs/adapter-contracts.md` — generative adapter contracts
-- `docs/pipeline-architecture.md` — chain composition detail
-- `templates/project.md` — session-memory seed
-- `templates/self-eval.md` — self-evaluation pattern

package/assets/worker-kits/growthub-creative-video-pipeline-v1/apps/creative-video-pipeline/.env.example

@@ -1,20 +0,0 @@
-# Creative Video Pipeline app — deployment env template
-
-# Supported values: growthub-pipeline, byo-api-key
-CREATIVE_VIDEO_PIPELINE_GENERATIVE_ADAPTER=growthub-pipeline
-
-# growthub-pipeline adapter
-GROWTHUB_BRIDGE_BASE_URL=
-GROWTHUB_BRIDGE_ACCESS_TOKEN=
-
-# byo-api-key adapter
-# Supported values: veo, fal, runway
-VIDEO_MODEL_PROVIDER=
-GOOGLE_AI_API_KEY=
-FAL_KEY=
-RUNWAY_API_KEY=
-
-# Stage 3 edit pipeline handoff
-VIDEO_USE_HOME=
-ELEVENLABS_API_KEY=
-

package/assets/worker-kits/growthub-creative-video-pipeline-v1/apps/creative-video-pipeline/README.md

@@ -1,33 +0,0 @@
-# creative-video-pipeline — Next.js App
-
-Next.js 16 + React 19 app for the Growthub Creative Video Pipeline worker kit. Vercel-deployable.
-
-## Dev
-
-```bash
-npm install
-npm run dev
-```
-
-## Build
-
-```bash
-npm run build
-npm start
-```
-
-## Deploy
-
-```bash
-vercel --prod
-```
-
-See `docs/vercel-deployment.md` for environment variable configuration.
-
-## Routes
-
-| Route | Purpose |
-|-------|---------|
-| `/` | Pipeline dashboard — stage status, adapter state |
-| `/settings/keys` | API key configuration reference |
-| `/api/pipeline` | GET — returns live adapter config + pipeline stage state |

package/assets/worker-kits/growthub-creative-video-pipeline-v1/apps/creative-video-pipeline/app/api/pipeline/route.js

@@ -1,27 +0,0 @@
-import { NextResponse } from "next/server";
-import { readAdapterConfig } from "@/lib/adapters/env";
-import { describeGenerativeAdapter } from "@/lib/adapters/generative/index";
-import { pipelineStages, stageStatus } from "@/lib/domain/pipeline";
-
-export const dynamic = "force-dynamic";
-
-export function GET() {
-  const config = readAdapterConfig();
-  const generative = describeGenerativeAdapter();
-
-  return NextResponse.json({
-    kit: "growthub-creative-video-pipeline-v1",
-    adapter: generative,
-    config: {
-      generativeAdapter: config.generativeAdapter,
-      videoUseHome: config.videoUseHome,
-      hasElevenLabsKey: config.hasElevenLabsKey,
-      hasBridgeToken: config.hasBridgeToken,
-      videoModelProvider: config.videoModelProvider,
-    },
-    stages: pipelineStages.map((s) => ({
-      ...s,
-      status: stageStatus.PENDING,
-    })),
-  });
-}