@csszyx/mcp-server 0.15.1 → 0.15.3

package/llms-full.txt

@@ -769,11 +769,12 @@ a template like `` `gap-${n}` ``) leaves the merge in mangled form, matching
 the mangled CSS. The lookup is single-pass and idempotent — already-mangled
 tokens, authored literals, and external (non-csszyx) class names pass through
 unchanged — and it is an identity in dev or on unmangled builds. Code that
-INSPECTS a className for a utility by its original spelling must decode first:
-`szDecode(token)` (from `@csszyx/runtime`) maps a mangled token back to its
-original name and is identity everywhere else, so
-`className.split(/\s+/).some(t => szDecode(t).startsWith('w-'))` is safe on
-every build shape.
+INSPECTS a className for a utility must not read the spelling: `has(className,
+'w')` (from `@csszyx/runtime`) decodes each token through the registry and
+strips its variant before matching, so it answers the same on every build
+shape. `szDecode(token)` maps one mangled token back to its original name — and
+returns the whole original, variant prefix included, so a hand-rolled
+`startsWith('w-')` on it is false for `md:w-full`.
 
 ## `szs` — slot map for a component's internal parts
 
@@ -3902,8 +3903,8 @@ import {
   stripSzProps,
 } from "@csszyx/runtime";
 
-// Partition: outer = border-outward (margin/position/border/sizing/bg/shadow/transform/visibility),
-//            inner = border-inward (padding/overflow/display/layout/gap/text/paint-inside/interactivity)
+// Partition: outer = border-outward (margin/position/border/ring/sizing/bg/shadow/transform/visibility),
+//            inner = border-inward (padding/overflow/display/flex/grid/gap/text/interaction)
 const { outer, inner } = splitBox("m-4 px-2 md:flex");
 // outer: "m-4"   inner: "px-2 md:flex"
 
@@ -4086,9 +4087,13 @@ the built HTML carries no executable inline script and a strict CSP
 If an `sz`-generated utility also appears as a static string or template quasi in a
 source-level `class` or `className` attribute/property (including a `clsx(...)`
 expression), csszyx keeps that class unmangled. This ensures raw and `sz` consumers
-continue to reference the same emitted rule. Use `mangleExclude` when the class is
-only visible through an imported constant, DOM selector/class API, ignored
-dependency, downstream macro, or another value unavailable to the source scan.
+continue to reference the same emitted rule. When something else depends on the
+class NAME — a stylesheet matching by attribute (`[class*="bg-tag"]`), a DOM
+query, a class assembled outside any visible `className` — list it in
+`production.manglePreserve` (exact name, or a prefix ending in `*`); the
+hybrid-hazard warning prints a paste-ready value. `production.mangleExclude` is
+the other switch: it keeps the allocator from producing a token equal to a short
+class in third-party CSS, and never keeps a csszyx class from being renamed.
 
 Final-output class mangling is available in Vite, Webpack, and Rollup. The esbuild
 adapter keeps class names readable (and warns when `production.mangle: true` is

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@csszyx/mcp-server",
-  "version": "0.15.1",
+  "version": "0.15.3",
   "description": "Model Context Protocol (MCP) server for csszyx — enables AI agents to understand and generate sz props",
   "license": "MIT",
   "type": "module",
@@ -28,18 +28,18 @@
     "node": "^22.18.0 || >=24.11.0"
   },
   "dependencies": {
-    "@modelcontextprotocol/sdk": "^1.29.0",
-    "zod": "^4.4.3",
-    "@csszyx/cli": "0.15.1",
-    "@csszyx/compiler": "0.15.1",
-    "@csszyx/unplugin": "0.15.1"
+    "@csszyx/cli": "0.15.3",
+    "@csszyx/compiler": "0.15.3",
+    "@csszyx/unplugin": "0.15.3",
+    "@modelcontextprotocol/sdk": "^1.30.0",
+    "zod": "^4.4.3"
   },
   "devDependencies": {
     "@types/node": "^22.20.1",
-    "tsx": "^4.23.11",
+    "tsx": "^4.23.12",
     "typescript": "^6.0.3",
     "unbuild": "^3.6.1",
-    "vitest": "^4.1.10"
+    "vitest": "^4.1.11"
   },
   "keywords": [
     "csszyx",