An open source design system that's fully customizable and agent ready
TypeScript
docs(spec): integration verify keeps partial theme export sets packable (#7059)
Joey50cc119530db
diff --git a/docs/specs/AST-050-app-themes/spec.md b/docs/specs/AST-050-app-themes/spec.mdindex b05b6a5fbe..3866812ac4 100644--- a/docs/specs/AST-050-app-themes/spec.md+++ b/docs/specs/AST-050-app-themes/spec.md@@ -136,8 +136,11 @@ described.stylesheet; it never falls back to copying or to runtime source.`integration add theme` MUST write these exports, and `integration verify`MUST fail when an exported theme module, stylesheet, or font stylesheet does- not resolve from the packed tarball, or when a built module or stylesheet does- not match its source.+ not resolve from the packed tarball, or when a theme exports both its built+ module and its stylesheet and either one does not match its source. A theme+ that exports only part of that pair, or none of it, stays packable when every+ path it exports resolves, and `integration verify` warns about what is missing+ or does not match.- **FR8 — Local themes are added like package themes.** The project's localthemes root is `src/themes`: the folder the copying `theme add` writes intoand the folder `theme eject` copies into by default, also in a project with no@@ -290,7 +293,7 @@ unchanged.| FR3, FR4 | Theme record tests | import, remove, use; removing the default; using a theme not added; a hand-edited module; two modules; no module with `astryx.theme`; `ASTRYX_THEME` set | The default is not an added theme, a hand-edited or second module is overwritten, theme state is written outside the module, `astryx.theme` stops resolving, or `ASTRYX_THEME` changes which theme a command reads || FR5 | Response type and text field tests | every command; first import | An import emits `theme.add`, a field has no text projection, or the first import shows no wiring || FR6 | Eject tests against the copy fixtures | bundled, integration, and nested-file themes; eject then list | Copied source bytes or copy receipt fields differ from the copying `theme add`, the descriptor is missing, or the ejected theme is not listed as local |-| FR7, FR8 | Integration verify and real provider-to-consumer tests | multi-theme package; single-theme package; missing export; font stylesheet missing from the tarball; stale build; a local theme sharing a package theme's slug; local themes in a project with no `src` folder | A theme without a resolvable built module is imported, verify passes a stale or missing export, a shared slug imports the package theme without `--package`, the copying `theme add` resolves a local theme, or local themes are looked for outside `src/themes` |+| FR7, FR8 | Integration verify and real provider-to-consumer tests | multi-theme package; single-theme package; missing export; font stylesheet missing from the tarball; stale build; partial export set; a local theme sharing a package theme's slug; local themes in a project with no `src` folder | A theme without a resolvable built module is imported, verify passes a stale complete pair or an unresolved export, verify fails a partial export set whose exports resolve, a shared slug imports the package theme without `--package`, the copying `theme add` resolves a local theme, or local themes are looked for outside `src/themes` || FR9 | Generated module tests | package and local themes | The module imports source || FR10 | List tests | added, default, bundled, package, local | A listed theme lacks its app fields || FR11 | Doctor tests, one planted fault per check | each of the ten faults; a correct app | A check passes on its fault, or passes without positive evidence |