@snacky/ui 0.3.6 → 0.3.8

package/README.md

@@ -2,7 +2,7 @@
 
 React implementation of the Snacky App design system - generated from the
 source of truth at `../../index.html` (via `tokens.json` / `components.json`),
-pixel-accurate to Figma (file key `4Uh4Y1fPQXu2hwq0vEXHXd`).
+pixel-accurate to Figma.
 
 This exists so AI coding tools (and humans) building new Snacky features can
 **import** these components directly instead of regenerating similar-looking
@@ -62,22 +62,7 @@ Illustration, ProductImage, ProductCard.
 Every component is diffed against `index.html`'s own Live Preview
 implementation - the code that actually renders the documentation site - not
 just the spec values in `components.json`. Where the two disagree, the
-verified implementation wins. `List`, `Header`, `BottomSheet` and `Section`
-were additionally checked against their Figma component sets directly.
-
-Two things worth knowing before you rely on them:
-
-- **`NavBar` items use `flex: 1`** to fill the container, where the site's own
-  demo hardcodes `72x72` per item. That demo only ever renders at a fixed
-  360px frame; a real nav bar has to fill the actual device width, so this is
-  a deliberate deviation rather than a mismatch.
-- **`BottomSheet` and `Section` spacing is variant-dependent by design.** Both
-  shells have since been checked against Figma, and the finding was that no
-  single shell default reproduces every variant: BottomSheet's block gap is
-  32px on Welcome, 24px on Calendar and 16px elsewhere, and Section's "Variant"
-  layout has no horizontal shell padding at all, with its header owning the
-  24px instead. The shells ship sensible defaults and expect `children` to
-  override the spacing where a specific composition needs to.
+verified implementation wins.
 
 See [CHANGELOG.md](https://github.com/rezatresnas/snacky-design-system/blob/main/packages/react-ui/CHANGELOG.md)
 for how the package got here, including the mistakes.
@@ -138,12 +123,16 @@ what is already in the bundle.
   library of your own. Either way, check the licence yourself before shipping
   - it is the one part of this that a component library cannot decide for you.
 
+- **`NavBar` items use `flex: 1`** to fill the container, where the site's demo
+  hardcodes `72x72` per item - that demo only ever renders at a fixed 360px
+  frame, so this is a deliberate deviation rather than a mismatch.
 - **Modal/Section**: the design system documents ~9 Modal "variants" and ~13
   Section "variants", but each is really the *same* shell component
   (`BottomSheet` / `Section`) with different `children` - so that's what's
   exported, matching every `code.tsx` sample exactly, rather than 22 near-
-  duplicate components. (See Verification status above on why their spacing is
-  variant-dependent.)
+  duplicate components. Their spacing is variant-dependent by design - Figma
+  uses different gaps per variant, so the shells ship sensible defaults and
+  expect `children` to override where a composition needs it.
 
 ## Keeping this in sync
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@snacky/ui",
-  "version": "0.3.6",
+  "version": "0.3.8",
   "description": "Snacky App design system - React component library. Generated from the source-of-truth design system at ../../index.html (tokens.json / components.json), pixel-accurate to Figma.",
   "license": "MIT",
   "author": "rezatresnas",