@officexapp/vidfarm-devcli 0.21.54 → 0.21.55

package/.agents/skills/vidfarm/SKILL.md

@@ -439,6 +439,8 @@ Vidfarm keeps a small shelf of **experimental prompts**: complete, standalone me
 
 Why they exist: the prompts you find on the `/discover` pages are tuned to **one template's format**. These are deliberately **generalized** — the method, not the template — so they transfer to whatever you are building. The live index is `https://vidfarm.cc/experimental` (always current); today it holds:
 
+**Two ways to reach any of them.** Fetch the URL, or read it **by name, offline** — every one of these ships inside the devcli package: `vidfarm harness list` prints this same shelf under *Format harnesses*, `vidfarm harness show <name>` prints one (`--dna <strand>` for a single strand), and `vidfarm qa ./work --harness <name>` grades a build against it. The name is the URL slug, and underscores resolve too — `meme_recaption` and `meme-recaption` are the same harness in both places. Prefer the CLI when you already have it: no fetch, no 402, and it stacks with a base (`--harness google-news-to-video --harness short-form`).
+
 | Prompt | What it does |
 |---|---|
 | `https://vidfarm.cc/experimental/unique-product-explainers.md` | N customer URLs → N product-introduction videos that do not look like each other. Differentiation as an input, frame-level review, measured verification |
@@ -447,6 +449,7 @@ Why they exist: the prompts you find on the `/discover` pages are tuned to **one
 | `https://vidfarm.cc/experimental/ugc-reaction-greenscreen.md` | Sell an app with three streams cut against each other: `ugc-reaction` raws, a Display Greenscreen device whose screen carries the customer's real demo, and the demo itself. One actor across every beat via `actor_<uuid>`, a per-frame tracked screen insert, captions inside the platform-chrome-safe core, and two exports from one render (voiceover-only to publish, voiceover+music to review) |
 | `https://vidfarm.cc/experimental/sticker-slideshow-tips.md` | A tips **carousel** — the deliverable is N still slides, and the 3.0s-per-slide MP4 is only the playable preview. Die-cut cutouts on a paper page or a photo background, a literal "Tips for…" cover, the specificity ladder, one slide shilled from the middle and written so it survives deleting the brand name, four background modes, and a measured WCAG contrast gate on the exported PNGs |
 | `https://vidfarm.cc/experimental/wall-text-pov-ugc.md` | One unbroken ambient take + one static block of unplated type. No cuts, no voiceover, no subtitles, nothing animated. The retention engine is arithmetic — `duration = words / 8`, so one play lands the viewer at the **halfway mark**, committed and one pass from done — floored at 8s so a trending sound gets a real phrase of a track. The four speaker frames, MIRROR vs TURN, a density pass that treats padding as the fatal failure, casting the scene dark so the type needs no plate (measured), ping-ponging the plate for a seamless loop, and three gates. Runs at $0 |
+| `https://vidfarm.cc/experimental/animated-sticker-story.md` | A narrated **paper puppet theater** — one full-bleed parchment stage that never cuts, a cast of die-cut stickers, and every element moved by ONE paused GSAP timeline (MotionPathPlugin for walks; paths in absolute canvas coordinates, never `align:"self"`). The three-node rig, the seven moves (ENTER / WALK / CROWD / BEAT / STAMP / DRAW / CAMERA), buying SHEETS rather than stickers so one art class survives, generating art without shadows and adding one CSS drop-shadow, kinetic captions that animate **colour only** on whisper word timings, a two-pass build that MEASURES where the drawing is quietest before placing any type, a feathered paper wash that is not a plate, and the offer named once as a wordmark on the last beat. Desktop-only. ~$0.25 in `hybrid`, $0 in `minimize` |
 
 Fetch one as plain markdown and follow it end to end; do not skim it into a summary.
 

package/.agents/skills/vidfarm/harnesses/README.md

@@ -111,3 +111,29 @@ The `.harness/` directory a `vidfarm pull` writes is a different thing: machine-
 | `explainer` | Faceless educational video: one claim, invented visuals |
 | `product-demo` | Real product doing a real thing — the highest slop-risk format in the catalog |
 | `product-explainer` | Introducing a product a stranger has never heard of, with no usable screen footage. The plain-English line, the simple sticker-led open, per-client differentiation |
