@ekanos/ui 0.1.2 → 0.1.4

package/README.md

@@ -33,19 +33,18 @@ One subpath per component, mirroring the `@kit/ui` names:
 | `@ekanos/ui/spinner`         | `Spinner`                                                                                                     |
 | `@ekanos/ui/ai-prompt-input` | `PromptInput` compound components for AI ask surfaces                                                         |
 
-Most source files are a thin `export * from '@kit/ui/<name>'` — for those,
-`@kit/ui` stays the single source of truth. At build time the `@kit/ui` code is
-inlined into `dist/` so the published artifact has no workspace dependencies
-(`scripts/pack-test.mjs` fails the build if any `@kit/` specifier leaks).
+Most source files are a thin re-export of the internal `@kit/ui` library — for
+those, `@kit/ui` stays the single source of truth. At build time that code is
+inlined into `dist/` so the published artifact has no workspace dependencies;
+`pnpm --filter @ekanos/ui pack:test` fails the build if any `@kit/` specifier
+leaks into the tarball.
 
 Three subpaths — `if`, `trans`, and `spinner` — are instead implemented
-natively in `src/_impl/`. Their `@kit/ui` counterparts live in
-`packages/ui/src/makerkit/`, which is Makerkit-authored code from the
-commercial Turbo starter this monorepo was built on; publishing it under this
+natively here. Their internal counterparts are Makerkit-authored code from the
+commercial Turbo starter this monorepo was built on; publishing that under this
 package's MIT license would purport to grant reuse rights we do not hold. The
-implementations here are original, and `pack:test` fails the build if any
-`packages/ui/src/makerkit` source is ever inlined into `dist/`. Inside the
-monorepo, first-party code keeps using `@kit/ui` as before.
+implementations shipped here are original, and `pack:test` fails the build if
+any Makerkit-authored source is ever inlined into `dist/`.
 
 ## Styling
 
@@ -135,7 +134,7 @@ tokens, and nine of its ten elevation levels, are deliberately absent.
 The build enforces this in both directions: it re-compiles the same class
 strings against Fusion's **full** token map and fails if a component has started
 using a token this package doesn't ship (which would otherwise emit no CSS at
-all, silently). See `scripts/build-css.mjs`.
+all, silently). The CSS build enforces it.
 
 ### Fonts
 
@@ -246,12 +245,12 @@ runtime is a declared dependency of this package.
 ## Building / verifying
 
 ```bash
-pnpm --filter @ekanos/ui build      # tsup → dist/, then scripts/build-css.mjs → the stylesheets
-pnpm --filter @ekanos/ui pack:test  # clean-room publish gate (see scripts/pack-test.mjs)
+pnpm --filter @ekanos/ui build      # tsup → dist/, then the CSS build → the stylesheets
+pnpm --filter @ekanos/ui pack:test  # clean-room publish gate
 ```
 
 The build runs in two stages, in this order for a reason: `tsup` bundles the
-components, then `scripts/build-css.mjs` scans the *built* `dist/*.js` for class
+components, then the CSS build scans the *built* `dist/*.js` for class
 strings and compiles exactly those through Tailwind. Deriving the utility set
 from the build output rather than a hand-kept list is what makes it impossible
 to add a component whose classes have no CSS.