@officexapp/vidfarm-devcli 0.21.54 → 0.21.55

package/experimental/google-news-to-video.md

@@ -1,3 +1,12 @@
+---
+name: google-news-to-video
+video_type: Timely newsjack — a recent real event turned into a short video. Two searches, never one: news-search finds the STORY, video/image-search finds the VISUALS
+# No `checks:` block on purpose. This harness governs the SOURCING method, not one
+# fixed cut, so the shape of the finished video is set by whichever format harness
+# you build it in (short-form, wall-text-pov-ugc, …). Stack them: `--harness
+# google-news-to-video --harness short-form`.
+---
+
 # Google News to Video — reusable prompt & method
 
 Turns **a recent real event → a timely short video**, using two searches instead of one.

package/experimental/unique-product-explainers.md

@@ -1,3 +1,11 @@
+---
+name: unique-product-explainers
+video_type: Bulk product explainers — N customer URLs into N product-introduction videos that do not look like each other. Differentiation as an input, frame-level review, measured verification
+# No `checks:` block on purpose. This harness governs a BATCH and its anti-convergence
+# rules; the per-video shape comes from the format harness each variant is built in.
+# Stack them: `--harness unique-product-explainers --harness product-explainer`.
+---
+
 # Unique Product Explainer Videos — reusable prompt & method
 
 Turns **N customer URLs → N product-introduction videos that do not look like each other**,

package/marketplace.md

@@ -32,6 +32,8 @@ get paid to make videos for other people?"* Do not guess — guessing wrong cost
 harnesses — the written apparatus that reproduces one format well — and the live index is
 `https://vidfarm.cc/experimental`. A **buyer** names one in the brief; a **clipper** reads the task,
 identifies the format, and follows the harness that matches it. Details in each side's harness file.
+Every one of them also ships inside the CLI — `vidfarm harness list`, then `vidfarm harness show
+<name>` — so a clipper with no network still reads the full contract by name.
 
 ## Get the key over REST (no copy-paste)
 
@@ -425,6 +427,9 @@ task is, then follows the matching format harness from the live index at
 - a task tied to a recent real event → `https://vidfarm.cc/experimental/google-news-to-video.md`
 - nothing in the index fits → a CLI base: `vidfarm harness list` (`short-form`, `hooks`,
   `ugc-testimonial`, `explainer`, `product-demo`, `product-explainer`)
+- **no network, or you would rather not fetch** → `vidfarm harness list` prints the index above as
+  its second shelf, and `vidfarm harness show <name>` prints the whole harness. Every format harness
+  ships inside the CLI package, under the same name as its URL slug. Same document, no fetch
 - **no harness fits at all → freestyle it against the best practices in
   `https://vidfarm.cc/skill.md`.** This is a normal, correct outcome, not a failure. Harnesses exist
   to reproduce a *known* format reliably; a task outside every known format is still a task you can

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@officexapp/vidfarm-devcli",
-  "version": "0.21.54",
+  "version": "0.21.55",
   "description": "Local bridge for the Vidfarm Trackpad Editor. `vidfarm serve <template_id>` boots the FULL editor on localhost (disk-backed records/storage, free in-process render); edit composition.html on disk (Claude Code, Codex, etc.) and the browser live-morphs it.",
   "type": "module",
   "bin": {