+
+## Format harnesses — the second shelf
+
+`vidfarm harness list` prints the bases above **and** the format harnesses: complete contracts for
+ONE format, published at `https://vidfarm.cc/experimental` and shipped inside the CLI package under
+the same name as their URL slug. A base is a starting point you edit; a format harness is a method
+you follow. Read one **before** you build that format, and stack it on a base.
+
+| Name | For |
+|---|---|
+| `meme-recaption` | One borrowed meme clip, one new caption aimed at the offer's problem space |
+| `wall-text-pov-ugc` | One unbroken ambient take + one static block of unplated type. `duration = words / 8` |
+| `ugc-reaction-greenscreen` | Reaction cutaways + a keyed device carrying the customer's real app demo |
+| `sticker-slideshow-tips` | A tips carousel — N still slides at 3.0s; the slides are the deliverable |
+| `animated-sticker-story` | A narrated paper puppet theater on one parchment stage, one GSAP timeline |
+| `google-news-to-video` | Timely newsjack — news-search finds the STORY, video-search the VISUALS |
+| `unique-product-explainers` | N customer URLs → N videos that do not converge. Differentiation as an input |
+
+```bash
+vidfarm harness list                                  # both shelves
+vidfarm harness show wall-text-pov-ugc                # the whole contract, no fetch
+vidfarm qa ./work --harness wall-text-pov-ugc --harness short-form   # they STACK
+```
+
+Underscores resolve too (`meme_recaption` = `meme-recaption`), on the CLI and at the URL. The web
+index is the source of truth for what exists; `vidfarm harness list` is the same shelf, offline.

package/.agents/skills/vidfarm/recipes/bulk-scripting-with-a-harness.md

@@ -26,7 +26,8 @@ Two ways in, depending on where the format came from:
 
 ```bash
 # (a) From a bundled base — when the format is one you're defining
-vidfarm harness list                                    # short-form | hooks | ugc-testimonial | explainer | product-demo | product-explainer
+vidfarm harness list                                    # bases: short-form | hooks | ugc-testimonial | explainer | product-demo | product-explainer
+                                                        # + format harnesses: meme-recaption | wall-text-pov-ugc | … (the /experimental shelf, offline)
 vidfarm harness init hooks --out ./work/HARNESS.md
 
 # (b) From the template you're batching — when the format is one you're REPLICATING

package/.agents/skills/vidfarm/references/automation-and-local-dev.md

@@ -62,7 +62,7 @@ A director who says "make me a video about X" usually wants the first. A directo
 | "give me the harness for this template_id" | `vidfarm harness derive <templateId\|forkId>` — the **decomposition**, as a harness |
 
 ```bash
-vidfarm harness list                                        # the bundled starting points
+vidfarm harness list                                        # bases to edit + the format harnesses (vidfarm.cc/experimental, offline)
 vidfarm harness init short-form --out ./work/HARNESS.md     # copy, then EDIT it
 vidfarm harness derive <forkId> --out ./work/HARNESS.md     # a decomposed template → a harness
 vidfarm harness show ./work/HARNESS.md --dna visual         # ONE strand, not the whole doc
@@ -84,7 +84,7 @@ vidfarm qa ./work --harness hooks --harness ./brand/HOUSE.md # built-in + your o
 
 > Don't confuse `HARNESS.md` with the `.harness/` directory `vidfarm pull` writes. That directory is machine-generated context (`context.json`, `agent-guide.md`), regenerated on every pull — never hand-edit it. `HARNESS.md` is the one the director owns.
 
