@lindaui/tokens 0.4.2 → 0.4.4

package/dist/index.css

@@ -264,6 +264,9 @@
   .relative {
     position: relative;
   }
+  .static {
+    position: static;
+  }
   .sticky {
     position: sticky;
   }

package/llms.txt

@@ -113,3 +113,22 @@ CSS entries include a `types` condition pointing to the shipped `src/style.d.ts`
 Strict TypeScript `noUncheckedSideEffectImports` resolves the extensionless
 `@lindaui/tokens/css` import without a consumer ambient declaration. Runtime
 CSS targets remain unchanged; import styles once at the application root.
+
+## Consumer control policy
+
+Use installed LindaUI entries for controls and canonical tokens for styling.
+Semantic HTML containers, text, labels and graphics remain appropriate. Select
+input, selection and expansion components by behavior, not only by tag name.
+The lindaui skill check reports recognized native controls with installed
+counterparts. Required native behavior needs an adjacent JSX comment with a
+nonempty reason: {/* lindaui-allow-native: reason */}. Run check in consumer CI;
+static findings do not prove browser behavior or exhaustive compliance.
+
+## Verification evidence
+
+Record the exact installed versions of ui, blocks and tokens when reporting an
+integration. A successful build or a matching latest tag alone does not prove
+that the expected packages were tested. Keep checker, typecheck/build and browser
+results separate. Published tarball integrity establishes downloaded bytes and
+package identity; consumer behavior still requires integration and interaction
+tests. See the repository acceptance matrix in CLAUDE.md for release evidence.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lindaui/tokens",
-  "version": "0.4.2",
+  "version": "0.4.4",
   "description": "Brand design tokens (OKLCH light/dark) + HeroUI v3 + Tailwind v4 compiled into a single CSS bundle.",
   "author": "Franco Carballar <francocarballar@gmail.com>",
   "license": "MIT",