@reqvire-org/ads 0.3.17 → 0.3.20

package/docs/ARCHITECTURE.md

@@ -67,6 +67,32 @@ state mechanics. Patterns own reusable layout and composition. Application
 containers provide domain data, routing, application effects, and callbacks through public
 APIs.
 
+A component provides one cohesive UI capability. A pattern arranges capabilities
+into a reusable structure or workflow; a layout part may arrange content slots.
+Components may compose other components/controllers, and patterns may compose
+patterns. Import count, element count and implementation size do not decide the
+layer. Scenarios may compose public UI and development review helpers to demonstrate their
+subject without becoming production patterns.
+
+Patterns are production application UI. Development-only framing, demo controls
+and token renderers belong in project-owned `review/`, with a separate
+`reviewEntry` (default `review/index.ts`) and `${publicAlias}/review` import alias.
+They are absent from the product barrel and catalogue. Guards reject production
+dependencies on review code, types and styles; review source keeps normal styling,
+token and public product-contract checks. Scenarios exercise the real production
+implementation through fixtures. The [portable review guide](../skills/ads-designer/references/review.md)
+defines guarded owners, build isolation and migration steps. Review rendering
+stays inside the App iframe; it adds no project execution to the host shell.
+
+Core guards reject component runtime dependencies on patterns/composition through
+resolved imports, re-exports and helpers. Patterns consume public component
+contracts rather than private implementation symbols or rendered style hooks;
+documented non-state customization variables remain available. Source tracing
+distinguishes styling a private part from reading ancestor context for the
+pattern's own arrangement. Application and development dependencies retain their
+separate boundaries. The portable skill-local [layer guide](../skills/ads-designer/references/layers.md)
+explains repairs and analysis limits; semantic classification still needs review.
+
 The Data pillar describes design values; business data is a separate input to
 the UX contract. Application adapters own live business-data loading,
 authentication, stores, routing, caching and refresh policy. Components and
