@exxatdesignux/ui 0.5.12 → 0.5.13

package/CHANGELOG.md

@@ -1,5 +1,24 @@
 # Changelog
 
+## 0.5.13
+
+### Patch Changes
+
+- **The `sync-template-from-web.mjs` script and its publish-time workflow step are removed.** 0.5.12 retired the legacy `packages/ui/template/` (Next.js scaffold) by dropping it from `package.json#files` but kept the script that regenerated it on every publish "as a known-shaped reference". A second look confirmed the regeneration was producing a folder nothing reads — `package.json#files` excludes it, `bin/init.mjs` reads `template-vite/` only, and `npm pack --dry-run` for 0.5.12 reported 0 `template/` files in the artifact. So this release deletes the dead pipeline outright.
+  - **`packages/ui/scripts/sync-template-from-web.mjs`** — removed (~7 KB script).
+  - **`packages/ui/package.json`** — drops the `sync-template` script and the `prepack` chain entry that ran it on every publish. `prepack` is now `node ./scripts/vendor-consumer-extras.mjs && tsup` (extras still regenerated, dist still built).
+  - **`.github/workflows/publish-ui.yml`** — drops the "Sync npm starter template from apps/web" step. Shaves ~10 s off every publish run.
+- **Why this is safe:** the rule + skill propagation that customers actually consume is unchanged. `vendor:consumer-extras` regenerates `consumer-extras/cursor-rules/` from workspace `.cursor/rules/` on every publish, and `bin/init.mjs` runs `sync-extras.mjs` after copying `template-vite/` so a freshly-scaffolded customer repo gets the canonical workspace rules within seconds — overwriting whatever lived in `template-vite/.cursor/rules/`. The retired script never touched that pipeline.
+- **Stale path references the 0.5.12 release commit message claimed to fix but didn't.** Sweep done in this release:
+  - **`template-vite/.cursor/rules/exxat-nav-single-active.mdc`** — Reference paths cited `packages/ui/template/components/sidebar/...`; now `template-vite/components/sidebar/...`.
+  - **`template-vite/.cursor/rules/exxat-library-hub-header.mdc`** — `globs:` cited `packages/ui/template/components/library-*.tsx`; now `template-vite/components/library-*.tsx`.
+  - **`template-vite/src/styles/globals.css`** — header comment described the now-retired `sync-template-from-web` rewrite; rewritten to state the actual hand-maintained `@source` path and explain why `apps/web` and `template-vite/` use different relative paths.
+  - **`template-vite/components/exxat-product-logo.tsx`** + the `apps/web/` mirror — the "Reference paths" comment pointed at a deleted file in the legacy `template/`; reworded as a historical reference without a path.
+  - **`apps/web/docs/token-taxonomy.md`** — three occurrences of `apps/web/app/globals.css` / `template/app/globals.css` updated to the post-PR-6 paths (`apps/web/src/styles/globals.css` / `template-vite/src/styles/globals.css`).
+  - **`apps/web/docs/migrations/_template.md`** — the migration-author search-paths checklist pointed at the legacy folder.
+  - **`apps/web/docs/migrations/0003-globals-css-canonical.md`** — the historical paragraph claiming "the `sync-template-from-web.mjs` script already does this rewrite" reframed as legacy now that the automation is gone.
+- **Consumer-visible impact:** only customers scaffolding with `--no-extras` see corrected `template-vite/.cursor/rules/` paths in their fresh repo. The default scaffold flow (which runs `sync-extras.mjs` automatically) was already getting canonical rules from `consumer-extras/cursor-rules/` on 0.5.12 — that path is unchanged. Every component, hook, token, and CSS export is identical to 0.5.12.
+
 ## 0.5.12
 
 ### Patch Changes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@exxatdesignux/ui",
