@svadmin/ui 0.72.0 → 0.74.0

package/README.md

@@ -2,38 +2,66 @@
 
 Svelte 5 admin components using semantic design tokens and Bits UI primitives.
 
+The design-system boundary is intentionally split: Bits UI owns headless
+interaction primitives, while Tailwind semantic classes and `tailwind-variants`
+own recipes and variant composition. shadcn-svelte is the authoring source for
+new components; it is not a parallel runtime library.
+
 ## CSS Integration
 
-For a host without Tailwind, import the precompiled stylesheet once:
+Import the precompiled stylesheet once:
 
 ```ts
 import '@svadmin/ui/app.css';
 ```
 
-No Tailwind plugin is required in that host. Both component styles and the
-transitional utility aliases are compiled into the published stylesheet.
+Consumers do not need Tailwind. Both component styles and the existing
+utility aliases are included in the published native stylesheet. Theme overrides
+continue to use public semantic CSS variables; nested themes use `.svadmin-theme`.
 
-For a Tailwind v4 host that also generates its own utilities:
+`app.theme.css` is retained as a native-CSS alias of `app.css`. It no longer
+emits compiler metadata. Import one UI CSS entry, not both. Old host `@source`
+directives can be removed; styles are pre-generated, not scanned at consumption.
 
-```css
-@import "tailwindcss";
-@import "@svadmin/ui/app.theme.css";
-```
+## Migration Boundary
 
-The theme entry includes the same precompiled component styles, plus the
-semantic `@theme` metadata. Import one SVAdmin CSS entry, not both.
-Theme overrides use semantic CSS variables; nested themes use `.svadmin-theme`.
+The package publishes precompiled CSS: consumers do not need to compile library
+sources. Tailwind is an authoring/build dependency only; generated APIs are not
+a new compatibility commitment.
 
-## Migration Boundary
+Existing `svadmin-u-*` aliases and compatibility rules remain native CSS. Do not
+rename or delete them mechanically. New styles should use semantic Tailwind
+classes and reviewed recipes. This is not a wholesale rewrite of every UI
+component.
+
+Button, Badge, content layouts and Surface appearance use the shared
+`tailwind-variants` registry. Public props, bindings, semantic class markers and
+null-variant semantics remain compatible. Existing component CSS state rules
+remain part of the published stylesheet.
+
+The package now permits the `tailwind-variants` recipe helper and the
+`shadcn-svelte` generator. The generator is only an authoring tool; published
+components continue to use the package's semantic tokens and Bits UI primitives.
+Panda configuration and generated helpers are no longer part of the build.
+
+## shadcn Authoring
 
-Tailwind and its animation helpers remain build-time tools. The UI package no
-longer declares `tailwind-variants` or `tailwind-merge` as runtime dependencies.
-The source still contains transitional utility aliases; this is not a complete
-rewrite to hand-authored CSS.
+Run `bun run --cwd packages/ui shadcn:add button` to generate candidate source
+under `shadcn/candidate`, not `src`. The isolated configuration uses `$lib` only
+inside that sandbox; it does not change published imports or package exports.
+Dependencies are recorded in the sandbox without installation.
 
-The public variant helpers return semantic classes for class-only composition.
-Components also expose variant and size data attributes. Primitive defaults
-live in the `components` layer so host utilities can override them.
+Review each candidate before adapting it into the existing component. Preserve
+semantic tokens, public props, data slots, bindings and accessibility enhancements.
+Convert candidate aliases to package-relative imports. Do not publish its CSS
+or utilities until they have a tested precompiled build. The generator is not an
+OpenUI runtime: schema validation, registry and controlled actions remain owned
+by the existing Surface implementation.
+
+The initial `surfaceMetric` and `surfaceTable` recipes cover every public
+variant. Surface applications opt into `styledSurfaceCatalog` and load
+`@svadmin/surface/styles.css`; see the Surface package's `STYLING.md`. Default
+Surface v1 props and the no-variant rendering path stay unchanged.
 
 ## Validation
 
@@ -43,10 +71,22 @@ bun run test
 bun run test:css
 ```
 
-The CSS tests inspect both published entries, require coverage for every
-migrated utility alias referenced by components, compile a Tailwind host, and
-verify that postprocessing is idempotent.
+CSS tests pin the original native compatibility rule tree, declarations and
+cascade order, check every referenced utility alias, verify the declarations for
+all styled recipe slots and variants, and exercise a deliberately missing rule.
+They also check nested layer flattening, isolation of generated CSS variables,
+postbuild idempotence and both public stylesheet entries.
 
 The utility migration script is an explicit maintenance operation, not a build
 step. It validates the full input set before writing and leaves dynamic
 template fragments unchanged for manual review.
+
+Reusable design contracts are exported from the package entry point. Use the
+slot helpers for shared field and surface styling instead of adding a second
+component styling system:
+
+```ts
+import { fieldClasses } from '@svadmin/ui';
+
+const classes = fieldClasses('error');
+```

package/THIRD_PARTY_NOTICES.md

@@ -0,0 +1,52 @@
+# Static CSS compatibility notices
+
+The compatibility CSS was generated once from cf6c4746578176ea773a17ef6f49f353292f7818; no compiler is required by the package. Upstream license notices are retained below.
+
+## tailwindcss
+
+MIT License
+
+Copyright (c) Tailwind Labs, Inc.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+
+
+## tw-animate-css
+
+MIT License
+
+Copyright (c) 2025 Wombosvideo
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.