@@ -155,6 +181,19 @@ values; source guards alone cannot establish extraction correctness. The
 skill-local [atomic styling guide](../skills/ads-designer/references/atomic-styles.md#preserve-custom-property-arithmetic-during-extraction)
 documents integration and source-workaround semantics.
 
+The resolver also preserves complete `@property` registrations and their
+conditional at-rule context for atomic `css`/`styled`. Their descriptors are schema
+metadata, not separate atomic declarations. CSS-tree validates CSS value grammar;
+PostCSS supplies source/at-rule structure. Registered names have one owner and a
+stable schema across its modules, because registration is document-global. Runtime
+variables are registered in owned Linaria; shared or namespaced design tokens are
+registered beside their real value definitions. Base resets and fonts cannot own
+registrations. Descriptor literals are narrowly permitted where CSS requires an
+independent initial value; ordinary visual assignments remain token-governed.
+MCP serves these styles to the sandboxed App document. Registration metadata
+neither creates new token definitions nor replaces token sample coverage.
+Compiled-CSS and browser tests verify interpolation in React and Preact Apps.
+
 ## Public APIs preserve the boundary
 
 The application and project-owned preview scenarios consume a project's public ADS entry. Components
@@ -220,6 +259,13 @@ external bases still require declared CSP origins. This belongs to document
 loading and changes no project link or scenario handler. External hosts control
 their own document-loading and CSP behavior.
 
+The proxy and App sandbox permit native forms (`allow-forms`), including the
+legacy nested widget. This lets browser constraint validation and `submit`
+handlers run for clicks, Enter and `requestSubmit()`. Client-side handlers retain
+their own `preventDefault()` behavior. The App stays opaque; CSP
+`form-action 'none'` blocks native action requests without suppressing submit
+handlers. Hosts outside ADS choose their own sandbox and CSP permissions.
+
 The project compiler publishes a versioned dependency graph: shared runtime and
 foundation assets, plus independently addressable scenario modules. Inside the
 App, a resource loader obtains the selected dependency closure through MCP,
@@ -289,12 +335,12 @@ real public implementation. It mounts independently, without opening a showcase
 page or initializing the application's router, store or services first.
 
 Scenarios and their fixtures live beside the tokens, component or pattern they exercise.
-Demo framing belongs to public review/layout patterns; component props describe
+Demo framing belongs to development-only review helpers; component props describe
 intentional product behavior and visual variants.
 Token scenarios choose real token names and sample inputs; a project-owned
-review pattern applies the foundation variables. The tool contains no project
+review renderer applies the foundation variables. The tool contains no project
 token list, sample templates or assumed visual identity. Even an initial token
-scenario uses a public project-owned review pattern to apply its declared samples;
+scenario uses a project-owned development review renderer to apply its declared samples;
 a definitions-only inspector does not establish preview coverage.
 Larger scenarios live under `composition/`. They use the same public screen
 patterns as production: application adapters supply live data and effects;
@@ -445,6 +491,20 @@ Another run replaces that check's resource access; candidate evidence never
 certifies live source. Detailed usage lives in the portable skill-local
 [evidence guide](../skills/ads-designer/references/evidence.md).
 
+MCP delivery is separate from validation: verification and mutation controllers
+use complete results to decide acceptance. Their MCP replies contain counts,
+bounded acceptance, at most three failure previews and a result ID in at most
+4 KiB of UTF-8 JSON. `ads_results` reads saved outcomes, diagnostics and other
+sections without rerunning checks. Pages have at most 20 rows and 8 KiB of JSON;
+truncated records support bounded text ranges. Discovery and investigation
+sections use the same paging budget. Cursors bind the query and result/revision;
+superseded IDs fail explicitly instead of silently returning another run.
+Only the latest verification and mutation snapshots are retained, each at most
+8 MiB under `.ds/tool-results/`. Oversized reports retain a summary with an
+explicit unavailable-details warning. Storage/notification failure cannot change
+an accepted edit's applied state. These are payload byte budgets, not tokenizer
+estimates; MCP compatibility text may duplicate structured JSON on the wire.
+
 Edits stay focused without requiring entire file bodies in model context. Peer units and
 unrelated owners remain outside the selected unit's edit boundary. Shared foundation,
 branding and guides have their own units. Shared credits and text license notices
@@ -511,7 +571,7 @@ For concrete instructions, use:
 
 Token preview completeness has two checks. Static guards require explicit fixture
 bindings (`token`, CSS `property`, and project-selected `probe`) consumed by a public
-review pattern. The App then verifies rendered samples in the actual browser by
+review renderer. The App then verifies rendered samples in the actual browser by
 probing those bindings and restoring them. The tool supplies no token/property
 classification or visual sample palette. A source build alone is not a rendered
 verification, and the browser check does not judge design quality.

package/docs/BEHAVIORS.md

@@ -308,8 +308,20 @@ Guarantees report passing only when all their checks have current passing eviden
 Passing applies to those cases and profiles, not every application state.
 
 Results expose structured `failure` boundaries and explicit `acceptance` scope.
-Use `ads_investigate({unit,check})` for the latest compact investigation, including
-isolated dry runs; `ads://project/investigations` lists available entries. Exact
+MCP execution replies contain counts, bounded acceptance, at most three failure
+previews and a `resultId` (4 KiB UTF-8 JSON maximum). Use `ads_results` to read
+selected `outcomes`, `checks`, `diagnostics` or other sections without execution.
+Pages default to 10 rows, allow at most 20 and stay within 8 KiB; follow
+`nextCursor` with identical selection/status. Truncated records provide
+`recordIndex` for exact `offset`/`chars` ranges. Only the latest verification and
+mutation snapshots are retained, independently, at most 8 MiB each. Replaced IDs
+fail explicitly. Validation still uses complete internal outcomes.
+
+Use `ads_investigate({unit,check,runId})` with an outcome's exact IDs for its compact
+summary (4 KiB maximum); details, requests, browser errors and artifact metadata are separate
+paged sections (8 KiB maximum). Truncated records support exact text ranges with
+the recorded run ID. Saved outcomes describe completion time; compare current
+`ads_behaviors` revisions for freshness. It includes isolated dry runs; `ads://project/investigations` lists available entries. Exact
 input and observed preview revisions, failing step/source, startup viewport,
 failed startup requests and available project-recorded artifacts keep diagnosis
 separate from an inferred component defect. No artifact is invented or test
@@ -354,3 +366,10 @@ Keep ESM modules and explicit imports. Avoid an eagerly imported controller
 registry. Tree shaking and shared chunks follow the project bundler: class methods,
 side effects, global CSS and dynamic maps can retain extra code. Inspect emitted
 resources instead of assuming a controller produces a minimal bundle.
+
+Development-only `review/<Owner>` units may register the same guarantee/check
+contracts for review presentation and controls. Subjects can name that owner's
+separate review API or local headless helpers; checks still run registered project
+profiles and can refer to an existing real scenario. This grants no production
+API, catalogue entry, `covers` credit or runtime import permission. See the
+[portable review guide](../skills/ads-designer/references/review.md).

package/docs/CHANGELOG.md

@@ -1,5 +1,45 @@
 # Changelog
 
+## Unreleased
+
+## 0.3.20
+
+- Preserve the motion-review checklist separately from the development review-layer
+  guide; both remain self-contained in the motion skill. Version 0.3.19 was tagged
+  but publication was cancelled before this correction.
+
+- Separate project-owned review UI from production patterns. Add `review/` owners,
+  a configurable development entry and derived `/review` alias, guarded companion
+  exports and review contracts. Preserve real component/token render evidence,
+  block production imports and verify review assets stay out of product bundles.
+  Move the working showcase and empty starter helpers to the new layer; publish
+  self-contained migration guidance in all skills and `ads://guides/review`.
+- Enable native form validation and submit events across the showcase, diagnostic
+  explorer and legacy App iframe layers. Retain opaque App origins and block
+  native action requests through CSP. Cover click/Enter submission, custom/native
+  validation and no-network behavior in generic React, Preact and HTML Apps.
+- Enforce runtime component dependency direction and public component contracts
+  for patterns through aliases, re-exports and helpers. Reject proven private
+  style-hook/variable access while preserving ancestor-context layout and documented
+  customization. Publish portable layer guidance in every skill and through MCP.
+
+## 0.3.18
+
+- Preserve complete typed `@property` registrations through atomic css/styled
+  extraction, conditional rules and CSS minification. Validate descriptors with
+  CSS-tree, enforce runtime/token ownership and naming conflicts, and retain
+  ordinary style-token gates. Verify dummy interpolation in React/Preact MCP Apps.
+- Sync all skill references for registrations and selector-owned native
+  composition; keep implementation independent of any imported component library.
+
+- Deliver verification and guarded-edit replies as 4 KiB JSON summaries with
+  counts, acceptance and result IDs. Page outcomes, diagnostics, logs and captures
+  through `ads_results`; retain only the latest verification and mutation snapshots.
+  Keep complete internal validation independent of delivery.
+- Page behavior discovery and investigation details; bind cursors to their query
+  and recorded run, reject superseded evidence, and document selective retrieval
+  in every portable skill. Keep artifacts separate from tool JSON.
+
 ## 0.3.17
 
 - Recognize native semantic composition through source-verified runtime Linaria

package/docs/GUIDE.md

@@ -495,10 +495,10 @@ export default function Scenario() { return <Button>{fixture.label}</Button>; }
 IDs derive from filenames; do not maintain another registry or hand-assigned IDs.
 Token scenarios live beside foundation CSS under the configured token directory.
 The starter includes `tokens/Foundation.scenario.tsx` and its local fixture for
-a project-owned token review pattern. Keep its presentation in that pattern:
+a project-owned token review renderer. Keep its presentation in that pattern:
 
 ```tsx
-import { TokenSamples } from "@ds";
+import { TokenSamples } from "@ds/review";
 import { fixture } from "./Typography.fixture";
 export const scenario = { title: fixture.title, covers: ["TokenSamples"], samples: fixture.samples };
 export default function Scenario() { return <TokenSamples {...fixture} />; }
@@ -723,6 +723,7 @@ inspection errors fail the check. These guards read files and never delete them.
   "dsDir": "design-system",
   "publicAlias": "@ds",
   "publicEntry": "index.ts",
+  "reviewEntry": "review/index.ts",
   "stylesEntry": "styles.css",
   "tokenDir": "tokens",
   "inlineStyleFiles": [],

package/docs/MCP.md

@@ -1,5 +1,11 @@
 # ADS over MCP
 
+For component/pattern classification and dependency/style boundary diagnostics,
+read `ads://guides/layers`. A component supplies one cohesive UI capability; a
+pattern arranges capabilities into reusable structures/workflows. Guards enforce
+resolved ownership boundaries, not component counts. Scenarios may compose public
+UI to demonstrate their subject; application adapters own store access and routing.
+
 `ads mcp [directory]` serves a project's local design system over stdio. It uses
 the same `ds.config.json`, token inspection and core checks as the CLI. It reads
 source and build artifacts. Optionally it manages one configured project
@@ -54,15 +60,21 @@ managed project compiler on demand and after relevant source changes.
 Switching entries overlays a centered loading spinner, then reveals the new
 scenario inside the existing App. Loading and diagnostic overlays do not move the
 preview. Token presentation comes from project-owned scenarios, fixtures and
-public review patterns, using the project's real foundation CSS and extracted
+development-only review helpers, using the project's real foundation CSS and extracted
 styles. The App runtime contains no token sample templates or named token ordering.
 The generic definition inspector remains available without a scenario build.
 
 There are no required browser-page files in the project. Colocated scenarios and
-fixtures, optional public review-layout patterns, and the project's compiler
+fixtures, optional development-only review helpers, and the project's compiler
 entry supply the presentation. Use the existing runtime URL when MCP is connected
 instead of starting a second compiler for that project.
 
+Development review UI lives in `review/`, behind a separate development entry;
+production patterns remain application UI. Discover `ads_status.project.review`
+and read `ads://guides/review` for imports, guarded owners and migration. Review
+exports are not product catalogue entries. They can frame real scenarios and
+render token samples without entering the deployed application's graph.
+
 ## Connect Codex or Claude
 
 Use the published package through `npx`. No ADS checkout or global installation
@@ -175,9 +187,10 @@ The server supplies agent guidance through its instructions, tool descriptions,
 | `ads_show_tokens` | Render a discovered token scenario; legacy compilers retain the definition inspector |
 | `ads_scenarios` | Bounded token/component/pattern/composition scenario discovery |
 | `ads_show_scenario` | Render an exact discovered scenario with its own fixtures |
-| `ads_behaviors` | Bounded guarantee/evidence discovery; pass an exact unit for contract details |
+| `ads_behaviors` | Paged owner discovery; select a unit and detail section |
 | `ads_verify` | Execute an owner's registered checks and record revision-bound evidence |
-| `ads_investigate` | Read one check's latest compact failure/evidence bundle without rerunning it |
+| `ads_results` | Page saved execution outcomes, diagnostics, logs and captures without rerunning |
+| `ads_investigate` | Read one check's summary, then paged requests/errors/artifacts |
 | `ads_capture` | On-demand PNG of a discovered scenario or named element; replace current and clear candidate |
 | `ads_capture_clear` | Remove generated captures or discard only the candidate |
 | `ads_show_<id>` | Optional explicitly configured grouped App |
@@ -193,8 +206,9 @@ public exports from `components/`, `patterns/` and `controllers/`; it does not e
 guess component props. Read the exported API and owning guide. An export name
 alone does not prove that a preview renders that particular element.
 
-`ads://project/status`, `/build`, `/tokens`, `/catalog`, `/scenarios`, `/behaviors`, and `/checks` carry complete JSON
-detail. Allowed project documentation/source and skill files are separate
+`ads://project/status`, `/build`, `/tokens`, `/catalog`, `/scenarios` and `/checks`
+carry project JSON detail. Behavior discovery, execution outcomes and investigation
+details are paged; their resource reads use the same bounds as their tools. Allowed project documentation/source and skill files are separate
 resources. No arbitrary filesystem reader is exposed. Prefer bounded tools for
 large catalogues; explicit resource reads can enter model context and a client
 may truncate large payloads.
@@ -215,6 +229,14 @@ informational limit nor a traced target proves a rendered failure or success.
 Bounded check results put warnings before informational limits; the checks
 resource retains complete results.
 
+`property-registration` is a blocking architecture diagnostic for invalid or
+conflicting typed CSS registrations. Keep registrations in their runtime owner
+or beside their real token definitions; `base.css` remains a closed reset contract.
+Use `@reqvire-org/ads/linaria` in both product and preview extraction so each
+registration survives intact in the App's CSS resources. Descriptor literals are
+metadata; normal styling still uses tokens. Read `ads://guides/atomic-styles` for
+ownership, valid initial values, browser checks and examples.
+
 ### Screenshots and candidate comparison
 
 `ads_capture({scenario:"<discovered ID>",target?,theme?,viewport?})` renders current
@@ -249,8 +271,10 @@ limits, target declarations and the guarded review workflow.
 
 Read `ads://guides/behaviors` or the [behavior guide](BEHAVIORS.md) for the contract
 and runner schema. `ads_behaviors({ "unit": "components/MessageScroller" })`
-returns subjects, guarantees, demonstration links and check IDs for a discovered
-owner. `ads_verify({ "unit": "components/MessageScroller", "checks": ["prepend-anchor"] })`
+pages an owner's checks by default; select `section: "subjects"`, `"guarantees"`,
+`"demonstrations"` or `"profiles"` for other details. Without a unit it lists owner
+summaries. Follow `nextCursor` with identical filters. Changed registrations or
+evidence revisions invalidate discovery cursors. `ads_verify({ "unit": "components/MessageScroller", "checks": ["prepend-anchor"] })`
 runs those registered cases. The names here are examples, never built-in cases.
 
 `covers` describes rendered UI; optional `exercises` describes public behavioral
@@ -276,14 +300,47 @@ single failed assertion does not turn the other checks into failures. Overall
 verification and guarded application still fail. Suite errors, unexplained exits,
 missing results and interrupted reports cannot certify passing checks.
 
-For diagnosis, call `ads_investigate({ "unit": "components/Example", "check": "keyboard-navigation" })`
-with discovered IDs. It reads the latest check bundle without rerunning anything,
-including rejected candidates. `ads://project/investigations` lists available
-bundles; returned resource URIs expose the bundle and available registered
+Verification and guarded-edit replies are summaries: counts, acceptance, at most
+three failure previews and `resultId`, within 4096 UTF-8 JSON bytes. Use:
+
+```js
+ads_results({resultId: "<returned ID>", section: "outcomes", status: "not_passed"})
+ads_results({resultId: "<returned ID>", section: "outcomes", status: "not_passed", cursor: "<nextCursor>"})
+```
+
+Each listing defaults to 10 rows, allows at most 20 and stays within 8192 JSON
+bytes. A byte-limited page can contain fewer than `limit` rows; follow
+`nextCursor` with the same result ID, section and status. Other sections are
+`checks`, `advisories`, `warnings`, `changes`, `captures`, `acceptance`,
+`investigation` and `selection`. No page reruns validation. Rows marked
+`detailTruncated` can be read exactly with `recordIndex`, `offset` and `chars`
+(maximum 2000 UTF-16 characters); follow `nextOffset`. Read full logs only for the
+relevant record. JSON also remains available through `ads://results/<resultId>`;
+use matching query parameters for pages or ranges. `ads://project/results` lists
+the latest IDs. Status embeds summaries, not complete runner reports. Saved
+outcomes are completion-time evidence; compare revisions with `ads_behaviors`
+before claiming current source passed.
+
+Only the latest verification snapshot and latest mutation snapshot are retained,
+independently, each up to 8 MiB in `.ds/tool-results/`. Replacing a snapshot makes
+its old ID unavailable; do not mix pages across runs. An oversized report retains
+only its summary and an explicit unavailable-details warning. A failed disk write
+keeps details in server memory until shutdown. Neither condition changes guard
+acceptance or whether source was applied. These are logical payload byte limits;
+compatibility text can duplicate structured JSON in the MCP response.
+
+For diagnosis, take one outcome's exact `unit`, `check` and `runId` and call
+`ads_investigate`. The run ID rejects superseded evidence. Without a check, it
+lists available investigations with paging. An exact check returns a summary
+within 4096 JSON bytes; `section: "details"`, `"requests"`, `"browserErrors"` or `"artifacts"`
+returns detail pages with the same 10/20-row and 8192-byte limits. Truncated records support
+`recordIndex`/`offset`/`chars` with the exact `runId`; artifact URIs are read
+separately. It never reruns checks, including rejected candidates.
+`ads://project/investigations` lists available bundles; returned resource URIs expose the bundle and available registered
 artifacts. Exact input/observed preview revisions, source/failing step, startup
 viewport and failed requests separate evidence from a suspected cause.
-`failure.category` distinguishes architecture, build, transport, runner and
-assertion boundaries; `acceptance` names established and unverified scope.
+The summary's `details.failure.category` distinguishes architecture, build,
+transport, runner and assertion boundaries; `acceptance` names established and unverified scope.
 Only the latest bundle per check remains resource-accessible. Read the portable
 [evidence guide](../skills/ads-designer/references/evidence.md) for collection
 limits and project-controlled trace/screenshot recording.
@@ -352,6 +409,7 @@ The same discovery covers the rest of the project ADS:
 
 | Unit | Scope |
 |------|-------|
+| `review/<Owner>` | Development-only frames, token renderers, demo controls, local checks and review-entry re-exports |
 | `foundation` | Shared ADS entry styles and root helpers |
 | `documentation` | ADS/project guides, shared credits and license notices, and `licenses/` text collections |
 | `assets/brand`, `assets/fonts`, other `assets/*` groups | Original SVG, image, font and other asset files |
@@ -424,8 +482,9 @@ Pass that `patchFile` to `ads_apply_patch` with `dryRun:true` to validate before
 applying. This runs the normal candidate gates, including affected registered
 behavior checks against an isolated candidate and its configured browser preview.
 It writes no live source and does not persist passing evidence for live inputs.
-Read returned `behavior` failures or behavior-check results in `checks`; update the
-draft, diff again and repeat as needed. Apply with `dryRun:false` after validation;
+Read the summary, then use its `resultId` with `ads_results` for failing
+`outcomes`, `diagnostics` or named pipeline `checks`; update the draft, diff again
+and repeat as needed. Apply with `dryRun:false` after validation;
 the gates run again. `ads_verify({unit,checks?})` checks current source and accepts
 no draft argument; a selected-check draft runner is not currently exposed.
 Use `action:"discard"` to remove the draft. Remote clients can continue sending
@@ -463,8 +522,8 @@ Install changed dependencies before verification; candidates use the project's
 installed `node_modules`.
 
 Resolve ownership diagnostics by preserving the required capability in its proper
-layer. Demo-only sizing, borders and framing belong in a public review/layout
-pattern; a component API addition needs a runtime use case. Measured imperative
+layer. Demo-only sizing, borders and framing belong in a development-only review
+helper; a component API addition needs a runtime use case. Measured imperative
 geometry uses exact `styleWrites` properties. After migrating JSX inline geometry,
 replace its own boundary entries in the same owner patch and check the final state.
 After the gates pass, verify the behavior in a browser.
@@ -472,7 +531,7 @@ After the gates pass, verify the behavior in a browser.
 A small change needs only its hunk. A complete new component may include its
 implementation, public re-export, scenario and fixture in the same unit patch,
 so coverage is checked against a complete candidate. New units use a new
-`components/`, `patterns/` or `composition/` owner ID following the same colocation
+`components/`, `patterns/`, `controllers/`, `review/` or `composition/` owner ID following the same colocation
 convention. A patch cannot include a peer unit, capture existing peers beneath
 a new directory owner, or change unrelated public-entry statements. Shared
 public-entry changes are limited to re-exports from the selected unit. Alongside
@@ -606,6 +665,14 @@ origin hosts the sandbox proxy; that proxy creates an opaque inner App iframe
 and forwards the standard Apps bridge messages. The diagnostic explorer follows
 the same sandbox model. Only the App materializes and executes project resources.
 
+Both ADS hosts allow native form validation and submission events through all
+iframe layers. Client-side forms use their intended `submit` handlers and
+`preventDefault()`. CSP `form-action 'none'` blocks native action requests;
+`allow-forms` grants neither host DOM access nor top-level navigation. External
+hosts choose their own permissions. See the portable
+[scenario guide](../skills/ads-designer/references/scenarios.md#forms-inside-apps)
+for verification and diagnosis.
+
 For inline documents without an explicit App base URL, ADS supplies
 `<base href="about:srcdoc">` and permits the local `about:` base scheme in CSP.
 Bare and named fragment links retain native in-document navigation and state.
@@ -977,7 +1044,7 @@ instruction reads alone do not establish Apps/Skills activation.
 ### Token sample verification
 
 Token scenarios declare `samples: fixture.samples` and render a project-owned public
-review pattern with that `samples` input. Each fixture record has `{ token, property,
+review renderer with that `samples` input. Each fixture record has `{ token, property,
 probe }`; the tool discovers the resulting token names. Plain token lists and empty
 covers do not satisfy review coverage. The same bindings travel in the compiled
 resource manifest or self-contained App seed.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@reqvire-org/ads",
-  "version": "0.3.17",
+  "version": "0.3.20",
   "type": "module",
   "description": "A design system your agent can see and shape. Your components. Your look. Your code.",
   "repository": {
@@ -52,6 +52,7 @@
   },
   "dependencies": {
     "@modelcontextprotocol/server": "2.3.1",
+    "css-tree": "3.2.1",
     "postcss": "^8.5.30",
     "postcss-selector-parser": "^7.1.6",
     "postcss-value-parser": "^4.2.0",

package/dist/bootstrap-ds/design-system/patterns/token-preview/Scenario.tsx

@@ -1,4 +0,0 @@
-import { TokenPreview } from "@ds";
-import { fixture } from "./fixture";
-export const scenario = { title: fixture.title, covers: ["TokenPreview"] };
-export default function Scenario() { return <TokenPreview {...fixture} />; }

package/dist/bootstrap-ds/design-system/patterns/token-preview/fixture.ts

@@ -1,8 +0,0 @@
-export const fixture = {
-  "title": "Token preview",
-  "text": "Aa",
-  samples: [
-    {"token": "--accent", "property": "background-color", "probe": "rgb(31, 97, 163)"},
-    {"token": "--space-4", "property": "width", "probe": "13.375px"},
-  ]
-} as const;

package/dist/skills/ads-designer/assets/bootstrap-ds/design-system/patterns/token-preview/Scenario.tsx

@@ -1,4 +0,0 @@
-import { TokenPreview } from "@ds";
-import { fixture } from "./fixture";
-export const scenario = { title: fixture.title, covers: ["TokenPreview"] };
-export default function Scenario() { return <TokenPreview {...fixture} />; }

package/dist/skills/ads-designer/assets/bootstrap-ds/design-system/patterns/token-preview/fixture.ts

@@ -1,8 +0,0 @@
-export const fixture = {
-  "title": "Token preview",
-  "text": "Aa",
-  samples: [
-    {"token": "--accent", "property": "background-color", "probe": "rgb(31, 97, 163)"},
-    {"token": "--space-4", "property": "width", "probe": "13.375px"},
-  ]
-} as const;