-  "version": "0.5.12",
+  "version": "0.5.13",
   "description": "Exxat shared design system (components, hooks, tokens). Monorepo setup: clone repo then pnpm bootstrap at workspace root — see github.com/ExxatDesign/Exxat-DS-Workspace README.",
   "license": "UNLICENSED",
   "author": "Exxat Design",
@@ -155,7 +155,6 @@
     "lint": "eslint src/",
     "test": "vitest run",
     "test:watch": "vitest",
-    "sync-template": "node ./scripts/sync-template-from-web.mjs",
     "vendor:consumer-extras": "node ./scripts/vendor-consumer-extras.mjs",
     "tokens:index": "node ./scripts/build-tokens-index.mjs",
     "tokens:check": "node ./scripts/build-tokens-index.mjs --check"

package/template-vite/.cursor/rules/exxat-library-hub-header.mdc

@@ -1,6 +1,6 @@
 ---
 description: Library library — folder-scoped hub header More menu must expose Customize folder; sheet on hub client
-globs: apps/web/components/library-*.tsx, packages/ui/template/components/library-*.tsx
+globs: apps/web/components/library-*.tsx, packages/ui/template-vite/components/library-*.tsx
 alwaysApply: false
 appliesTo: [react]
 ---

package/template-vite/.cursor/rules/exxat-nav-single-active.mdc

@@ -28,5 +28,5 @@ Only **one** primary sidebar row, collapsible child, or secondary-panel link may
 ## Reference
 
 - `packages/ui/src/lib/nav-active.ts`
-- `packages/ui/template/components/sidebar/app-sidebar.tsx`
-- `packages/ui/template/components/sidebar/secondary-nav.tsx`
+- `packages/ui/template-vite/components/sidebar/app-sidebar.tsx`
+- `packages/ui/template-vite/components/sidebar/secondary-nav.tsx`

package/template-vite/components/exxat-product-logo.tsx

@@ -21,9 +21,9 @@
  * removes both classes of issue.
  *
  * **Reference paths:** the mark + "Exxat" path data is the same `d=…` source
- * used by the original `ExxatOneLogo` in `packages/ui/template/components/
- * exxat-product-logo.tsx` (the pre-text-route baseline). Only the gradient
- * colours are pulled from the brand registry so new brands recolour the mark.
+ * used by the historical `ExxatOneLogo` (the pre-text-route baseline). Only
+ * the gradient colours are pulled from the brand registry so new brands
+ * recolour the mark.
  */
 
 import * as React from "react"

package/template-vite/src/styles/globals.css

@@ -1,15 +1,16 @@
 /* ==========================================================================
-   EXXAT DESIGN SYSTEM — apps/web globals.css
+   EXXAT DESIGN SYSTEM — create-exxat-app starter globals.css
    ------------------------------------------------------------------
-   Canonical theme tokens, custom variants, and base-layer styles
-   live in `@exxatdesignux/ui/globals.css`. Edits should land there
-   (the package CSS is the source of truth); this file only declares
-   the Tailwind `@source` so the consumer's location is honoured.
+   Canonical theme tokens, custom variants, and base-layer styles live
+   in `@exxatdesignux/ui/globals.css`. Edits should land there (the
+   package CSS is the source of truth); this file only declares the
+   Tailwind `@source` directives so the consumer's own utility usage
+   under `components/`, `hooks/`, `lib/`, `src/` is also picked up.
 
-   Workspace dev: `@source` points at the package's `src/` directly so
-   the IDE / Turbopack pick up new utility usages without a rebuild.
-   The `sync-template-from-web.mjs` script rewrites this path to
-   `../node_modules/@exxatdesignux/ui/src` for the npm starter.
+   The `@source` below points at `../../node_modules/@exxatdesignux/ui/src`
+   — the consumer-relative path. The workspace reference app
+   (`apps/web/src/styles/globals.css`) uses a sibling `../../../../packages/ui/src`
+   path instead so monorepo dev picks up new utilities without a rebuild.
 
    Standard: WCAG 2.1 Level AA
    ========================================================================== */