@omkarux/vela 0.7.1 → 0.8.0

package/CHANGELOG.md

@@ -3,6 +3,36 @@
 All notable changes to this project are documented here.
 This project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.8.0] — 2026-09-12
+
+### Added
+- **Flutter target.** `npm run tokens` now also emits `flutter/lib/vela_tokens.dart` from the same
+  `tokens/vela.tokens.json`: primitives as `Color`s, every semantic as a field of a `VelaColors`
+  `ThemeExtension` with `light` and `dark` instances, the sizing scale as logical pixels, the type
+  ramp as `TextStyle`s (line-height ÷ size, which is what Flutter's `height` takes) and
+  `velaThemeData(Brightness)` to seed a `ThemeData`. Ships as `@omkarux/vela/tokens.dart` and as a
+  path-installable Dart package in `flutter/`. Tests hold it to the CSS's discipline: every token
+  present, every value identical to the JSON, regeneration a no-op; the file is syntax-checked
+  whenever a Dart SDK is on the machine. Nothing in the widget layer is generated — the tokens
+  travel, the components are built per stack against the same specs.
+
+## [0.7.1] — 2026-09-11
+
+### Fixed
+- 46 numeric tokens carried Figma names the library does not use (`text/h1-size` where the library
+  has `size/h1`, and the like). Found by the new read-back; corrected in the JSON, and a test now
+  holds every collection to its naming convention so the drift check can trust the names.
+
+## [0.7.0] — 2026-09-11
+
+### Added
+- **Read-back drift check.** `npm run tokens:figma:read` prints a script that reads every variable
+  out of the library, resolved per mode; `npm run tokens:figma:check <file>` diffs the result
+  against the JSON and exits 1 on any mismatch. Closes the half of the loop that only pushed.
+- Figma component builders live in source (`scripts/figma/components/*.figma.js`, run by
+  `npm run figma:build`), version stamps on every generated description, and a spec lint that
+  fails the build when a component spec loses a section the sync compiles.
+
 ## [0.6.0] — 2026-09-11
 
 ### Added

package/README.md

@@ -101,14 +101,14 @@ npm run contrast   # WCAG report for both themes
 npm run verify     # typecheck + tests + build + pack-and-consume gate
 ```
 
-## Editing tokens — one source, three targets
+## Editing tokens — one source, four targets
 
 `tokens/vela.tokens.json` is the only place a value is written. It uses the W3C Design Tokens
 format (2025.10), ships inside the package as `@omkarux/vela/tokens.json`, and everything else is
 generated from it:
 
 ```bash
-npm run tokens          # → src/styles/tokens.light.css + tokens.dark.body.css
+npm run tokens          # → src/styles/tokens.*.css + flutter/lib/vela_tokens.dart (a Flutter theme)
 npm run tokens:figma    # → a Plugin API script that creates-or-updates every Figma variable
 npm run tokens:check    # fails if the CSS was hand-edited instead of the JSON (runs in CI)
 npm run guidelines:figma # → a script that writes each spec's summary into its Figma description
@@ -130,7 +130,8 @@ Worth being precise about what travels and what doesn't:
 
 | Layer | Ports? |
 |---|---|
-| **Tokens** (`dist/tokens.css`) | **Entirely.** Plain CSS custom properties — Angular, Vue, Svelte, Rails, plain HTML. From the same source you could emit Swift, Kotlin or XML for native. |
+| **Tokens** (`dist/tokens.css`) | **Entirely.** Plain CSS custom properties — Angular, Vue, Svelte, Rails, plain HTML. |
+| **Tokens for Flutter** (`tokens.dart`) | **Entirely.** Generated from the same JSON: the primitives, a `VelaColors` `ThemeExtension` with `light` and `dark`, the sizing scale in logical pixels, the type ramp as `TextStyle`s and `velaThemeData(Brightness)`. Swift, Kotlin or XML would be the same kind of script. Widgets are not generated — they are built against `guidelines/`. |
 | **The contract** (`guidelines/`) | **Entirely.** Intent, closed prop sets, token bindings, accessibility, anti-patterns. Only the code samples are React-shaped. |
 | **Components** (`dist/index.js`) | **No.** One implementation per framework, by definition. |
 | **The contrast audit** (`npm run contrast`) | **Entirely.** It parses CSS and knows nothing about React. |

package/flutter/README.md

@@ -0,0 +1,16 @@
+# vela_tokens
+
+Vela's design tokens for Flutter. **Generated** — do not edit `lib/vela_tokens.dart` or `pubspec.yaml`.
+Edit `../tokens/vela.tokens.json` and run `npm run tokens`; the same file generates the CSS and the
+Figma library, so one token edit lands in all three.
+
+| Symbol | What it is |
+|---|---|
+| `VelaPrimitives` | The raw palette. Alias only — never bind in a widget. |
+| `VelaColors` | Every semantic colour as a field; a `ThemeExtension` with `light` and `dark` instances. |
+| `VelaSizing` | Spacing, icon, control-height, radius and focus scales in logical pixels, plus motion. |
+| `VelaTypography` | Font families, weights, sizes, and the ramp composed as `TextStyle`s. |
+| `velaThemeData(Brightness)` | A `ThemeData` seeded from the semantics, with `VelaColors` installed as an extension. |
+
+Use it as a path dependency (`vela_tokens: { path: ../vela/flutter }`) or vendor the one file.
+Widgets are not generated: build them against `../guidelines/`, which is implementation-independent.