-Bundled bases (`vidfarm harness list`, files under `.agents/skills/vidfarm/harnesses/`): **`short-form`** (the default — the four charges hook/loop/payoff/bait + the standalone rule), **`hooks`** (hook-variant batches: chunk-1 legibility, the unguessable test, the anti-patterns that only show up at volume), **`ugc-testimonial`**, **`explainer`**, **`product-demo`**, **`product-explainer`** (introducing a brand nobody has heard of, with no usable screen footage: the plain-English line by t=5s, the ≤3-text-run sticker-led open, VO + music bed, and the assignment method that stops N client videos converging). Each is a *starting point to edit*, never a house style to conform to — the parts that matter most are the parts the director adds. A harness can also be any file anywhere: `--harness ./campaigns/q3/RULES.md` is fully supported, and `VIDFARM_HARNESS=./work/HARNESS.md` sets a default for a whole run.
+`vidfarm harness list` prints **two shelves**. The second one is the format harnesses — the `https://vidfarm.cc/experimental` shelf, shipped in the package so `vidfarm harness show meme-recaption` works with no fetch. Those are complete contracts for ONE format: read one before you build that format, and stack it on a base (`--harness wall-text-pov-ugc --harness short-form`). The first shelf is the bundled bases (files under `.agents/skills/vidfarm/harnesses/`): **`short-form`** (the default — the four charges hook/loop/payoff/bait + the standalone rule), **`hooks`** (hook-variant batches: chunk-1 legibility, the unguessable test, the anti-patterns that only show up at volume), **`ugc-testimonial`**, **`explainer`**, **`product-demo`**, **`product-explainer`** (introducing a brand nobody has heard of, with no usable screen footage: the plain-English line by t=5s, the ≤3-text-run sticker-led open, VO + music bed, and the assignment method that stops N client videos converging). Each is a *starting point to edit*, never a house style to conform to — the parts that matter most are the parts the director adds. A harness can also be any file anywhere: `--harness ./campaigns/q3/RULES.md` is fully supported, and `VIDFARM_HARNESS=./work/HARNESS.md` sets a default for a whole run.
 
 **The format is two halves, and the split is deliberate:** a front-matter `checks:` block the CLI settles deterministically (duration, aspect, `hook_words_max`, `forbid_text`, `first_frame_text`, … — full key list in `harnesses/README.md`), and every `- [ ]` checkbox in the body, which comes back as a **review item for you to answer**. "Is the withheld answer one the viewer can't supply themselves?" is a judgment call; a linter claiming to settle it would be lying. **Answer the review items honestly in your report** — the CLI prints them precisely because it can't.
 

package/SKILL.director.md

@@ -439,6 +439,8 @@ Vidfarm keeps a small shelf of **experimental prompts**: complete, standalone me
 
 Why they exist: the prompts you find on the `/discover` pages are tuned to **one template's format**. These are deliberately **generalized** — the method, not the template — so they transfer to whatever you are building. The live index is `https://vidfarm.cc/experimental` (always current); today it holds:
 
+**Two ways to reach any of them.** Fetch the URL, or read it **by name, offline** — every one of these ships inside the devcli package: `vidfarm harness list` prints this same shelf under *Format harnesses*, `vidfarm harness show <name>` prints one (`--dna <strand>` for a single strand), and `vidfarm qa ./work --harness <name>` grades a build against it. The name is the URL slug, and underscores resolve too — `meme_recaption` and `meme-recaption` are the same harness in both places. Prefer the CLI when you already have it: no fetch, no 402, and it stacks with a base (`--harness google-news-to-video --harness short-form`).
+
 | Prompt | What it does |
 |---|---|
 | `https://vidfarm.cc/experimental/unique-product-explainers.md` | N customer URLs → N product-introduction videos that do not look like each other. Differentiation as an input, frame-level review, measured verification |
@@ -447,6 +449,7 @@ Why they exist: the prompts you find on the `/discover` pages are tuned to **one
 | `https://vidfarm.cc/experimental/ugc-reaction-greenscreen.md` | Sell an app with three streams cut against each other: `ugc-reaction` raws, a Display Greenscreen device whose screen carries the customer's real demo, and the demo itself. One actor across every beat via `actor_<uuid>`, a per-frame tracked screen insert, captions inside the platform-chrome-safe core, and two exports from one render (voiceover-only to publish, voiceover+music to review) |
 | `https://vidfarm.cc/experimental/sticker-slideshow-tips.md` | A tips **carousel** — the deliverable is N still slides, and the 3.0s-per-slide MP4 is only the playable preview. Die-cut cutouts on a paper page or a photo background, a literal "Tips for…" cover, the specificity ladder, one slide shilled from the middle and written so it survives deleting the brand name, four background modes, and a measured WCAG contrast gate on the exported PNGs |
 | `https://vidfarm.cc/experimental/wall-text-pov-ugc.md` | One unbroken ambient take + one static block of unplated type. No cuts, no voiceover, no subtitles, nothing animated. The retention engine is arithmetic — `duration = words / 8`, so one play lands the viewer at the **halfway mark**, committed and one pass from done — floored at 8s so a trending sound gets a real phrase of a track. The four speaker frames, MIRROR vs TURN, a density pass that treats padding as the fatal failure, casting the scene dark so the type needs no plate (measured), ping-ponging the plate for a seamless loop, and three gates. Runs at $0 |
