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

package/AGENTS.md

@@ -13,6 +13,24 @@ and how the underlying engine is built, see the repo root's
 
 ## 1. Install + setup
 
+```sh
+npx @kbach/cli init
+```
+
+Automates everything below — installs `@kbach/react-native`, patches (or
+creates) `babel.config.js` via a format-preserving codemod (handles both
+Expo's function-export form and React Native CLI's plain object-export
+form), and on React Native CLI offers to run the native rebuild right
+there. Safe to re-run at any time (idempotent — reports "already has the
+kbach babel plugin" rather than duplicating the entry). See
+[`packages/cli/AGENTS.md`](../cli/AGENTS.md) for exactly what it detects
+and changes, and what it does when the codemod can't safely apply
+(prints the same manual snippet shown below, rather than guessing).
+
+The manual steps below are both the CLI's own fallback and the accurate
+reference for what it actually does — start here if you're wiring this
+up by hand, or the CLI reported it couldn't:
+
 ```sh
 npm install @kbach/react-native@beta
 ```
@@ -255,18 +273,10 @@ colors.alpha(colors.blue[6], 30);
 colors.get('brand');   // a custom color, typed as plain `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.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
+(§5.1 of the root AGENTS.md) — define a color as mode-aware in
+`kbach.config.js` if you want it to differ by mode.
 
 `colors.brand` (a custom flat color) is typed `string | ColorScale`
 because the same object also serves shade families and TS can't tell them

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kbach/react-native",
-  "version": "1.0.0-beta.49",
+  "version": "1.0.0-beta.50",
   "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",