@nadicodeai/design-system 12.1.110 → 12.1.112

package/README.md

@@ -1,6 +1,6 @@
 # nadicode Design System
 
-The `@nadicodeai/design-system` package. [`DESIGN.md`](./DESIGN.md) is nadicode's design system and its only design authority: every token and every rule for applying it. This README says how to consume the package and how the build turns `DESIGN.md` into what it ships.
+The `@nadicodeai/design-system` package. [`DESIGN.md`](./DESIGN.md) is nadicode's design system and its design authority: every token, the visual direction and the rules every component and page shares. A component's own contract is the usage page in its source in `@nadicodeai/ui`. This README says how to consume the package and how the build turns `DESIGN.md` into what it ships.
 
 This README is a package map and the setup guide for static or non-React consumers. React consumers use the UI package's stylesheet and follow [`packages/ui/README.md`](../ui/README.md); they do not compose design-system stylesheets themselves.
 
@@ -99,9 +99,9 @@ Consumer overrides belong in an explicit later layer:
 
 ## How the build works
 
-`npm run build -w @nadicodeai/design-system` reads `DESIGN.md` twice: the
-`@google/design.md` CLI exports the YAML front matter, and
-`scripts/sd/design-tokens-fence.ts` reads the one `json design-tokens` fence.
+`npm run build -w @nadicodeai/design-system` reads two sources: the
+`@google/design.md` CLI exports `DESIGN.md`'s YAML front matter, and
+`scripts/sd/token-extension.ts` reads the token extension, `src/tokens/extension.tokens.json`.
 `scripts/sd/compose-token-graph.ts` joins them into the single `nadicode` token
 graph and checks that every alias resolves and points the allowed way (`core`
 reaches nothing outside itself; `semantic` names only `core`; a register reaches
@@ -116,9 +116,13 @@ The source graph under `src/css/` is bundled into three public stylesheets:
 `css` (everything), `css/tokens` (the token layer alone) and `css/host` (for a
 host with base styles of its own). `src/css/index.css` declares the cascade's
 layer order.
-Generated files and `dist/` are outputs: edit `DESIGN.md` and rebuild, never the
-output. CI rebuilds and fails when a committed generated file differs from the
-fresh build, and `tests/guards/` holds the structural checks on every output.
+Generated files and `dist/` are outputs, which git does not track: edit
+`DESIGN.md` or `src/tokens/extension.tokens.json` and rebuild, never the output.
+Every install builds them through the root `prepare`, and `tests/guards/` holds
+the structural checks on every output.
+The favicons are the exception: `generate:favicons` writes them and git tracks
+them. A consumer reaches any output through the package's `exports`, never a
+path into `dist/` or `src/`.
 
 ### Worked example (static HTML)
 

package/dist/tokens/nadicode.dtcg-resolved.json

@@ -1,6 +1,6 @@
 {
   "$schema": "https://www.designtokens.org/schemas/2025.10/format.json",
-  "$description": "nadicode's design system and its only design authority: the tokens and the rules every component, website section, and product screen in the website, the Portal, the Nadia desktop app, and the Alveare desktop app builds on.",
+  "$description": "nadicode's design system and its design authority for tokens, visual direction and the rules every component and page shares: every component, website section, and product screen in the website, the Portal, the Nadia desktop app, and the Alveare desktop app builds on it. A component's own contract is the usage page in its source in @nadicodeai/ui.",
   "nadicode": {
     "core": {
       "color": {

package/dist/tokens/nadicode.dtcg.json

@@ -1,6 +1,6 @@
 {
   "$schema": "https://www.designtokens.org/schemas/2025.10/format.json",
-  "$description": "nadicode's design system and its only design authority: the tokens and the rules every component, website section, and product screen in the website, the Portal, the Nadia desktop app, and the Alveare desktop app builds on.",
+  "$description": "nadicode's design system and its design authority for tokens, visual direction and the rules every component and page shares: every component, website section, and product screen in the website, the Portal, the Nadia desktop app, and the Alveare desktop app builds on it. A component's own contract is the usage page in its source in @nadicodeai/ui.",
   "nadicode": {
     "core": {
       "color": {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nadicodeai/design-system",
-  "version": "12.1.110",
+  "version": "12.1.112",
   "type": "module",
   "publishConfig": {
     "access": "public"
@@ -173,6 +173,7 @@
     "src/assets/logo-geometry.js",
     "src/assets/house-icons.js",
     "src/assets/empty",
+    "src/tokens",
     "src/assets/fonts",
     "data",
     "dist"