+| `https://vidfarm.cc/experimental/animated-sticker-story.md` | A narrated **paper puppet theater** — one full-bleed parchment stage that never cuts, a cast of die-cut stickers, and every element moved by ONE paused GSAP timeline (MotionPathPlugin for walks; paths in absolute canvas coordinates, never `align:"self"`). The three-node rig, the seven moves (ENTER / WALK / CROWD / BEAT / STAMP / DRAW / CAMERA), buying SHEETS rather than stickers so one art class survives, generating art without shadows and adding one CSS drop-shadow, kinetic captions that animate **colour only** on whisper word timings, a two-pass build that MEASURES where the drawing is quietest before placing any type, a feathered paper wash that is not a plate, and the offer named once as a wordmark on the last beat. Desktop-only. ~$0.25 in `hybrid`, $0 in `minimize` |
 
 Fetch one as plain markdown and follow it end to end; do not skim it into a summary.
 
@@ -2907,7 +2910,7 @@ A director who says "make me a video about X" usually wants the first. A directo
 | "give me the harness for this template_id" | `vidfarm harness derive <templateId\|forkId>` — the **decomposition**, as a harness |
 
 ```bash
-vidfarm harness list                                        # the bundled starting points
+vidfarm harness list                                        # bases to edit + the format harnesses (vidfarm.cc/experimental, offline)
 vidfarm harness init short-form --out ./work/HARNESS.md     # copy, then EDIT it
 vidfarm harness derive <forkId> --out ./work/HARNESS.md     # a decomposed template → a harness
 vidfarm harness show ./work/HARNESS.md --dna visual         # ONE strand, not the whole doc
@@ -2929,7 +2932,7 @@ vidfarm qa ./work --harness hooks --harness ./brand/HOUSE.md # built-in + your o
 
 > Don't confuse `HARNESS.md` with the `.harness/` directory `vidfarm pull` writes. That directory is machine-generated context (`context.json`, `agent-guide.md`), regenerated on every pull — never hand-edit it. `HARNESS.md` is the one the director owns.
 
-Bundled bases (`vidfarm harness list`, files under `.agents/skills/vidfarm/harnesses/`): **`short-form`** (the default — the four charges hook/loop/payoff/bait + the standalone rule), **`hooks`** (hook-variant batches: chunk-1 legibility, the unguessable test, the anti-patterns that only show up at volume), **`ugc-testimonial`**, **`explainer`**, **`product-demo`**, **`product-explainer`** (introducing a brand nobody has heard of, with no usable screen footage: the plain-English line by t=5s, the ≤3-text-run sticker-led open, VO + music bed, and the assignment method that stops N client videos converging). Each is a *starting point to edit*, never a house style to conform to — the parts that matter most are the parts the director adds. A harness can also be any file anywhere: `--harness ./campaigns/q3/RULES.md` is fully supported, and `VIDFARM_HARNESS=./work/HARNESS.md` sets a default for a whole run.
+`vidfarm harness list` prints **two shelves**. The second one is the format harnesses — the `https://vidfarm.cc/experimental` shelf, shipped in the package so `vidfarm harness show meme-recaption` works with no fetch. Those are complete contracts for ONE format: read one before you build that format, and stack it on a base (`--harness wall-text-pov-ugc --harness short-form`). The first shelf is the bundled bases (files under `.agents/skills/vidfarm/harnesses/`): **`short-form`** (the default — the four charges hook/loop/payoff/bait + the standalone rule), **`hooks`** (hook-variant batches: chunk-1 legibility, the unguessable test, the anti-patterns that only show up at volume), **`ugc-testimonial`**, **`explainer`**, **`product-demo`**, **`product-explainer`** (introducing a brand nobody has heard of, with no usable screen footage: the plain-English line by t=5s, the ≤3-text-run sticker-led open, VO + music bed, and the assignment method that stops N client videos converging). Each is a *starting point to edit*, never a house style to conform to — the parts that matter most are the parts the director adds. A harness can also be any file anywhere: `--harness ./campaigns/q3/RULES.md` is fully supported, and `VIDFARM_HARNESS=./work/HARNESS.md` sets a default for a whole run.
 
 **The format is two halves, and the split is deliberate:** a front-matter `checks:` block the CLI settles deterministically (duration, aspect, `hook_words_max`, `forbid_text`, `first_frame_text`, … — full key list in `harnesses/README.md`), and every `- [ ]` checkbox in the body, which comes back as a **review item for you to answer**. "Is the withheld answer one the viewer can't supply themselves?" is a judgment call; a linter claiming to settle it would be lying. **Answer the review items honestly in your report** — the CLI prints them precisely because it can't.
 
