@vibeframe/mcp-server 0.113.27 → 0.113.28

package/dist/index.js

@@ -26374,8 +26374,8 @@ no unresolved unacknowledged host-agent issues.
 **Load the \`hyperframes\` skill before authoring scenes** \u2014 it encodes the
 composition rules, motion principles, type system, and visual-identity gate.
 If your agent has it installed globally it is already available; otherwise run
-\`vibe scene install-skill\` to eject a local, editable copy (\`SKILL.md\` +
-\`references/\`, gitignored by default) and read \`SKILL.md\`.
+\`vibe scene install-skill\`, which runs upstream's installer and writes
+\`.agents/skills/hyperframes/SKILL.md\`. Read that file before authoring.
 
 **Always invoke the relevant skill before authoring scenes.** Skills encode
 framework-specific patterns (GSAP timeline registration, data-attribute
@@ -26405,7 +26405,7 @@ the framework-level minimum, not the cinematic craft layer.
 - \`index.html\` \u2014 root composition (timeline)
 - \`compositions/scene-*.html\` \u2014 per-scene HTML authored by you or the agent
 - \`assets/\` \u2014 generated/canonical build media (narration audio, images, video)
-- \`references/\` \u2014 composition rule docs, only when ejected via \`vibe scene install-skill\` (not user media)
+- \`.agents/skills/hyperframes/\` \u2014 upstream composition rules, when installed here rather than globally
 - \`transcript.json\` \u2014 Whisper word-level transcript (if narration exists)
 - \`hyperframes.json\` \u2014 HF registry config (speak to both toolchains)
 - \`vibe.config.json\` \u2014 canonical VibeFrame config (providers, budget)
@@ -26469,8 +26469,9 @@ function buildSceneGitignore() {
 renders/*.mp4
 tmp/
 
-# Vendored Hyperframes skill copies \u2014 regenerable via 'vibe scene install-skill'.
-# Delete these lines if you eject and want to commit per-project customizations.
+# Hyperframes skill copies left by older VibeFrame versions. Nothing writes
+# these now - upstream's installer owns the rules and puts them under
+# .agents/skills/hyperframes/, which is yours to commit or ignore.
 /SKILL.md
 /references/
 /.claude/skills/hyperframes/
@@ -26508,12 +26509,7 @@ function describeSceneScaffold(opts) {
     ];
   }
   if (profile === "agent" || profile === "full") {
-    groups.agent = [
-      resolve8(dir, "AGENTS.md"),
-      resolve8(dir, "SKILL.md"),
-      resolve8(dir, "references"),
-      resolve8(dir, "CLAUDE.md")
-    ];
+    groups.agent = [resolve8(dir, "AGENTS.md"), resolve8(dir, "CLAUDE.md")];
   }
   return groups;
 }
@@ -306834,7 +306830,7 @@ var sceneComposePromptsTool = defineTool({
   cost: "free",
   title: "Get Scene Authoring Prompts",
   annotations: { readOnly: true, openWorld: false },
-  description: "Emit the per-beat compose plan for the host agent to author scene HTML itself. Reads STORYBOARD.md + DESIGN.md and returns each beat's outputPath + userPrompt + cues + body, plus references to the project's SKILL.md (Hyperframes rules) and DESIGN.md (visual identity). The host agent writes each compositions/scene-<id>.html file directly \u2014 VibeFrame makes NO LLM call here. Hosts that cannot write files (e.g. Claude Desktop) submit each authored beat with scene_submit instead. Pairs with scene_install_skill (Phase H1). Phase H2 of the agentic-native composer plan; the internal-LLM batch path (build) remains as a fallback for non-agent contexts.",
+  description: "Emit the per-beat compose plan for the host agent to author scene HTML itself. Reads STORYBOARD.md + DESIGN.md and returns each beat's outputPath + userPrompt + cues + body, plus the path to the Hyperframes rules (skillReference) and DESIGN.md (visual identity). The host agent writes each compositions/scene-<id>.html file directly \u2014 VibeFrame makes NO LLM call here, and there is no internal-LLM fallback: authoring is always the host agent's job. Hosts that cannot write files (e.g. Claude Desktop) submit each authored beat with scene_submit instead. Pairs with scene_install_skill, which fetches the rules from upstream when the agent does not already have them.",
   schema: sceneComposePromptsSchema,
   async execute(args, ctx) {
     const projectDir = resolve40(ctx.workingDirectory, args.projectDir);
@@ -314697,11 +314693,11 @@ narration / backdrop intent.
 1. \`vibe init my-promo --visual-style "Swiss Pulse"\` \u2014 seeds
    \`DESIGN.md\` (palette, typography, motion, transitions) plus the
    \`vibe.config.json\` / \`hyperframes.json\` / \`index.html\` scaffold.
-   In Plan H this **also installs local composition rules** at the
-   right place for your host (\`.claude/skills/hyperframes/\` for Claude
-   Code, \`.cursor/rules/hyperframes.mdc\` for Cursor, universal
-   \`SKILL.md\` for everyone else).
-2. Read \`SKILL.md\` (or the host-specific copy) \u2014 Hyperframes
+   It does **not** install the composition rules; if your agent does not
+   already have the \`hyperframes\` skill, run
+   \`vibe scene install-skill\` to fetch them from upstream into
+   \`.agents/skills/hyperframes/\`.
+2. Read \`.agents/skills/hyperframes/SKILL.md\` (or your global copy) \u2014
    framework rules, motion principles, type system, transition recipes.
 3. Read \`DESIGN.md\` \u2014 project-specific palette / typography / motion
    signature (visual identity hard-gate).
@@ -315031,9 +315027,10 @@ var META = {
     title: "Scene authoring with vibe",
     summary: "Author per-scene HTML compositions and render to MP4 (BUILD flow)",
     steps: [
-      'Run `vibe init <dir> --visual-style "<style name>"` to scaffold the project + install local composition rules.',
+      'Run `vibe init <dir> --visual-style "<style name>"` to scaffold the project.',
+      "Run `vibe scene install-skill` unless your agent already has the `hyperframes` skill; `vibe doctor` tells you which.",
       "Edit `STORYBOARD.md` with per-beat YAML cues (narration / backdrop / duration).",
-      "Read `SKILL.md` for the framework rules and `DESIGN.md` for the visual-identity hard-gate.",
+      "Read `.agents/skills/hyperframes/SKILL.md` for the framework rules and `DESIGN.md` for the visual-identity hard-gate.",
       "Run `vibe build <dir>`. With an agent host detected, the CLI emits a `needs-author` plan; the host agent authors each `compositions/scene-<id>.html` and re-invokes to render.",
       "Run `vibe build <dir> --stage sync` to assemble index.html, `vibe scene lint <dir> --fix` to validate, then `vibe render <dir>` to produce the MP4."
     ],
@@ -316071,7 +316068,7 @@ function handleCliFlags(argv, version2) {
 }
 
 // src/index.ts
-if (handleCliFlags(process.argv.slice(2), "0.113.27")) {
+if (handleCliFlags(process.argv.slice(2), "0.113.28")) {
   process.exit(0);
 }
 console.log = (...args) => console.error(...args);
@@ -316084,7 +316081,7 @@ var server = new Server(
   {
     name: "vibeframe",
     // Stamped with the package version by build.js at bundle time.
-    version: "0.113.27"
+    version: "0.113.28"
   },
   {
     capabilities: {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vibeframe/mcp-server",
-  "version": "0.113.27",
+  "version": "0.113.28",
   "description": "VibeFrame MCP Server - AI-native video editing via Model Context Protocol",
   "type": "module",
   "bin": {
@@ -60,8 +60,8 @@
     "tsx": "^4.21.0",
     "typescript": "^5.3.3",
     "vitest": "^1.2.2",
-    "@vibeframe/cli": "0.113.27",
-    "@vibeframe/core": "0.113.27"
+    "@vibeframe/core": "0.113.28",
+    "@vibeframe/cli": "0.113.28"
   },
   "engines": {
     "node": ">=20"