vectorvesper 2.1.0 → 2.1.1

package/dist/hooks.json

@@ -1,7 +1,7 @@
 {
   "version": "1.0.0",
   "engineVersion": "1.0.2",
-  "generatedAt": "2026-08-02T16:02:47.693Z",
+  "generatedAt": "2026-08-09T14:27:32.779Z",
   "contractLevel": "full",
   "hooks": [
     {
@@ -95,7 +95,7 @@
         "exposeImplementation": false,
         "reason": "Reproducing this hook's implementation makes the consumer run a private requestAnimationFrame loop instead of joining the shared FrameConductor. That silently removes the coordination, scheduling and frame-budget governance the runtime exists to provide, and nothing errors when it happens. Copying is a correctness bug, not just a licensing question.",
         "correctUsage": "Install @vectorvesper/motion and import the hook. Never inline, reimplement, or paste an equivalent.",
-        "readingSource": "If you want to read the real implementation, you can: @vectorvesper/motion is MIT, ships unminified, and its sourcemaps carry the original TypeScript in sourcesContent — so node_modules/@vectorvesper/motion/dist has every line, no reconstruction needed. Read it freely to understand or debug. It changes nothing about the output: what you write is still an import. A copy compiles, passes review and silently runs its own rAF loop outside the conductor, so 'I read the source and it looked simple' is exactly how this bug gets shipped. Start with the `mechanism` field above — it is usually the whole answer, and it is current with the version you have."
+        "readingSource": "The `mechanism` field above is the answer to almost every 'how does this actually work' question, and it is written for the version you have. Prefer it. The published package is minified and ships no sourcemaps, so node_modules is a poor place to read from — but @vectorvesper/motion is MIT, so the real source is readable in the repository if you want it. Either way it changes nothing about the output: what you write is still an import. A copy compiles, passes review and silently runs its own rAF loop outside the conductor, so 'I read the source and it looked simple' is exactly how that bug gets shipped."
       }
     },
     {
@@ -195,7 +195,7 @@
         "exposeImplementation": false,
         "reason": "Reproducing this hook's implementation makes the consumer run a private requestAnimationFrame loop instead of joining the shared FrameConductor. That silently removes the coordination, scheduling and frame-budget governance the runtime exists to provide, and nothing errors when it happens. Copying is a correctness bug, not just a licensing question.",
         "correctUsage": "Install @vectorvesper/motion and import the hook. Never inline, reimplement, or paste an equivalent.",
-        "readingSource": "If you want to read the real implementation, you can: @vectorvesper/motion is MIT, ships unminified, and its sourcemaps carry the original TypeScript in sourcesContent — so node_modules/@vectorvesper/motion/dist has every line, no reconstruction needed. Read it freely to understand or debug. It changes nothing about the output: what you write is still an import. A copy compiles, passes review and silently runs its own rAF loop outside the conductor, so 'I read the source and it looked simple' is exactly how this bug gets shipped. Start with the `mechanism` field above — it is usually the whole answer, and it is current with the version you have."
+        "readingSource": "The `mechanism` field above is the answer to almost every 'how does this actually work' question, and it is written for the version you have. Prefer it. The published package is minified and ships no sourcemaps, so node_modules is a poor place to read from — but @vectorvesper/motion is MIT, so the real source is readable in the repository if you want it. Either way it changes nothing about the output: what you write is still an import. A copy compiles, passes review and silently runs its own rAF loop outside the conductor, so 'I read the source and it looked simple' is exactly how that bug gets shipped."
       }
     },
     {
@@ -342,7 +342,7 @@
         "exposeImplementation": false,
         "reason": "Reproducing this hook's implementation makes the consumer run a private requestAnimationFrame loop instead of joining the shared FrameConductor. That silently removes the coordination, scheduling and frame-budget governance the runtime exists to provide, and nothing errors when it happens. Copying is a correctness bug, not just a licensing question.",
         "correctUsage": "Install @vectorvesper/motion and import the hook. Never inline, reimplement, or paste an equivalent.",
-        "readingSource": "If you want to read the real implementation, you can: @vectorvesper/motion is MIT, ships unminified, and its sourcemaps carry the original TypeScript in sourcesContent — so node_modules/@vectorvesper/motion/dist has every line, no reconstruction needed. Read it freely to understand or debug. It changes nothing about the output: what you write is still an import. A copy compiles, passes review and silently runs its own rAF loop outside the conductor, so 'I read the source and it looked simple' is exactly how this bug gets shipped. Start with the `mechanism` field above — it is usually the whole answer, and it is current with the version you have."
+        "readingSource": "The `mechanism` field above is the answer to almost every 'how does this actually work' question, and it is written for the version you have. Prefer it. The published package is minified and ships no sourcemaps, so node_modules is a poor place to read from — but @vectorvesper/motion is MIT, so the real source is readable in the repository if you want it. Either way it changes nothing about the output: what you write is still an import. A copy compiles, passes review and silently runs its own rAF loop outside the conductor, so 'I read the source and it looked simple' is exactly how that bug gets shipped."
       }
     },
     {
@@ -450,7 +450,7 @@
         "exposeImplementation": false,
         "reason": "Reproducing this hook's implementation makes the consumer run a private requestAnimationFrame loop instead of joining the shared FrameConductor. That silently removes the coordination, scheduling and frame-budget governance the runtime exists to provide, and nothing errors when it happens. Copying is a correctness bug, not just a licensing question.",
         "correctUsage": "Install @vectorvesper/motion and import the hook. Never inline, reimplement, or paste an equivalent.",
-        "readingSource": "If you want to read the real implementation, you can: @vectorvesper/motion is MIT, ships unminified, and its sourcemaps carry the original TypeScript in sourcesContent — so node_modules/@vectorvesper/motion/dist has every line, no reconstruction needed. Read it freely to understand or debug. It changes nothing about the output: what you write is still an import. A copy compiles, passes review and silently runs its own rAF loop outside the conductor, so 'I read the source and it looked simple' is exactly how this bug gets shipped. Start with the `mechanism` field above — it is usually the whole answer, and it is current with the version you have."
+        "readingSource": "The `mechanism` field above is the answer to almost every 'how does this actually work' question, and it is written for the version you have. Prefer it. The published package is minified and ships no sourcemaps, so node_modules is a poor place to read from — but @vectorvesper/motion is MIT, so the real source is readable in the repository if you want it. Either way it changes nothing about the output: what you write is still an import. A copy compiles, passes review and silently runs its own rAF loop outside the conductor, so 'I read the source and it looked simple' is exactly how that bug gets shipped."
       }
     },
     {
@@ -559,7 +559,7 @@
         "exposeImplementation": false,
         "reason": "Reproducing this hook's implementation makes the consumer run a private requestAnimationFrame loop instead of joining the shared FrameConductor. That silently removes the coordination, scheduling and frame-budget governance the runtime exists to provide, and nothing errors when it happens. Copying is a correctness bug, not just a licensing question.",
         "correctUsage": "Install @vectorvesper/motion and import the hook. Never inline, reimplement, or paste an equivalent.",
-        "readingSource": "If you want to read the real implementation, you can: @vectorvesper/motion is MIT, ships unminified, and its sourcemaps carry the original TypeScript in sourcesContent — so node_modules/@vectorvesper/motion/dist has every line, no reconstruction needed. Read it freely to understand or debug. It changes nothing about the output: what you write is still an import. A copy compiles, passes review and silently runs its own rAF loop outside the conductor, so 'I read the source and it looked simple' is exactly how this bug gets shipped. Start with the `mechanism` field above — it is usually the whole answer, and it is current with the version you have."
+        "readingSource": "The `mechanism` field above is the answer to almost every 'how does this actually work' question, and it is written for the version you have. Prefer it. The published package is minified and ships no sourcemaps, so node_modules is a poor place to read from — but @vectorvesper/motion is MIT, so the real source is readable in the repository if you want it. Either way it changes nothing about the output: what you write is still an import. A copy compiles, passes review and silently runs its own rAF loop outside the conductor, so 'I read the source and it looked simple' is exactly how that bug gets shipped."
       }
     },
     {
@@ -677,7 +677,7 @@
         "exposeImplementation": false,
         "reason": "Reproducing this hook's implementation makes the consumer run a private requestAnimationFrame loop instead of joining the shared FrameConductor. That silently removes the coordination, scheduling and frame-budget governance the runtime exists to provide, and nothing errors when it happens. Copying is a correctness bug, not just a licensing question.",
         "correctUsage": "Install @vectorvesper/motion and import the hook. Never inline, reimplement, or paste an equivalent.",
-        "readingSource": "If you want to read the real implementation, you can: @vectorvesper/motion is MIT, ships unminified, and its sourcemaps carry the original TypeScript in sourcesContent — so node_modules/@vectorvesper/motion/dist has every line, no reconstruction needed. Read it freely to understand or debug. It changes nothing about the output: what you write is still an import. A copy compiles, passes review and silently runs its own rAF loop outside the conductor, so 'I read the source and it looked simple' is exactly how this bug gets shipped. Start with the `mechanism` field above — it is usually the whole answer, and it is current with the version you have."
+        "readingSource": "The `mechanism` field above is the answer to almost every 'how does this actually work' question, and it is written for the version you have. Prefer it. The published package is minified and ships no sourcemaps, so node_modules is a poor place to read from — but @vectorvesper/motion is MIT, so the real source is readable in the repository if you want it. Either way it changes nothing about the output: what you write is still an import. A copy compiles, passes review and silently runs its own rAF loop outside the conductor, so 'I read the source and it looked simple' is exactly how that bug gets shipped."
       }
     },
     {
@@ -804,7 +804,7 @@
         "exposeImplementation": false,
         "reason": "Reproducing this hook's implementation makes the consumer run a private requestAnimationFrame loop instead of joining the shared FrameConductor. That silently removes the coordination, scheduling and frame-budget governance the runtime exists to provide, and nothing errors when it happens. Copying is a correctness bug, not just a licensing question.",
         "correctUsage": "Install @vectorvesper/motion and import the hook. Never inline, reimplement, or paste an equivalent.",
-        "readingSource": "If you want to read the real implementation, you can: @vectorvesper/motion is MIT, ships unminified, and its sourcemaps carry the original TypeScript in sourcesContent — so node_modules/@vectorvesper/motion/dist has every line, no reconstruction needed. Read it freely to understand or debug. It changes nothing about the output: what you write is still an import. A copy compiles, passes review and silently runs its own rAF loop outside the conductor, so 'I read the source and it looked simple' is exactly how this bug gets shipped. Start with the `mechanism` field above — it is usually the whole answer, and it is current with the version you have."
+        "readingSource": "The `mechanism` field above is the answer to almost every 'how does this actually work' question, and it is written for the version you have. Prefer it. The published package is minified and ships no sourcemaps, so node_modules is a poor place to read from — but @vectorvesper/motion is MIT, so the real source is readable in the repository if you want it. Either way it changes nothing about the output: what you write is still an import. A copy compiles, passes review and silently runs its own rAF loop outside the conductor, so 'I read the source and it looked simple' is exactly how that bug gets shipped."
       }
     },
     {
@@ -941,7 +941,7 @@
         "exposeImplementation": false,
         "reason": "Reproducing this hook's implementation makes the consumer run a private requestAnimationFrame loop instead of joining the shared FrameConductor. That silently removes the coordination, scheduling and frame-budget governance the runtime exists to provide, and nothing errors when it happens. Copying is a correctness bug, not just a licensing question.",
         "correctUsage": "Install @vectorvesper/motion and import the hook. Never inline, reimplement, or paste an equivalent.",
-        "readingSource": "If you want to read the real implementation, you can: @vectorvesper/motion is MIT, ships unminified, and its sourcemaps carry the original TypeScript in sourcesContent — so node_modules/@vectorvesper/motion/dist has every line, no reconstruction needed. Read it freely to understand or debug. It changes nothing about the output: what you write is still an import. A copy compiles, passes review and silently runs its own rAF loop outside the conductor, so 'I read the source and it looked simple' is exactly how this bug gets shipped. Start with the `mechanism` field above — it is usually the whole answer, and it is current with the version you have."
+        "readingSource": "The `mechanism` field above is the answer to almost every 'how does this actually work' question, and it is written for the version you have. Prefer it. The published package is minified and ships no sourcemaps, so node_modules is a poor place to read from — but @vectorvesper/motion is MIT, so the real source is readable in the repository if you want it. Either way it changes nothing about the output: what you write is still an import. A copy compiles, passes review and silently runs its own rAF loop outside the conductor, so 'I read the source and it looked simple' is exactly how that bug gets shipped."
       }
     },
     {
@@ -1077,7 +1077,7 @@
         "exposeImplementation": false,
         "reason": "Reproducing this hook's implementation makes the consumer run a private requestAnimationFrame loop instead of joining the shared FrameConductor. That silently removes the coordination, scheduling and frame-budget governance the runtime exists to provide, and nothing errors when it happens. Copying is a correctness bug, not just a licensing question.",
         "correctUsage": "Install @vectorvesper/motion and import the hook. Never inline, reimplement, or paste an equivalent.",
-        "readingSource": "If you want to read the real implementation, you can: @vectorvesper/motion is MIT, ships unminified, and its sourcemaps carry the original TypeScript in sourcesContent — so node_modules/@vectorvesper/motion/dist has every line, no reconstruction needed. Read it freely to understand or debug. It changes nothing about the output: what you write is still an import. A copy compiles, passes review and silently runs its own rAF loop outside the conductor, so 'I read the source and it looked simple' is exactly how this bug gets shipped. Start with the `mechanism` field above — it is usually the whole answer, and it is current with the version you have."
+        "readingSource": "The `mechanism` field above is the answer to almost every 'how does this actually work' question, and it is written for the version you have. Prefer it. The published package is minified and ships no sourcemaps, so node_modules is a poor place to read from — but @vectorvesper/motion is MIT, so the real source is readable in the repository if you want it. Either way it changes nothing about the output: what you write is still an import. A copy compiles, passes review and silently runs its own rAF loop outside the conductor, so 'I read the source and it looked simple' is exactly how that bug gets shipped."
       }
     },
     {
@@ -1212,7 +1212,7 @@
         "exposeImplementation": false,
         "reason": "Reproducing this hook's implementation makes the consumer run a private requestAnimationFrame loop instead of joining the shared FrameConductor. That silently removes the coordination, scheduling and frame-budget governance the runtime exists to provide, and nothing errors when it happens. Copying is a correctness bug, not just a licensing question.",
         "correctUsage": "Install @vectorvesper/motion and import the hook. Never inline, reimplement, or paste an equivalent.",
-        "readingSource": "If you want to read the real implementation, you can: @vectorvesper/motion is MIT, ships unminified, and its sourcemaps carry the original TypeScript in sourcesContent — so node_modules/@vectorvesper/motion/dist has every line, no reconstruction needed. Read it freely to understand or debug. It changes nothing about the output: what you write is still an import. A copy compiles, passes review and silently runs its own rAF loop outside the conductor, so 'I read the source and it looked simple' is exactly how this bug gets shipped. Start with the `mechanism` field above — it is usually the whole answer, and it is current with the version you have."
+        "readingSource": "The `mechanism` field above is the answer to almost every 'how does this actually work' question, and it is written for the version you have. Prefer it. The published package is minified and ships no sourcemaps, so node_modules is a poor place to read from — but @vectorvesper/motion is MIT, so the real source is readable in the repository if you want it. Either way it changes nothing about the output: what you write is still an import. A copy compiles, passes review and silently runs its own rAF loop outside the conductor, so 'I read the source and it looked simple' is exactly how that bug gets shipped."
       }
     },
     {
@@ -1364,7 +1364,7 @@
         "exposeImplementation": false,
         "reason": "Reproducing this hook's implementation makes the consumer run a private requestAnimationFrame loop instead of joining the shared FrameConductor. That silently removes the coordination, scheduling and frame-budget governance the runtime exists to provide, and nothing errors when it happens. Copying is a correctness bug, not just a licensing question.",
         "correctUsage": "Install @vectorvesper/motion and import the hook. Never inline, reimplement, or paste an equivalent.",
-        "readingSource": "If you want to read the real implementation, you can: @vectorvesper/motion is MIT, ships unminified, and its sourcemaps carry the original TypeScript in sourcesContent — so node_modules/@vectorvesper/motion/dist has every line, no reconstruction needed. Read it freely to understand or debug. It changes nothing about the output: what you write is still an import. A copy compiles, passes review and silently runs its own rAF loop outside the conductor, so 'I read the source and it looked simple' is exactly how this bug gets shipped. Start with the `mechanism` field above — it is usually the whole answer, and it is current with the version you have."
+        "readingSource": "The `mechanism` field above is the answer to almost every 'how does this actually work' question, and it is written for the version you have. Prefer it. The published package is minified and ships no sourcemaps, so node_modules is a poor place to read from — but @vectorvesper/motion is MIT, so the real source is readable in the repository if you want it. Either way it changes nothing about the output: what you write is still an import. A copy compiles, passes review and silently runs its own rAF loop outside the conductor, so 'I read the source and it looked simple' is exactly how that bug gets shipped."
       }
     },
     {
@@ -1506,7 +1506,7 @@
         "exposeImplementation": false,
         "reason": "Reproducing this hook's implementation makes the consumer run a private requestAnimationFrame loop instead of joining the shared FrameConductor. That silently removes the coordination, scheduling and frame-budget governance the runtime exists to provide, and nothing errors when it happens. Copying is a correctness bug, not just a licensing question.",
         "correctUsage": "Install @vectorvesper/motion and import the hook. Never inline, reimplement, or paste an equivalent.",
-        "readingSource": "If you want to read the real implementation, you can: @vectorvesper/motion is MIT, ships unminified, and its sourcemaps carry the original TypeScript in sourcesContent — so node_modules/@vectorvesper/motion/dist has every line, no reconstruction needed. Read it freely to understand or debug. It changes nothing about the output: what you write is still an import. A copy compiles, passes review and silently runs its own rAF loop outside the conductor, so 'I read the source and it looked simple' is exactly how this bug gets shipped. Start with the `mechanism` field above — it is usually the whole answer, and it is current with the version you have."
+        "readingSource": "The `mechanism` field above is the answer to almost every 'how does this actually work' question, and it is written for the version you have. Prefer it. The published package is minified and ships no sourcemaps, so node_modules is a poor place to read from — but @vectorvesper/motion is MIT, so the real source is readable in the repository if you want it. Either way it changes nothing about the output: what you write is still an import. A copy compiles, passes review and silently runs its own rAF loop outside the conductor, so 'I read the source and it looked simple' is exactly how that bug gets shipped."
       }
     },
     {
@@ -1673,7 +1673,7 @@
         "exposeImplementation": false,
         "reason": "Reproducing this hook's implementation makes the consumer run a private requestAnimationFrame loop instead of joining the shared FrameConductor. That silently removes the coordination, scheduling and frame-budget governance the runtime exists to provide, and nothing errors when it happens. Copying is a correctness bug, not just a licensing question.",
         "correctUsage": "Install @vectorvesper/motion and import the hook. Never inline, reimplement, or paste an equivalent.",
-        "readingSource": "If you want to read the real implementation, you can: @vectorvesper/motion is MIT, ships unminified, and its sourcemaps carry the original TypeScript in sourcesContent — so node_modules/@vectorvesper/motion/dist has every line, no reconstruction needed. Read it freely to understand or debug. It changes nothing about the output: what you write is still an import. A copy compiles, passes review and silently runs its own rAF loop outside the conductor, so 'I read the source and it looked simple' is exactly how this bug gets shipped. Start with the `mechanism` field above — it is usually the whole answer, and it is current with the version you have."
+        "readingSource": "The `mechanism` field above is the answer to almost every 'how does this actually work' question, and it is written for the version you have. Prefer it. The published package is minified and ships no sourcemaps, so node_modules is a poor place to read from — but @vectorvesper/motion is MIT, so the real source is readable in the repository if you want it. Either way it changes nothing about the output: what you write is still an import. A copy compiles, passes review and silently runs its own rAF loop outside the conductor, so 'I read the source and it looked simple' is exactly how that bug gets shipped."
       }
     },
     {
@@ -1795,7 +1795,7 @@
         "exposeImplementation": false,
         "reason": "Reproducing this hook's implementation makes the consumer run a private requestAnimationFrame loop instead of joining the shared FrameConductor. That silently removes the coordination, scheduling and frame-budget governance the runtime exists to provide, and nothing errors when it happens. Copying is a correctness bug, not just a licensing question.",
         "correctUsage": "Install @vectorvesper/motion and import the hook. Never inline, reimplement, or paste an equivalent.",
-        "readingSource": "If you want to read the real implementation, you can: @vectorvesper/motion is MIT, ships unminified, and its sourcemaps carry the original TypeScript in sourcesContent — so node_modules/@vectorvesper/motion/dist has every line, no reconstruction needed. Read it freely to understand or debug. It changes nothing about the output: what you write is still an import. A copy compiles, passes review and silently runs its own rAF loop outside the conductor, so 'I read the source and it looked simple' is exactly how this bug gets shipped. Start with the `mechanism` field above — it is usually the whole answer, and it is current with the version you have."
+        "readingSource": "The `mechanism` field above is the answer to almost every 'how does this actually work' question, and it is written for the version you have. Prefer it. The published package is minified and ships no sourcemaps, so node_modules is a poor place to read from — but @vectorvesper/motion is MIT, so the real source is readable in the repository if you want it. Either way it changes nothing about the output: what you write is still an import. A copy compiles, passes review and silently runs its own rAF loop outside the conductor, so 'I read the source and it looked simple' is exactly how that bug gets shipped."
       }
     },
     {
@@ -1903,7 +1903,7 @@
         "exposeImplementation": false,
         "reason": "Reproducing this hook's implementation makes the consumer run a private requestAnimationFrame loop instead of joining the shared FrameConductor. That silently removes the coordination, scheduling and frame-budget governance the runtime exists to provide, and nothing errors when it happens. Copying is a correctness bug, not just a licensing question.",
         "correctUsage": "Install @vectorvesper/motion and import the hook. Never inline, reimplement, or paste an equivalent.",
-        "readingSource": "If you want to read the real implementation, you can: @vectorvesper/motion is MIT, ships unminified, and its sourcemaps carry the original TypeScript in sourcesContent — so node_modules/@vectorvesper/motion/dist has every line, no reconstruction needed. Read it freely to understand or debug. It changes nothing about the output: what you write is still an import. A copy compiles, passes review and silently runs its own rAF loop outside the conductor, so 'I read the source and it looked simple' is exactly how this bug gets shipped. Start with the `mechanism` field above — it is usually the whole answer, and it is current with the version you have."
+        "readingSource": "The `mechanism` field above is the answer to almost every 'how does this actually work' question, and it is written for the version you have. Prefer it. The published package is minified and ships no sourcemaps, so node_modules is a poor place to read from — but @vectorvesper/motion is MIT, so the real source is readable in the repository if you want it. Either way it changes nothing about the output: what you write is still an import. A copy compiles, passes review and silently runs its own rAF loop outside the conductor, so 'I read the source and it looked simple' is exactly how that bug gets shipped."
       }
     },
     {
@@ -2064,7 +2064,7 @@
         "exposeImplementation": false,
         "reason": "Reproducing this hook's implementation makes the consumer run a private requestAnimationFrame loop instead of joining the shared FrameConductor. That silently removes the coordination, scheduling and frame-budget governance the runtime exists to provide, and nothing errors when it happens. Copying is a correctness bug, not just a licensing question.",
         "correctUsage": "Install @vectorvesper/motion and import the hook. Never inline, reimplement, or paste an equivalent.",
-        "readingSource": "If you want to read the real implementation, you can: @vectorvesper/motion is MIT, ships unminified, and its sourcemaps carry the original TypeScript in sourcesContent — so node_modules/@vectorvesper/motion/dist has every line, no reconstruction needed. Read it freely to understand or debug. It changes nothing about the output: what you write is still an import. A copy compiles, passes review and silently runs its own rAF loop outside the conductor, so 'I read the source and it looked simple' is exactly how this bug gets shipped. Start with the `mechanism` field above — it is usually the whole answer, and it is current with the version you have."
+        "readingSource": "The `mechanism` field above is the answer to almost every 'how does this actually work' question, and it is written for the version you have. Prefer it. The published package is minified and ships no sourcemaps, so node_modules is a poor place to read from — but @vectorvesper/motion is MIT, so the real source is readable in the repository if you want it. Either way it changes nothing about the output: what you write is still an import. A copy compiles, passes review and silently runs its own rAF loop outside the conductor, so 'I read the source and it looked simple' is exactly how that bug gets shipped."
       }
     }
   ],