@@ -4588,7 +4591,8 @@ Two ways in, depending on where the format came from:
 
 ```bash
 # (a) From a bundled base — when the format is one you're defining
-vidfarm harness list                                    # short-form | hooks | ugc-testimonial | explainer | product-demo | product-explainer
+vidfarm harness list                                    # bases: short-form | hooks | ugc-testimonial | explainer | product-demo | product-explainer
+                                                        # + format harnesses: meme-recaption | wall-text-pov-ugc | … (the /experimental shelf, offline)
 vidfarm harness init hooks --out ./work/HARNESS.md
 
 # (b) From the template you're batching — when the format is one you're REPLICATING

package/SKILL.md

@@ -98,6 +98,8 @@ vidfarm publish <forkId>                                 # push edits back to th
 | "A UGC ad for my app" / "someone reacting, then the app" / a client's app demo you have to make watchable | three streams cut against each other: `ugc-reaction` raws (ONE actor, via `actor_<uuid>`), a Display Greenscreen device carrying their real demo on its screen, and the demo. Ships a voiceover-only cut to publish + a voiceover+music cut to review | `vidfarm.cc/experimental/ugc-reaction-greenscreen.md` |
 | "A tips slideshow / carousel" / "5 tips for X" / a listicle post | N still slides at exactly 3.0s, die-cut cutouts on a page or a photo, a literal "Tips for…" cover, ONE slide shilled from the middle. **The slides are the deliverable; the MP4 is the preview.** $0–$0.15 | `vidfarm.cc/experimental/sticker-slideshow-tips.md` |
 | "A confession / truth bomb over a POV or ambient scene" / "just text on a video" / a text-story post | ONE unbroken take + ONE static block of unplated type. Nothing animates, nothing is cut. `duration = words / 8` (min 8s) so one play reaches the HALFWAY mark and they loop to finish. Cast the scene DARK so the type needs no plate. $0 | `vidfarm.cc/experimental/wall-text-pov-ugc.md` |
+| "An animated explainer / a little story that animates" / "like those Vox map animations" / "cutout paper animation" | ONE full-bleed parchment stage, no cuts, a cast of die-cut paper stickers moved by ONE paused GSAP timeline. Narrated, subtitles stay small and kinetic in colour only, the offer named once as a wordmark on the LAST beat. Buy SHEETS, not stickers. Desktop-only (the web editor strips scripts). ~$0.25 hybrid, $0 minimize | `vidfarm.cc/experimental/animated-sticker-story.md` |
+| "Make N videos for N customers / clients" / a batch that must not read as N runs of one template | differentiation is an INPUT, not a hope: assign each variant its own frame before you build any of them, then review frame by frame. $0 | `vidfarm.cc/experimental/unique-product-explainers.md` |
 | "Download this video from `<url>`" | `vidfarm download-video <url>` (paid). Free plan gets a 402 — `vidfarm browse page "<url>"` and save it from their Chrome yourself, else have them download it, then `vidfarm put-file`. Never answer "I can't." | `references/browser-harness.md` |
 | "Turn this thread / subreddit / profile into a video" | `vidfarm recycle <source>` — returns the raw decomposition, unranked; you pick the hook (paid) | `references/assets-and-sourcing.md` |
 | "Create an avatar / spokesperson / talking head" | `vidfarm avatar "<who>" --say "<line>"` — a greenscreen talking-head video, keyed in the same job | `references/primitives.md` |
@@ -195,6 +197,7 @@ Otherwise fetch `https://vidfarm.cc/skill-pack/vidfarm/files/<path>`. Load one f
 | `references/rest-api.md` | direct HTTP integration only |
 | `recipes/*.md` | `find-and-fork-template` · `retheme-template` · `local-edit-render-approve` · `onboard-a-new-director` · `bulk-scripting-with-a-harness` · `cutout-graphics-for-explainers` |
 | `harnesses/README.md` | anything harness-shaped — start here. Bases: `short-form` · `hooks` · `ugc-testimonial` · `explainer` · `product-demo` · `product-explainer` |
