@vibeframe/cli 0.94.1 → 0.95.0

package/dist/index.js

@@ -25754,8 +25754,18 @@ async function fileExists(path2) {
     return false;
   }
 }
+async function findProjectConfigPath(cwd = process.cwd()) {
+  let dir = resolve4(cwd);
+  for (; ; ) {
+    const candidate = getProjectConfigPath(dir);
+    if (await fileExists(candidate)) return candidate;
+    const parent = resolve4(dir, "..");
+    if (parent === dir) return null;
+    dir = parent;
+  }
+}
 async function getActiveScope(cwd) {
-  return await fileExists(getProjectConfigPath(cwd)) ? "project" : "user";
+  return await findProjectConfigPath(cwd) ? "project" : "user";
 }
 function applyDefaults(parsed) {
   const defaults = createDefaultConfig();
@@ -25787,7 +25797,8 @@ async function loadConfig(options = {}) {
   const { scope, cwd, merge } = options;
   if (merge) {
     const user = await readConfigFile(USER_CONFIG_PATH);
-    const project2 = await readConfigFile(getProjectConfigPath(cwd));
+    const projectPath2 = await findProjectConfigPath(cwd);
+    const project2 = projectPath2 ? await readConfigFile(projectPath2) : null;
     if (!user && !project2) return null;
     if (!user) return project2;
     if (!project2) return user;
@@ -25808,7 +25819,8 @@ async function loadConfig(options = {}) {
   if (scope) {
     return readConfigFile(getConfigPath(scope, cwd));
   }
-  const project = await readConfigFile(getProjectConfigPath(cwd));
+  const projectPath = await findProjectConfigPath(cwd);
+  const project = projectPath ? await readConfigFile(projectPath) : null;
   if (project) return project;
   return readConfigFile(USER_CONFIG_PATH);
 }
@@ -63444,7 +63456,7 @@ init_source();
 // package.json
 var package_default = {
   name: "@vibeframe/cli",
-  version: "0.94.1",
+  version: "0.95.0",
   description: "VibeFrame CLI - natural language video editing from the terminal",
   private: false,
   license: "MIT",
@@ -71685,10 +71697,21 @@ vibe walkthrough scene         # step-by-step authoring guide (scene)
 vibe walkthrough pipeline      # step-by-step authoring guide (pipeline)
 \`\`\`
 
-## Two flows \u2014 pick by intent
+## Route by the user's actual request
+
+Routing the user's request correctly is the most important judgement call
+you'll make. Do not force everything into a scene project.
 
-VibeFrame splits cleanly into two flows. Routing the user's request
-correctly is the most important judgement call you'll make.
+**ASSET \u2014 create one generated asset.**
+If the user asks for a single image, single video clip, sound effect, music
+bed, or narration file, use \`vibe generate ...\` directly. Do **not** edit
+\`DESIGN.md\`, \`STORYBOARD.md\`, or run \`vibe scene ...\` unless the user
+explicitly asks to build a storyboard/scene/composed video.
+
+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\`
+- "please add visuals using OpenAI image gen" \u2192 \`vibe generate image "..." -p openai ...\`
 
 **BUILD \u2014 create new video from text intent.**
 Use \`vibe build\` with a STORYBOARD.md + DESIGN.md. The
@@ -71700,9 +71723,9 @@ bundle, then renders to MP4. Idempotent re-runs reuse cached assets.
 Use \`vibe remix\`, \`vibe edit\`, or \`vibe audio\`. One-shot,
 batch-oriented operations on a file the user already has on disk.
 
-Decision rule: if the user is starting from intent (a script, a brand,
-an idea), it's BUILD. If the user is starting from a media file, it's
-REMIX.
+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
+starting from a media file and wants it transformed, it's REMIX.
 
 ## Common workflows
 
@@ -71824,6 +71847,13 @@ overview content moved into AGENTS.md above):
 - \`/vibe-pipeline\` \u2014 YAML pipeline authoring helper (Video as Code)
 - \`/vibe-scene\` \u2014 per-scene HTML authoring + \`vibe build\`
 
+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
+\`DESIGN.md\`, or edit \`STORYBOARD.md\` unless the user explicitly asks for a
+scene, storyboard, or composed video.
+
 To install / update them later:
 
 \`\`\`bash

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vibeframe/cli",
-  "version": "0.94.1",
+  "version": "0.95.0",
   "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.94.1",
-    "@vibeframe/core": "0.94.1"
+    "@vibeframe/ai-providers": "0.95.0",
+    "@vibeframe/core": "0.95.0"
   },
   "engines": {
     "node": ">=20"