@vibeframe/cli 0.95.1 → 0.95.2

package/dist/index.js

@@ -63483,7 +63483,7 @@ init_source();
 // package.json
 var package_default = {
   name: "@vibeframe/cli",
-  version: "0.95.1",
+  version: "0.95.2",
   description: "VibeFrame CLI - natural language video editing from the terminal",
   private: false,
   license: "MIT",
@@ -71741,6 +71741,7 @@ applies to BUILD only.
 Examples:
 - "make this image" \u2192 \`vibe generate image "..." -o assets/name.png\`
 - "use this image to make a video" \u2192 \`vibe generate video "..." -i image.png -o renders/name.mp4\`
+- "add a lower-third/title/animated overlay/grain/vignette to this clip" \u2192 prefer \`vibe generate motion "..." --video clip.mp4 --render -o out.mp4\` when the request asks for designed or animated motion graphics.
 - "please add visuals using OpenAI image gen" \u2192 \`vibe generate image "..." -p openai ...\`
 - *(verb-less paste)* "aerial view of a misty mountain peak at sunrise..." \u2192 \`vibe generate image "<paste>" -o assets/mountain-peak.png\`. **Don't** read it as a brief for DESIGN.md.
 
@@ -71757,6 +71758,10 @@ bundle, then renders to MP4. Idempotent re-runs reuse cached assets.
 **REMIX \u2014 transform existing video / audio.**
 Use \`vibe remix\`, \`vibe edit\`, or \`vibe audio\`. One-shot,
 batch-oriented operations on a file the user already has on disk.
+\`vibe edit text-overlay\` is the free deterministic path for simple static
+text burn-in. If the user asks for motion design, animated lower-thirds,
+designed titles, grain/vignette as part of a graphic treatment, or says
+"motion graphics", use \`vibe generate motion --video ... --render\` instead.
 
 Decision rule: if the user asks for one asset, it's ASSET. If the user asks
 for a multi-scene/storyboard/composed video, it's BUILD. If the user is
@@ -71782,6 +71787,7 @@ starting from a media file and wants it transformed, it's REMIX.
 | Extract highlights from a long video | \`vibe remix highlights file.mp4 -d 60\` |
 | Long video \u2192 vertical shorts | \`vibe remix auto-shorts file.mp4 -n 3 --add-captions\` |
 | Add animated word-by-word captions | \`vibe remix animated-caption file.mp4 -s karaoke-sweep\` |
+| Add designed motion graphics overlay | \`vibe generate motion "lower-third..." --video file.mp4 --render -o out.mp4\` |
 | Remove silence | \`vibe edit silence-cut in.mp4 -o out.mp4\` |
 | Add static captions | \`vibe edit caption in.mp4 -o out.mp4\` |
 | Translate audio (transcribe \u2192 TTS) | \`vibe audio dub file.mp4 -t ko\` |
@@ -71885,7 +71891,10 @@ overview content moved into AGENTS.md above):
 Claude-specific routing note: follow the ASSET / BUILD / REMIX decision
 rules in \`AGENTS.md\`. In particular, a request for one generated image or
 one generated video clip is an ASSET request: use \`vibe generate image\` or
-\`vibe generate video\` directly. Do not invoke \`/vibe-scene\`, edit
+\`vibe generate video\` directly. A request for designed/animated overlays
+on an existing clip is usually \`vibe generate motion --video ... --render\`,
+not \`vibe edit text-overlay\`, unless the user explicitly asks for a simple
+static text burn-in. Do not invoke \`/vibe-scene\`, edit
 \`DESIGN.md\`, or edit \`STORYBOARD.md\` unless the user explicitly asks for a
 scene, storyboard, or composed video.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vibeframe/cli",
-  "version": "0.95.1",
+  "version": "0.95.2",
   "description": "VibeFrame CLI - natural language video editing from the terminal",
   "private": false,
   "license": "MIT",
@@ -183,8 +183,8 @@
     "tsx": "^4.21.0",
     "typescript": "^5.3.3",
     "vitest": "^1.2.2",
-    "@vibeframe/ai-providers": "0.95.1",
-    "@vibeframe/core": "0.95.1"
+    "@vibeframe/core": "0.95.2",
+    "@vibeframe/ai-providers": "0.95.2"
   },
   "engines": {
     "node": ">=20"