+| `vidfarm harness list` | both shelves: the bases above, **plus every format harness from `vidfarm.cc/experimental`** — `meme-recaption` · `wall-text-pov-ugc` · `ugc-reaction-greenscreen` · `sticker-slideshow-tips` · `animated-sticker-story` · `google-news-to-video` · `unique-product-explainers`. They ship in the package, so `vidfarm harness show <name>` reads one in full with no fetch, and `vidfarm qa ./work --harness <name>` grades against it. The name is the URL slug |
 
 Also served at `vidfarm.cc`: `/experiments.md` (ad testing), `/marketplace.md` (the marketplace manual — routes you to one of the two side harnesses below), `/marketplace-buyer.md` (**buyer side**: commission videos from the crowd), `/agentic-clipper.md` (**worker side**: "Agentic Clipper" mode — one orchestrator on a long-horizon earning mission, one subagent per task), `/update.md` (upgrade runbook), `/experimental` (format harnesses under live testing — the index a clipper routes tasks against), `/skill/vidfarm-platform` (architecture), `/skill/hyperframes` (composition-authoring craft — route broad "make me a video" asks here first).
 

package/clipper.md

@@ -279,8 +279,10 @@ What matters for a clipper loop specifically:
 built like a meme recaption gets rejected, and so does the reverse. Read the live index at
 <https://vidfarm.cc/experimental> and pick — a product/feature introduction routes to
 `unique-product-explainers.md`, a recaption or reaction routes to `meme-recaption.md`, a timely
-event routes to `google-news-to-video.md`. Nothing fits? Fall back to a CLI base
-(`vidfarm harness list`) — and if no harness fits at all, **freestyle it against the best practices
+event routes to `google-news-to-video.md`. Each of those also ships inside the CLI under the same
+name, so `vidfarm harness show meme-recaption` reads the whole contract with no fetch, and
+`vidfarm qa ./work --harness meme-recaption` grades the build against it. Nothing fits? Fall back to
+a CLI base (`vidfarm harness list`) — and if no harness fits at all, **freestyle it against the best practices
 in <https://vidfarm.cc/skill.md>.** That is a normal outcome, not a failure: harnesses reproduce a
 *known* format, and a task outside every known format is still one you can deliver well. Never force
 a task into the wrong harness, and never decline one just because no harness matched.

package/dist/src/cli.js

