synthesisui 0.16.27 → 0.16.28

package/dist/doctor/scan.js

@@ -69,8 +69,14 @@ const FONT = /font-family\s*:\s*([^;}\n]+)/g;
  * time; the value normalizer makes `.3s` and `300ms` one literal, so the
  * system's own duration token gets NAMED, not just flagged.
  */
-const MOTION_PROP = /\b(?:transition|animation)(?:-(?:duration|delay|timing-function)|Duration|Delay|TimingFunction)?\s*:\s*["'`]?([^;}"'`\n]*)/g;
-const TIME_LITERAL = /(\d*\.?\d+)(ms|s)\b/g;
+// `]` ends the value too: Tailwind's arbitrary syntax (`[animation:...]`)
+// closes with it, and without the stop the "value" swallowed the rest of the
+// className - first real report blamed classes that sat beside the animation.
+const MOTION_PROP = /\b(?:transition|animation)(?:-(?:duration|delay|timing-function)|Duration|Delay|TimingFunction)?\s*:\s*["'`]?([^;}\]"'`\n]*)/g;
+// Trailing guard instead of `\b`: in arbitrary syntax spaces are `_`, which is
+// a word char, so `200ms_ease` failed `\b` and the hand-written clock passed
+// unseen (found on the generated button.tsx, first field run of the family).
+const TIME_LITERAL = /(\d*\.?\d+)(ms|s)(?![a-zA-Z0-9%])/g;
 const BEZIER = /cubic-bezier\([^)]*\)/g;
 /** `duration-300`, `duration-[350ms]`, `delay-75` - Tailwind's stock clock. */
 const TW_TIME = /\b(?:duration|delay)-(?:\[([^\]]+)\]|(\d+)\b)/g;
@@ -344,8 +350,15 @@ export function scanSource(file, source, table) {
             }
             // A `ds-*` animation name that the installed css never declares renders
             // as NOTHING, silently - the keyframe cousin of a phantom token.
+            //
+            // Two guards, both from the first field run (soft-test, 29/07): the
+            // lookbehind keeps `var(--ds-motion-durations-base)` from reading as a
+            // keyframe named after the token (`-` before `ds-` means it is a custom
+            // property, not a name); and the name must END on a word - the greedy
+            // run used to stop at Tailwind's `_` separator and report a truncated
+            // `ds-soft-test-` as phantom while the real keyframe existed.
             if (table.keyframes.size > 0) {
-                for (const w of value.matchAll(/\b(ds-[a-z0-9-]+)\b/g)) {
+                for (const w of value.matchAll(/(?<![\w-])(ds-[a-z0-9]+(?:-[a-z0-9]+)*)/g)) {
                     if (!table.keyframes.has(w[1]))
                         phantoms.push({ name: `@keyframes ${w[1]}`, line: at });
                 }

package/dist/guide.js

@@ -147,10 +147,18 @@ ${depLines.join("\n")}
         loop: "ambient loop · infinite - decorative, use sparingly",
         attention: "attention · one shot, only when asked",
     };
+    // Promise only what the ARTIFACTS actually contain, not what this CLI
+    // version knows how to describe. First field run (soft-test, 29/07): a
+    // newer CLI wrote "already compiled as ready utilities" against a theme.css
+    // an older server had compiled without --animate-* keys - the agent
+    // verified `animate-rise` emitted nothing and filed the GUIDE's own promise
+    // as a gap. The artifacts travel in this payload; reading them is free.
+    const hasAnimateKeys = /--animate-/.test(payload.artifacts["theme.css"] ?? "");
+    const hasReducedMotionFloor = Object.values(payload.artifacts).some((css) => /prefers-reduced-motion/.test(css ?? ""));
     const keyframeLines = Object.entries(motion.keyframes).map(([kname, frames]) => {
         const kf = frames;
         const intent = classifyKeyframe(kname, kf);
-        const usage = hasTailwind
+        const usage = hasTailwind && hasAnimateKeys
             ? `\`animate-${kebab(kname)}\``
             : `\`animation: ${animationShorthand(`ds-${slug}-${kebab(kname)}`, intent, isFullRotation(kf))}\``;
         return `- ${usage} - ${INTENT_LINE[intent]} (${describeKeyframe(kf)})`;
@@ -398,7 +406,7 @@ ${keyframeLines.length > 0
 
 The base is QUIET: nothing moves until someone asks. When they do, animation is **selection
 from this list**, not improvisation - these are the system's own animations, already compiled
-into ${hasTailwind ? "`theme.css` as ready utilities" : `\`tokens.css\` as \`@keyframes ds-${slug}-<name>\``}, each on the clock its intent calls for:
+into ${hasTailwind && hasAnimateKeys ? "`theme.css` as ready utilities" : `\`tokens.css\` as \`@keyframes ds-${slug}-<name>\``}, each on the clock its intent calls for:
 
 ${keyframeLines.join("\n")}
 ${patternLines.length > 0
@@ -409,8 +417,9 @@ ${patternLines.join("\n")}
 `
             : ""}
 Rules: entrances run once, never on scroll-loop; ambient loops are decoration, one per view is
-plenty; \`prefers-reduced-motion\` is already honored in the shipped CSS (a floor collapses all
-animations) - don't undo it. If a request needs a motion this vocabulary lacks, do NOT hand-roll
+plenty; ${hasReducedMotionFloor
+            ? "`prefers-reduced-motion` is already honored in the shipped CSS (a floor collapses all\nanimations) - don't undo it"
+            : "honor `prefers-reduced-motion` yourself (wrap animations in `motion-safe:` or a media query) - this build of the CSS ships no floor"}. If a request needs a motion this vocabulary lacks, do NOT hand-roll
 \`@keyframes\` or raw durations: file it (\`request_token\` via MCP, or \`synthesisui request\`) and
 tell the person what you chose from the vocabulary instead.`
         : ""}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "synthesisui",
-  "version": "0.16.27",
+  "version": "0.16.28",
   "description": "Bring SynthesisUI design systems into any project - tokens, typed components, whole pages and an agent-ready CLAUDE.md manifest.",
   "type": "module",
   "bin": {