package/dist/index.js

@@ -993,7 +993,7 @@ Remove ${slug}
 import fs6 from "fs";
 import path6 from "path";
 import pc8 from "picocolors";
-var CLI_VERSION = true ? "2.1.0" : "0.0.0-dev";
+var CLI_VERSION = true ? "2.1.1" : "0.0.0-dev";
 async function infoCommand() {
   console.log(pc8.bold(pc8.cyan("\nVector Vesper Diagnostics\n")));
   const projectInfo = detectProject();
@@ -1291,7 +1291,7 @@ async function whoamiCommand() {
 }
 
 // src/index.ts
-var version = true ? "2.1.0" : "0.0.0-dev";
+var version = true ? "2.1.1" : "0.0.0-dev";
 var program = new Command();
 program.name("vv").description("Vector Vesper CLI \u2014 add visual components to your React project").version(version).option("--verbose", "Show detailed debug output").hook("preAction", (thisCommand) => {
   const opts = thisCommand.opts();
@@ -1330,7 +1330,7 @@ program.command("whoami", { hidden: true }).description("Show current authentica
   await whoamiCommand();
 });
 program.command("mcp [action]").description("Run as an MCP server (stdio) for AI coding agents. `vv mcp status` checks the setup.").option("--stdio", "Force server mode even from an interactive terminal").action(async (action, options) => {
-  const { mcpCommand } = await import("./mcp-OURIIFET.js");
+  const { mcpCommand } = await import("./mcp-FCM3FZSK.js");
   await mcpCommand(action, options);
 });
 process.on("unhandledRejection", (error) => {

package/dist/{mcp-OURIIFET.js → mcp-FCM3FZSK.js}

@@ -7,7 +7,7 @@ import {
 
 // src/commands/mcp.ts
 import pc from "picocolors";
-var VERSION = true ? "2.1.0" : "0.0.0-dev";
+var VERSION = true ? "2.1.1" : "0.0.0-dev";
 var CONFIG_SNIPPET = `{
   "mcpServers": {
     "vectorvesper": {
@@ -101,7 +101,7 @@ ${pc.red("\u2717")} Unknown argument "${action}" for \`vv mcp\`.
     return;
   }
   protectStdout();
-  const { startMcpServer } = await import("./server-ROPGTSDI.js");
+  const { startMcpServer } = await import("./server-WQ564YNA.js");
   try {
     await startMcpServer();
   } catch (error) {

package/dist/{server-ROPGTSDI.js → server-WQ564YNA.js}

@@ -51,6 +51,8 @@ function collect(ast, traverse) {
     usesUseGSAP: false,
     usesR3F: false,
     raf: [],
+    rafSelfScheduling: [],
+    rafUnresolved: 0,
     hasCancelRaf: false,
     addEventListener: [],
     hasRemoveEventListener: false,
@@ -113,10 +115,14 @@ function collect(ast, traverse) {
     const line = node.loc?.start.line ?? 0;
     const argPaths = typeof p.get === "function" ? p.get("arguments") : [];
     switch (name) {
-      case "requestAnimationFrame":
+      case "requestAnimationFrame": {
         f.raf.push(line);
-        scanHotCallback(resolveFunction(argPaths[0]), "a requestAnimationFrame loop", true);
+        const cb = resolveFunction(argPaths[0]);
+        if (!cb) f.rafUnresolved++;
+        else if (callbackSchedulesAnotherFrame(cb, traverse)) f.rafSelfScheduling.push(line);
+        scanHotCallback(cb, "a requestAnimationFrame loop", true);
         break;
+      }
       case "cancelAnimationFrame":
         f.hasCancelRaf = true;
         break;
@@ -211,6 +217,9 @@ function collect(ast, traverse) {
     },
     Identifier(p) {
       const name = p.node.name;
+      if (/^(reducedMotion|prefersReducedMotion|prefersReduced)$/.test(name)) {
+        f.hasReducedMotionGuard = true;
+      }
       if (!BROWSER_GLOBALS.has(name)) return;
       if (fnDepth !== 0) return;
       const parent = p.parent;
@@ -265,8 +274,27 @@ function checkClientBoundary(f, file, framework) {
   }
   return out;
 }
+function callbackSchedulesAnotherFrame(cbNode, traverse) {
+  const isDeclaration = cbNode.type === "FunctionDeclaration";
+  const isExpression = cbNode.type === "ArrowFunctionExpression" || cbNode.type === "FunctionExpression";
+  if (!isDeclaration && !isExpression) return false;
+  const statement = isDeclaration ? cbNode : { type: "ExpressionStatement", expression: cbNode };
+  let found = false;
+  traverse(
+    { type: "File", program: { type: "Program", body: [statement], directives: [] } },
+    {
+      CallExpression(p) {
+        if (calleeName(p.node.callee) === "requestAnimationFrame") found = true;
+      },
+      OptionalCallExpression(p) {
+        if (calleeName(p.node.callee) === "requestAnimationFrame") found = true;
+      }
+    }
+  );
+  return found;
+}
 function isRafLoop(f) {
-  return f.raf.length >= 2;
+  return f.rafSelfScheduling.length > 0 || f.rafUnresolved >= 2;
 }
 function checkOrphanRaf(f, file) {
   if (!isRafLoop(f)) return [];
@@ -275,8 +303,10 @@ function checkOrphanRaf(f, file) {
       rule: "orphan-raf",
       severity: "warning",
       file,
-      line: f.raf[0],
-      message: `This file runs its own \`requestAnimationFrame\` loop${f.raf.length > 1 ? ` (\xD7${f.raf.length})` : ""}. Independent loops each schedule their own frame and cannot shed work under load \u2014 the coordination the runtime exists to provide is lost.`,
+      // Point at the self-scheduling call when we found one — that is the loop
+      // itself, not merely the first rAF in the file.
+      line: f.rafSelfScheduling[0] ?? f.raf[0],
+      message: `This file runs its own \`requestAnimationFrame\` loop${f.rafSelfScheduling.length > 1 ? ` (\xD7${f.rafSelfScheduling.length})` : ""}. Independent loops each schedule their own frame and cannot shed work under load \u2014 the coordination the runtime exists to provide is lost.`,
       fix: "Drive the animation from the shared conductor (`getConductor().subscribe(...)` in `@vectorvesper/motion`) or a hook that already joins it, so it shares one frame budget.",
       nudge: "Call `list_hooks` \u2014 a sensor or governor primitive may already cover this without a hand-written loop."
     }
@@ -400,7 +430,7 @@ async function checkMotionFiles(files, cwd) {
 }
 
 // src/mcp/server.ts
-var VERSION = true ? "2.1.0" : "0.0.0-dev";
+var VERSION = true ? "2.1.1" : "0.0.0-dev";
 function text(body) {
   return { content: [{ type: "text", text: body }] };
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "vectorvesper",
-  "version": "2.1.0",
+  "version": "2.1.1",
   "description": "Add WebGL, React Three Fiber & advanced motion components to your project via CLI.",
   "type": "module",
   "license": "MIT",