@@ -925,9 +925,18 @@ Local media engines & toolchain (all local, free, no account — no cloud key ne
                             "create me a harness" / "update the harness for
                             this format" / "give me the harness for this
                             template_id" all land here
-    harness list [--json]             Bundled starting points: short-form,
-                                      hooks, ugc-testimonial, explainer,
-                                      product-demo, product-explainer
+    harness list [--json]             Two shelves. BASES to copy and edit:
+                                      short-form, hooks, ugc-testimonial,
+                                      explainer, product-demo,
+                                      product-explainer. FORMAT harnesses —
+                                      complete contracts, read by name, same
+                                      shelf as vidfarm.cc/experimental:
+                                      meme-recaption, wall-text-pov-ugc,
+                                      ugc-reaction-greenscreen,
+                                      sticker-slideshow-tips,
+                                      animated-sticker-story,
+                                      google-news-to-video,
+                                      unique-product-explainers
     harness show <name|path>          Print one [--dna <strand>] to print just
                                       one strand (viral_dna, visual_dna, …)
     harness init <name> [--out <p>]   Copy one next to your work, then EDIT it
@@ -12344,13 +12353,28 @@ async function runHarnessCommand(argv) {
     });
     const json = Boolean(parsed.values.json);
     if (!sub || sub === "list") {
-        const builtins = listBuiltinHarnesses();
-        if (json)
-            return printJson({ harnesses: builtins.map(({ name, path: file, video_type }) => ({ name, path: file, video_type })) });
-        console.log(`${DIM}Built-in harnesses — copy one next to your work, then edit it:${RESET}`);
-        for (const entry of builtins) {
+        const all = listBuiltinHarnesses();
+        if (json) {
+            return printJson({
+                harnesses: all.map(({ name, path: file, video_type, origin, url }) => ({ name, path: file, video_type, origin, url })),
+                index_url: "https://vidfarm.cc/experimental"
+            });
+        }
+        const bases = all.filter((entry) => entry.origin === "builtin");
+        const experimental = all.filter((entry) => entry.origin === "experimental");
+        console.log(`${DIM}Base harnesses — copy one next to your work, then edit it:${RESET}`);
+        for (const entry of bases) {
             console.log(`  ${GREEN}${entry.name}${RESET} ${DIM}${entry.video_type ?? ""}${RESET}`);
         }
+        if (experimental.length) {
+            // The same shelf as https://vidfarm.cc/experimental, shipped in the package
+            // so an agent reads a full format contract by name without a fetch.
+            console.log(`\n${DIM}Format harnesses — complete contracts for ONE format. Read one before you build it:${RESET}`);
+            for (const entry of experimental) {
+                console.log(`  ${GREEN}${entry.name}${RESET} ${DIM}${(entry.video_type ?? "").slice(0, 120)}${RESET}`);
+            }
+            console.log(`${DIM}vidfarm harness show <name>              (also live at https://vidfarm.cc/experimental)${RESET}`);
+        }
         console.log(`\n${DIM}vidfarm harness init <name> --out ./work/${HARNESS_FILENAME}${RESET}`);
         console.log(`${DIM}vidfarm harness derive <forkId>          (a decomposed template → a harness)${RESET}`);
         console.log(`${DIM}vidfarm qa ./work --harness <name|path>  (repeatable — harnesses stack)${RESET}`);

package/dist/src/devcli/harness.js

@@ -59,10 +59,10 @@ const DISCOVERY_NAMES = ["HARNESS.md", "harness.md", "QA_REGIME.md", "qa_regime.
 // They ship inside the skill pack (.agents/skills/vidfarm/harnesses/) rather
 // than as TS string constants, so a director can read, diff, and copy them as
 // normal files — the file IS the documentation.
-function builtinDir() {
+function packDir(...segments) {
     let dir = path.dirname(fileURLToPath(import.meta.url));
     for (let i = 0; i < 6; i += 1) {
-        const candidate = path.join(dir, ".agents", "skills", "vidfarm", "harnesses");
+        const candidate = path.join(dir, ...segments);
         if (existsSync(candidate))
             return candidate;
         const parent = path.dirname(dir);
@@ -72,32 +72,77 @@ function builtinDir() {
     }
     return null;
 }
-export function listBuiltinHarnesses() {
-    const dir = builtinDir();
+function builtinDir() {
+    return packDir(".agents", "skills", "vidfarm", "harnesses");
+}
+// The EXPERIMENTAL harnesses — full format contracts under live testing, served
+// at https://vidfarm.cc/experimental/<slug>.md. They ship inside the npm package
+// too (`experimental/**/*.md` in package.json `files`), so an agent that already
+// has the CLI reaches them by NAME, offline, with no fetch: `vidfarm harness show
+// meme-recaption`, `vidfarm qa ./work --harness wall-text-pov-ugc`. The web index
+// stays the source of truth for what exists; this is the same shelf, local.
+function experimentalDir() {
+    return packDir("experimental");
+}
+function readEntry(full, name, origin) {
+    const parsed = parseHarness(readFileSync(full, "utf8"), full);
+    return {
+        name,
+        path: full,
+        video_type: parsed.video_type,
+        summary: parsed.summary,
+        origin,
+        ...(origin === "experimental" ? { url: `https://vidfarm.cc/experimental/${name}.md` } : {})
+    };
+}
+export function listExperimentalHarnesses() {
+    const dir = experimentalDir();
     if (!dir)
         return [];
     return readdirSync(dir)
-        .filter((file) => file.endsWith(BUILTIN_SUFFIX))
+        .filter((file) => file.endsWith(".md"))
         .sort()
-        .map((file) => {
-        const full = path.join(dir, file);
-        const parsed = parseHarness(readFileSync(full, "utf8"), full);
-        return { name: file.slice(0, -BUILTIN_SUFFIX.length), path: full, video_type: parsed.video_type, summary: parsed.summary };
-    });
+        .map((file) => readEntry(path.join(dir, file), file.slice(0, -".md".length), "experimental"));
 }
-/** Resolve `hooks` (built-in) or `./my/HARNESS.md` (a path) to a file. */
+/** Both shelves, built-ins first. `vidfarm harness list` prints exactly this. */
+export function listBuiltinHarnesses() {
+    const dir = builtinDir();
+    const builtins = !dir
+        ? []
+        : readdirSync(dir)
+            .filter((file) => file.endsWith(BUILTIN_SUFFIX))
+            .sort()
+            .map((file) => readEntry(path.join(dir, file), file.slice(0, -BUILTIN_SUFFIX.length), "builtin"));
+    return [...builtins, ...listExperimentalHarnesses()];
+}
+/**
+ * Resolve `hooks` (built-in), `meme-recaption` (experimental), or
+ * `./my/HARNESS.md` (a path) to a file. Underscore spellings resolve too, so the
+ * URL slug and the CLI name never disagree — the same near-miss the web route
+ * forgives with its aliases.
+ */
 export function resolveHarnessPath(ref) {
     const direct = path.resolve(ref);
     if (existsSync(direct) && !direct.endsWith(path.sep))
         return direct;
-    const dir = builtinDir();
-    if (dir) {
-        const candidate = path.join(dir, `${ref}${BUILTIN_SUFFIX}`);
+    const slug = ref.trim().toLowerCase().replace(/\.md$/, "").replace(/_/g, "-");
+    const builtins = builtinDir();
+    if (builtins) {
+        for (const name of [ref, slug]) {
+            const candidate = path.join(builtins, `${name}${BUILTIN_SUFFIX}`);
+            if (existsSync(candidate))
+                return candidate;
+        }
+    }
+    const experimental = experimentalDir();
+    if (experimental) {
+        const candidate = path.join(experimental, `${slug}.md`);
         if (existsSync(candidate))
             return candidate;
     }
     const names = listBuiltinHarnesses().map((entry) => entry.name);
-    throw new Error(`No harness "${ref}". Pass a file path, or one of the built-ins: ${names.join(", ") || "(none bundled)"}. ` +
+    throw new Error(`No harness "${ref}". Pass a file path, or one of the bundled names: ${names.join(", ") || "(none bundled)"}. ` +
+        `The live index is https://vidfarm.cc/experimental. ` +
         `Scaffold your own with \`vidfarm harness init <name> --out ./work/HARNESS.md\`, ` +
         `or derive one from a decomposed template with \`vidfarm harness derive <forkId>\`.`);
 }

package/dist/src/devcli/skill-docs.js

@@ -117,7 +117,8 @@ export const PACK_TOPICS = [
         blurb: "The 5-stage ladder — what the viewer knows, what the video must do, and what it may ask for" },
     { topic: "problem-angles", aliases: ["angle", "lenses", "problem-angle"], doc: "references/content-ideas.md", heading: "The problem angles",
         blurb: "44 angles on the problem — hold the frame, change the angle when a topic is \"already covered\"" },
-    { topic: "meme-recaption", aliases: ["meme", "recaption", "meme-caption", "meme_recaption"], doc: "references/editor-workflows.md", heading: "Writing a meme recaption",
+    { topic: "meme-recaption", // `meme_recaption` needs no alias: resolvePackTopic folds `_` to `-` first.
+        aliases: ["meme", "recaption", "meme-caption"], doc: "references/editor-workflows.md", heading: "Writing a meme recaption",
         blurb: "Recaption a meme at a pain or a win the niche knows — the cold-viewer test. Building one from scratch? the full format is vidfarm.cc/experimental/meme-recaption.md" },
     { topic: "product-explainer", aliases: ["product-explainers"], doc: "harnesses/product-explainer.HARNESS.md",
         blurb: "The product-explainer harness — the bundled base for explaining what a product does" },