@officexapp/vidfarm-devcli 0.21.53 → 0.21.55

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
@@ -2747,7 +2756,7 @@ Rules:
 - When swapping visuals, match both the literal scene DNA and the narrative purpose of the beat.
 - For replacement graphics, screenshots, or still-like scenes, prefer AI image generation plus Ken Burns before paying for AI video unless static_vs_pivot says motion footage is load-bearing.
 - If narration must be customized, default to premium ElevenLabs first, then the user's own ElevenLabs path, then BYOK OpenAI/Gemini/OpenRouter. If captions or scenes were timed to the old VO, retime them to the new narration.
-- NO HTML SLOP. You are editing HTML, but the output is a social video, not a web page. THE TEST IS THE NATIVE-EDITOR TEST: could you have made this element with the tools inside TikTok's own editor? That toolset is a font, a color, a stroke/outline, a soft shadow, a tight text box, alignment, opacity, rotation, animation presets — plus stickers, emoji, drawn marks and clips. It has NO padded capsule, NO border, NO gradient fill, NO blur panel, NO card. If you reached past it, cut it. Never author landing-page furniture: CTA "buttons" (a filled/gradient rounded capsule with action copy like "Sign Up for a Free Trial →"), benefit chip/badge rows ("✓ No Credit Card Needed"), bordered/shadowed/frosted cards holding a headline + URL, gradient text fills, feature grids, bulleted lists, or web-default fonts (Inter/Roboto/Arial/system-ui). AND NOT A SINGLE PILL EITHER: one lonely rounded, padded, filled capsule around a static stat or label — "10 hrs / week", "STEP 2", "EP.01", "+40%" — is a web badge, and being the only one on screen does not make it native. The ONLY legitimate capsule in a video is the active-word spotlight/karaoke caption highlight, because it moves with the spoken word. Emphasize a stat the way the editor would: bigger, heavier, ALL-CAPS, an accent color, a hand-drawn circle or underline, or its own beat on screen. Rule of thumb on anything holding words: border-radius over ~8px PLUS a background fill PLUS padding = a badge; drop the fill or drop the radius until the band hugs the glyphs. None of this appears in a real TikTok, and nothing in a video is clickable — say it as timed text on the footage instead. Arrows, scribble/underline marks, italics, ALL-CAPS, single-word color pops, emoji, transparent cut-out stickers, and mock social UI (iMessage bubbles, comment cards) are all fine. Captions use one of the FIVE imported families and nothing else (Montserrat default / TikTok Sans / Abel / Source Code Pro / Yesteryear - the full regime, with a rendered specimen of each, is at https://vidfarm.cc/fonts) at weight 700-900, ~36-64px on a 1080-wide frame, inside the 8%-85% safe zone, with exactly one of four backgrounds: outline, plain, an active-word spotlight/karaoke pill, or a tight-hugging solid band (radius <=8px, no border/shadow/gradient/blur).
+- NO HTML SLOP. You are editing HTML, but the output is a social video, not a web page. THE TEST IS THE NATIVE-EDITOR TEST: could you have made this element with the tools inside TikTok's own editor? That toolset is a font, a color, a stroke/outline, a soft shadow, a tight text box, alignment, opacity, rotation, animation presets — plus stickers, emoji, drawn marks and clips. It has NO padded capsule, NO border, NO gradient fill, NO blur panel, NO card. If you reached past it, cut it. Never author landing-page furniture: CTA "buttons" (a filled/gradient rounded capsule with action copy like "Sign Up for a Free Trial →"), benefit chip/badge rows ("✓ No Credit Card Needed"), bordered/shadowed/frosted cards holding a headline + URL, gradient text fills, feature grids, bulleted lists, or web-default fonts (Inter/Roboto/Arial/system-ui). AND NOT A SINGLE PILL EITHER: one lonely rounded, padded, filled capsule around a static stat or label — "10 hrs / week", "STEP 2", "EP.01", "+40%" — is a web badge, and being the only one on screen does not make it native. The ONLY legitimate capsule in a video is the active-word spotlight/karaoke caption highlight, because it moves with the spoken word. Emphasize a stat the way the editor would: bigger, heavier, ALL-CAPS, an accent color, a hand-drawn circle or underline, or its own beat on screen. Rule of thumb on anything holding words: border-radius over ~8px PLUS a background fill PLUS padding = a badge; drop the fill or drop the radius until the band hugs the glyphs. None of this appears in a real TikTok, and nothing in a video is clickable — say it as timed text on the footage instead. Arrows, scribble/underline marks, italics, ALL-CAPS, single-word color pops, emoji, transparent cut-out stickers, and mock social UI (iMessage bubbles, comment cards) are all fine. Captions use one of the FIVE imported families by default (Montserrat default / TikTok Sans / Abel / Source Code Pro / Yesteryear - the full regime, with a rendered specimen of each, is at https://vidfarm.cc/fonts). A custom family is allowed only if the composition DECLARES it (@font-face or a Google Fonts @import); an undeclared family silently falls back to a web-default sans and local renders coerce it to Montserrat. Every family has its own standalone reference card at https://vidfarm.cc/assets/fonts/caption-font-<family>.png (backgrounds: caption-bg-outline|plain|spotlight|highlight-solid.png) - after styling, pull a still and COMPARE it against the card for the family you picked, because a font that failed to load looks fine on its own. Weight 700-900, ~36-64px on a 1080-wide frame, inside the 8%-85% safe zone, with exactly one of four backgrounds: outline, plain, an active-word spotlight/karaoke pill, or a tight-hugging solid band (radius <=8px, no border/shadow/gradient/blur).
 - NO LAYOUT TEMPLATES — JUDGE THE WHOLE FRAME, NOT JUST THE ELEMENT. Every rule above judges one element, and a frame can pass element-by-element and still be a web page. The archetype is the MODAL: the backdrop dimmed and blurred out of focus, and floating on top of it a rounded bordered box holding a big headline, a smaller support line, and a fat CTA button. THE STACK IS THE TELL, NOT THE BOX — delete the border, the fill and the capsule, keep headline then subheadline then CTA centred in a well with even margins, and it STILL reads as a landing page, because a viewer recognizes the SHAPE before reading a single word. Banned at frame level: a modal/dialog staged on top of a backdrop that has been dimmed, blurred, greyed or scaled back (nothing in a video pops "above" the video); the hero triplet and its cousins (title + kicker + logo lockup, question + answer + URL); a full-frame dark wash used to stage a floating block (a legibility band on ONE caption is legal, a page-wide wash to stage a panel is not; likewise a blurred backdrop is fine alone — a blurred fill behind a 16:9 clip in a 9:16 frame is a real technique — but blur PLUS dimming is modal staging); nav strip / hero / three-up feature row / testimonial block / footer fine print; a blurred website screenshot used as the background plate (if the backdrop is a web page, the frame is a screen recording of a web page — show the real product UI full-bleed and in focus, or don't show it); a centred content column with even gutters and document margins. THE FIX IS ALWAYS TO UNSTACK IT INTO TIME: the headline is the hook at start:0, the support line lands on the next cut, the CTA is SPOKEN or a bare caption on the final frame. You lose nothing — a viewer reads one line at a time anyway — and you gain the pacing that makes it look shot rather than designed. Self-check before you place any text group: am I arranging words relative to EACH OTHER, or relative to the PICTURE? Relative to each other is a layout, which is web. Two on-screen text runs at once is the ceiling. Verify on real pixels: \`vidfarm stills . --at <t>\` — if the still could be a screenshot of a website, rebuild the beat. \`vidfarm qa\` catches only the mechanical half (layout-template, modal-scrim); the frame-level judgement is yours.
 - STRUCTURE BEFORE POLISH — THE FOUR CHARGES, WRITTEN BEFORE YOU TOUCH THE TIMELINE. Most agent-made videos fail on structure, not polish, because the timeline is the fun part so it gets built first and the words get retrofitted. Invert it: (1) HOOK — write the opening line as text first: a complete clause (subject + verb), no jargon, naming a SITUATION ("I've quit six businesses") not a label ("anonymity"); it goes on screen at start:0, because caption chunk 1 is read before any audio and muted autoplay is the default. Banned openings: throat-clearing ("so I was thinking", "here's the thing"), a logo, a title card, a fade from black, context before the claim. (2) LOOP — one open question by 0:10, said ON SCREEN, closing INSIDE this video (state the timestamp it closes at; if you can't, there is no loop), and the withheld answer must be one the viewer CANNOT supply themselves — a formally-correct loop with a guessable answer passes every mechanical check and dies in the field. (3) PAYOFF — shown, not summarized, ≥5 uninterrupted seconds, landing BEFORE the final beat; the payoff is not the CTA. (4) BAIT — one ask in the final beat and in the post caption; a keyword comment ask ("comment CLIPPER and I'll send the breakdown") is standard and allowed, but never "follow for part two", ragebait, or an earnings/health claim traded for the reply. Then build the timeline. Re-theming a decomposed template: viral_dna already names the source's hook/retention/payoff — rebuild each charge for the new subject, never flatten the loop into a product statement. Full craft harness: the vidfarm skill's references/hooks-and-virality.md. Checkable form: \`vidfarm harness show hooks\`.
 - ORIENT THE COLD VIEWER IN THE FIRST 3 SECONDS — THE VIEWER HAS NO CONTEXT AND DID NOT CHOOSE THIS VIDEO. Distinct from the hook: the hook makes them WANT to watch, orientation makes the watching POSSIBLE. A stranger mid-scroll must be able to answer three things by ~3s — what am I looking at (the CATEGORY noun), who is it for, and why is this on my screen (the situation). The failure is not a bad first frame, it is a good video that BEGINS AT BEAT TWO, and the author cannot see it because the author already knows what the thing is. Signatures, each a rebuild not a polish: a pronoun with no referent ("it just works", "this changes everything", "here's how they do it"); starting at step three (the process already running, the dashboard already full); a metaphor whose subject only lands at 6s; insider vocabulary, a product's own feature name, or an ACRONYM in the first line; a detail crop that reads as texture until you know the whole. Instead, the opening beat is BOTH channels at once: an EASY IMAGE (one large subject, already moving, legible at a glance and at thumbnail scale — a relevant die-cut sticker names the category before a word is read) AND an EASY LINE (first spoken sentence one clause, <=12 words, everyday words, concrete noun + verb, no subordinate clause, brand name said once plainly, and the CATEGORY named: "X is a language app that…"). Give the SITUATION, not the label — "the end of the month, and your receipts are in a shoebox" orients, "expense automation" does not. THIS IS NOT AN INTRO AND COSTS NO EXTRA SECONDS: it replaces the wind-up sentence, it never precedes it, and it never licenses a logo, a title card or a fade from black. Test it on the render, not the script: play the first 3 seconds ONLY to somebody with no context and stop — they should say what kind of thing it is and roughly who it is for. "Something about audio" is a fail. Fullest form: \`vidfarm harness show product-explainer\` (Rule 0).
@@ -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/composition-edit.js

@@ -391,11 +391,42 @@ const CAPTION_DEFAULT_FRAME = { x: 10, y: 70, width: 80, height: 14 };
 export const TIKTOK_CAPTION_SAFE_ZONE = { top: 8, bottom: 85 }; // % of canvas height
 // The composition font regime — mirrors COMPOSITION_FONT_IMPORT's family list in
 // services/studio-project-adapter.ts. A caption/text layer whose primary family
-// is outside this set isn't even imported (so it silently falls back at render),
-// which means coercing it to the bold default is strictly an improvement.
+// is outside this set is normally not imported (so it silently falls back at
+// render), which means coercing it to the bold default is strictly an
+// improvement. The regime is a strong default, not a ban: a family the
+// composition declares for itself (see compositionDeclaresFont) is left alone.
 const CAPTION_FONT_REGIME = ["tiktok sans", "montserrat", "abel", "source code pro", "yesteryear"];
 const CAPTION_REGIME_FALLBACK_FONT = "Montserrat";
 const CAPTION_FONT_FALLBACK_CHAIN = "'Montserrat', 'TikTok Sans', Abel, sans-serif";
+/**
+ * A CUSTOM family is allowed — as long as the composition actually ships it.
+ * The regime exists because an unimported family silently falls back to a
+ * web-default sans at render; it is not a ban on typography. So: if the
+ * composition declares the family itself (an `@font-face` for it, or a Google
+ * Fonts `@import`/`<link>` naming it), leave the layer alone. Only a family
+ * with no declaration anywhere gets coerced, because that one really is broken.
+ */
+export function compositionDeclaresFont(html, family) {
+    const name = family.trim().toLowerCase();
+    if (!name)
+        return false;
+    const hay = html.toLowerCase();
+    // @font-face { font-family: "Brand Sans" }
+    const faceRe = /@font-face\s*{[^}]*}/g;
+    for (const block of hay.match(faceRe) ?? []) {
+        const declared = block.match(/font-family\s*:\s*['"]?([^;'"}]+)/);
+        if (declared && declared[1].trim() === name)
+            return true;
+    }
+    // Google Fonts URL: family=Brand+Sans / family=Brand%20Sans
+    const urlName = name.replace(/\s+/g, "");
+    for (const m of hay.matchAll(/fonts\.googleapis\.com\/css2\?([^"')\s]+)/g)) {
+        const params = m[1].replace(/\+/g, "").replace(/%20/g, "");
+        if (params.includes(`family=${urlName}`))
+            return true;
+    }
+    return false;
+}
 function setStylePercent(node, prop, value) {
     if (node?.style)
         node.style[prop] = `${Number(value.toFixed(2))}%`;
@@ -450,7 +481,9 @@ export function normalizeTikTokCaptionLayout(html) {
         }
         // Font: coerce off-regime primary family to the bold default.
         const primary = String(node.getAttribute?.("data-font-family") || "").trim();
-        if (primary && !CAPTION_FONT_REGIME.includes(primary.toLowerCase())) {
+        if (primary &&
+            !CAPTION_FONT_REGIME.includes(primary.toLowerCase()) &&
+            !compositionDeclaresFont(html, primary)) {
             node.setAttribute?.("data-font-family", CAPTION_REGIME_FALLBACK_FONT);
             if (node.style)
                 node.style.fontFamily = CAPTION_FONT_FALLBACK_CHAIN;

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/qa-check.js

@@ -28,6 +28,7 @@ import { createHash } from "node:crypto";
 import { existsSync, readFileSync, writeFileSync } from "node:fs";
 import path from "node:path";
 import { parseHTML } from "linkedom";
+import { compositionDeclaresFont } from "./composition-edit.js";
 // ── Revision governor ────────────────────────────────────────────────────────
 //
 // `vidfarm qa` is feedback, not a gate — which is exactly what makes it a loop
@@ -646,16 +647,19 @@ export function qaCompositionHtml(html) {
         const style = styleString(node);
         const cssMatch = style.match(/(?:^|;)\s*font-family\s*:\s*([^;]+)/);
         const family = primaryFamily(attr || (cssMatch ? cssMatch[1] : ""));
-        if (family && !FONT_REGIME.includes(family)) {
+        // A custom family is allowed when the composition SHIPS it — an @font-face
+        // or a Google Fonts import naming it. The defect this rule exists for is a
+        // family that no render can load, so a declared one is not a finding.
+        if (family && !FONT_REGIME.includes(family) && !compositionDeclaresFont(html, family)) {
             const isWebDefault = WEB_DEFAULT_FONTS.includes(family) || family === "sans-serif" || family === "serif";
             push({
                 rule: "font-regime",
                 severity: isWebDefault ? "error" : "warn",
                 message: isWebDefault
                     ? `Text layer in "${family}" — a website body font. This alone makes a frame read as a screenshot of a web page.`
-                    : `Text layer in "${family}", outside the composition's imported font regime — it will silently fall back at render.`,
+                    : `Text layer in "${family}", which this composition never imports — it will silently fall back to a web-default sans at render.`,
                 where: label(node, "text layer"),
-                fix: `Use an imported display family: Montserrat (default), TikTok Sans, Abel, Source Code Pro, or Yesteryear — e.g. \`vidfarm set-style <dir> --layer <key> --font-family Montserrat\`. Local renders auto-coerce this, but the editor preview will not match until you fix it. The five families, each rendered as a real caption: https://vidfarm.cc/fonts`
+                fix: `Use a regime family — Montserrat (default), TikTok Sans, Abel, Source Code Pro, Yesteryear — e.g. \`vidfarm set-style <dir> --layer <key> --font-family Montserrat\`; each has its own reference card, e.g. https://vidfarm.cc/assets/fonts/caption-font-montserrat.png (all five: https://vidfarm.cc/fonts). Keeping "${family}" is allowed, but then you must IMPORT it in the composition (@font-face or a Google Fonts @import) — otherwise local renders coerce it to Montserrat.`
             });
         }
         // Weight: the TikTok caption look is heavy. Light weights are a legitimate

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" },