@kbach/react-native 1.0.0-beta.48 → 1.0.0-beta.49

package/AGENTS.md

@@ -255,11 +255,23 @@ colors.alpha(colors.blue[6], 30);
 colors.get('brand');   // a custom color, typed as plain `string`
 ```
 
-`colors.blue[n]` auto-mirrors to shade `13 - n` in dark mode (palette
-convention: 1 = lightest, 12 = darkest). `colors.brand` (a custom flat
-color) is typed `string | ColorScale` because the same object also serves
-shade families and TS can't tell them apart statically — use
-`colors.get(name)` when you need a guaranteed `string`.
+**Correction — no automatic shade-mirroring exists.** An earlier version
+of this doc claimed `colors.blue[n]` auto-mirrors to shade `13 - n` in
+dark mode; confirmed false against the actual code (`useColors.ts`'s own
+doc comment: "fully manual, no automatic shade-shifting or other
+assumption about what a 'dark variant' should be") — this was never
+implemented in this package's history, not a regression. `colors.blue[6]`
+returns the SAME value in both light and dark mode unless `blue-6` itself
+is defined in the theme as a `{ light, dark }` pair (§4.1 of the root
+AGENTS.md) — there is no built-in "flip the shade number" behavior at all.
+If you want a color to differ by mode, define it as mode-aware in
+`kbach.config.js`; reaching for a different numbered shade yourself is a
+manual, app-level choice this hook has no opinion on.
+
+`colors.brand` (a custom flat color) is typed `string | ColorScale`
+because the same object also serves shade families and TS can't tell them
+apart statically — use `colors.get(name)` when you need a guaranteed
+`string`.
 
 ## 10. Unknown-class warnings
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kbach/react-native",
-  "version": "1.0.0-beta.48",
+  "version": "1.0.0-beta.49",
   "description": "Kbach's utility-class styling engine for React Native — the same class names as @kbach/react, resolved to a StyleSheet-ready style object via a Kotlin/JNI TurboModule (native), the same WASM engine @kbach/react uses (Expo Web / react-native-web), or a pure-JS fallback engine (Expo Go). Ships its own native Android module — one npm install, no separate native package. Beta. Native is Android-only (no iOS bridge yet); works with the React Native CLI, an Expo dev client, AND Expo Go (a reduced-coverage pure-JS fallback, since Expo Go can't load any custom native module).",
   "keywords": [
     "css",