docs: add documentation quality gates

docs/prompting/storyboards.mdx

@@ -3,6 +3,8 @@ title: Storyboards
 description: "For multi-scene work, don't prompt the scenes one by one — prompt the plan: the arc, the per-frame beats, and the pacing rule the build follows to fill them in."
 ---
 
+import { DocsVideo } from "/snippets/docs-video.jsx";
+
 [Variables and templating](/prompting/variables-and-templating) was about reusing one composition across many renders. This page is the other axis of scale: one film with many scenes. Past a handful of beats, describing each scene from a blank page — "then frame 2 shows X, then frame 3 shows Y" — is the slow way and the way that drifts, because nothing ties the frames to each other. The fast way is to prompt the **plan** once — the throughline, the job each frame does, the rule that paces reveals — and let the build put frames against it.
 
 This narrative vocabulary is a writing discipline, not additional `STORYBOARD.md` schema: the workflow translates the plan into the smaller machine-readable shape the build consumes.
@@ -85,7 +87,11 @@ Without stating the return explicitly, a rebuild is free to treat the early moti
 >
 > Frame 3 — Landing (10.0–15.0s), type: cta, persuasion: callback + distillation, beat: resolve + inevitability, focal: the completed motif. At 10.0s: the accent dot from frames 1–2 expands and fills into the full Fernwell wordmark lockup — same motif, now complete, denser and larger. At 12.0s: tagline "Fernwell. Built for flow." stamps in below it. Hold 13.5–15.0s.
 
-<video controls muted loop playsinline preload="metadata" src="https://static.heygen.ai/hyperframes-oss/docs/images/prompting/storyboard-mini.mp4#t=0.1" style={{ borderRadius: "0.5rem", marginTop: "0.75rem" }}></video>
+<DocsVideo
+  title="HyperFrames video: Storyboard Mini"
+  src="https://static.heygen.ai/hyperframes-oss/docs/images/prompting/storyboard-mini.mp4#t=0.1"
+  loop
+/>
 *Rendered from the prompt above, unedited — no audio track, exactly as asked.*
 
 ## Related
@@ -100,7 +106,7 @@ Without stating the return explicitly, a rebuild is free to treat the early moti
   <Card title="Design systems and brand" icon="palette" href="/prompting/design-systems">
     The two-color discipline and brand tokens a storyboard's direction block draws from.
   </Card>
-  <Card title="The HyperFrames pipeline" icon="route" href="/guides/pipeline">
+  <Card title="How a HyperFrames project works" icon="route" href="/concepts">
     `STORYBOARD.md` as a production artifact — where this chapter's plans land, downstream of `BRIEF.md`.
   </Card>
 </CardGroup>
@@ -113,7 +119,11 @@ This is the clause in the [full capstone prompt](/prompting/capstone#the-full-pr
 
 > **The clip card** — the `<div class="clip">` typed in the opening travels the whole journey: it slides onto the wire as a clip chip after being typed, rides ahead of the camera between regions (handing itself off — visible leaving one region and arriving in the next), and is the thing that finally renders at the end. It is the protagonist.
 
-<video controls muted loop playsinline preload="metadata" src="https://static.heygen.ai/hyperframes-oss/docs/images/prompting/capstone-region-render.mp4#t=0.1" style={{ borderRadius: "0.5rem", marginTop: "0.75rem" }}></video>
+<DocsVideo
+  title="HyperFrames video: Capstone Region Render"
+  src="https://static.heygen.ai/hyperframes-oss/docs/images/prompting/capstone-region-render.mp4#t=0.1"
+  loop
+/>
 *That clause paying off, rendered — the protagonist chip arriving at the render slot after a full minute on the wire.*
 
 *Next: [Editing existing videos](/prompting/editing-existing-videos) — the editor verbs that turn a first render, storyboard or not, into the twenty edits after it.*