synthesisui 0.16.86 → 0.16.87

package/dist/anatomy-read.js

@@ -194,6 +194,15 @@ root) {
                     : [];
                 const t = transcribe(classes, declared);
                 parts[key] = { base: t.base, dark: t.dark, states: t.states };
+                /**
+                 * A drop on a PART is still a drop. The root path already says these out loud;
+                 * this one silently swallowed `p-spacing-sm` on a real menu popup, so the part
+                 * arrived with no padding and the not-expressed file had to discover it from
+                 * the outside (dono, 01/08).
+                 */
+                for (const cls of t.unreadable) {
+                    notes.push(`part \`${key}\`: \`${cls}\` starts like a design decision and reads as nothing - usually a typo in the source, and the element renders without it today`);
+                }
                 node_.part = key;
             }
             const text = typeof node.text === "string" ? node.text.trim() : "";

package/dist/commands/import.js

@@ -799,6 +799,31 @@ export async function takeCensus(root, opts) {
             console.log(body(line));
         console.log(body(paint.faint("Do not go looking for any of this - it is measured, and a sweep would bring back a different slice than the next one.")));
     }
+    /**
+     * THE DROPS, SAID OUT LOUD. `p-spacing-sm` on a real menu popup read as nothing and
+     * the popup shipped with no padding, invisibly - "if the compiler drops them, the drop
+     * is invisible from here" was the not-expressed file calling this exact hole (dono,
+     * 01/08). More often than not the class is malformed in THEIR source, which makes this
+     * a defect report about their code, not an apology about ours.
+     */
+    const unreadableByComponent = Object.entries(looks)
+        .filter(([, look]) => (look.unreadable ?? []).length > 0)
+        .map(([component, look]) => ({
+        component,
+        classes: look.unreadable ?? [],
+    }));
+    if (unreadableByComponent.length > 0) {
+        const total = unreadableByComponent.reduce((n, u) => n + u.classes.length, 0);
+        console.log("");
+        console.log(section("Design classes that read as nothing"));
+        console.log(body(`${total} class${total === 1 ? "" : "es"} start like a design decision and resolve to nothing - usually a typo in the source, and the element renders without that decision today. Nothing was guessed on their behalf:`));
+        for (const u of unreadableByComponent.slice(0, 8)) {
+            console.log(body(paint.faint(`  ${u.component}: ${u.classes.slice(0, 4).join(", ")}`)));
+        }
+        if (unreadableByComponent.length > 8) {
+            console.log(body(paint.faint(`  and ${unreadableByComponent.length - 8} more components`)));
+        }
+    }
     const coverageLines = describeCoverage(coverage);
     if (coverageLines.length > 0) {
         console.log("");
@@ -1590,6 +1615,7 @@ async function resolveReadParts(census, root) {
                 dark: {},
                 states: {},
                 skipped: [],
+                unreadable: [],
                 literals: [],
                 fromToken: 0,
                 fromLiteral: 0,

package/dist/doctor/transcribe.js

@@ -447,6 +447,22 @@ function resolveArbitrary(inner, declared) {
         return null;
     const v = /^var\(\s*(--[a-zA-Z0-9_-]+)\s*(?:,[^)]*)?\)$/.exec(raw);
     if (!v) {
+        /**
+         * `[--text-body-s]` IS the var() shorthand - Tailwind v3 defined it that way, so the
+         * author wrote a working thing once. v4 dropped the shorthand, which is why their
+         * inputs render at the inherited size today; the token they NAMED is still the
+         * intent, and a recipe is the rules to rebuild the component, not a photograph of
+         * the regression. Their own defect still gets reported - see `unreadable`.
+         *
+         * A bare `--name` they never declared resolves to nothing under either semantics,
+         * and carrying it would emit `font-size: --x`, which is invalid CSS.
+         */
+        if (raw.startsWith("--")) {
+            const name = raw.split(",")[0].trim();
+            return declared.has(name)
+                ? { value: tokenRefFor(name), token: name }
+                : null;
+        }
         // A literal in brackets is still a real value somebody typed.
         return /[<>{}@;]/.test(raw) ? null : { value: raw };
     }
@@ -540,12 +556,18 @@ export function readInlineStyle(source) {
 }
 /** Properties React leaves unitless, so a bare number is not pixels. */
 const UNITLESS = /^(opacity|zIndex|flex|flexGrow|flexShrink|order|lineHeight|fontWeight|zoom|columnCount|fillOpacity|strokeOpacity|animationIterationCount)$/;
+/**
+ * A prefix this reader claims to understand. A class that starts with one of these and
+ * still reads as nothing is a failed DESIGN read, not layout plumbing.
+ */
+const DESIGN_PREFIX = /^(?:p|px|py|pt|pr|pb|pl|m|mx|my|gap|rounded|text|font|bg|border|shadow|w|h|size|min-w|min-h|max-w|max-h|leading|tracking|opacity|fill|stroke)-\S/;
 export function transcribe(classes, declared) {
     const out = {
         base: {},
         states: {},
         dark: {},
         skipped: [],
+        unreadable: [],
         literals: [],
         fromToken: 0,
         fromLiteral: 0,
@@ -585,7 +607,16 @@ export function transcribe(classes, declared) {
                 out.skipped.push(cls);
             continue;
         }
-        if (!decl || !target)
+        if (!decl) {
+            // The prefix says design intent; the rest resolved to nothing. Malformed in their
+            // source more often than not - `p-spacing-sm` for `p-sm` - and a silent drop here
+            // is how a menu popup ships with no padding and nobody is told.
+            if (DESIGN_PREFIX.test(utility) && !out.unreadable.includes(cls)) {
+                out.unreadable.push(cls);
+            }
+            continue;
+        }
+        if (!target)
             continue;
         /**
          * EVERYTHING IT READS TRAVELS, literals included - as DATA.

package/dist/skill-import.js

@@ -543,6 +543,20 @@ extensions are configured at construction, not toggled later
 of their manifest and attaches it (\`"^2.1.0 in packages/ui"\`), so the rule does not go stale the
 day they upgrade and the information is not lost either.
 
+### If \`recipe_vocabulary\` is missing, the MCP registration is stale
+
+A real run reported "recipe_vocabulary and validate_recipe do not exist on this server" and
+sent every anatomy unvalidated - the repo's \`.mcp.json\` pinned \`synthesisui@0.16.78\` while
+the import itself ran unpinned at latest: **two CLI versions in one repo, in one run** (dono,
+01/08). Before concluding a tool does not exist, check the registration:
+
+\`\`\`json
+"args": ["synthesisui@latest", "mcp"]
+\`\`\`
+
+Tell the person to fix the pin and restart the server. Do not work around a stale server by
+skipping validation - unvalidated is how correct work arrives as nothing.
+
 ### Ask what a recipe can hold, BEFORE you write one
 
 \`\`\`
@@ -669,6 +683,26 @@ found them wastes a turn and risks contradicting the measurement:
 What is still yours: the anatomy tree, the part names, the frontiers, the roles, the
 concept, and the rules that are not about a class name.
 
+### A scale's INTENT is a rule, and their docs already wrote it
+
+A three-step spacing scale with documented meaning - sm "close UI relationships", md
+"standard internal padding", lg "layout gutters" - carries a law nothing else expresses:
+**this system has exactly three steps, and a fourth is a mistake.** A real import read the
+scale and lost the sentence (dono, 01/08).
+
+When their docs (a \`Geometry.mdx\`, a design-tokens page, comments beside the \`@theme\`)
+state what a step is FOR, send it as system-wide rules - \`applies: []\`, \`fact: true\`, the
+doc as evidence:
+
+\`\`\`
+this system's spacing has exactly three steps - sm for close relationships inside a
+control, md for standard internal padding, lg for layout gutters. A fourth step is a
+mistake, not a gap (Geometry.mdx)
+\`\`\`
+
+\`applies: []\` is what makes it reach CLAUDE.md and every prompt after - the same route the
+architecture rule travels.
+
 ### How much to send
 
 Send an anatomy for **every component with visible structure**, which is nearly all of them. A

package/package.json

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