@reqvire-org/ads 0.3.9 → 0.3.10

package/dist/preview-resources.mjs

@@ -28,7 +28,8 @@ export function previewEntriesPlugin(entries, mountEntry) {
     load(id) {
       const entry = ids.get(id.slice(1));
       if (!entry) return;
-      return `import { mountScenario } from ${JSON.stringify(mountEntry)};import Scenario from ${JSON.stringify(path.resolve(entry.root, entry.file))};export const mount = container => mountScenario(Scenario,container);`;
+      const styles = (entry.stylesheets ?? []).map(file => `import ${JSON.stringify(path.resolve(entry.root, file))};`).join("");
+      return `import { mountScenario } from ${JSON.stringify(mountEntry)};${styles}import Scenario from ${JSON.stringify(path.resolve(entry.root, entry.file))};export const mount = container => mountScenario(Scenario,container);`;
     },
   };
 }

package/dist/scenarios.mjs

@@ -110,7 +110,8 @@ export function inspectScenarios(options, suppliedProgram) {
       const owner = scoped.inventory.owner(relative);
       for (const name of tokens) if (tokenInventory.tokens.find(token => token.name === name)?.owner !== owner) report(file, `Token ${name} needs a preview beside its defining owner. Shared tokens belong under the configured token directory; local tokens stay with their component/pattern.`);
     }
-    scenarios.push({ id, kind, title: metadata.title, covers: [...new Set(metadata.covers)], ...(Object.hasOwn(metadata, "exercises") ? { exercises: [...new Set(exercises)] } : {}), tokens, ...(metadata.samples ? { samples: metadata.samples } : {}), file: path.relative(root, file).replaceAll("\\", "/"), artifact: path.relative(root, scenarioArtifact(root, id)).replaceAll("\\", "/") });
+    const stylesheets = kind === "tokens" ? scoped.definitions.filter(entry => entry.unit === scoped.inventory.owner(relative)).map(entry => entry.file) : [];
+    scenarios.push({ id, kind, title: metadata.title, covers: [...new Set(metadata.covers)], ...(Object.hasOwn(metadata, "exercises") ? { exercises: [...new Set(exercises)] } : {}), tokens, ...(metadata.samples ? { samples: metadata.samples } : {}), ...(stylesheets.length ? { stylesheets } : {}), file: path.relative(root, file).replaceAll("\\", "/"), artifact: path.relative(root, scenarioArtifact(root, id)).replaceAll("\\", "/") });
   }
   return { scenarios: scenarios.sort((a, b) => a.id.localeCompare(b.id)), diagnostics };
 }

package/dist/skills/ads-break-ui/references/scenarios.md

@@ -1,8 +1,23 @@
-# Scenario render evidence and public class helpers
+# Scenario rendering, token previews and public class helpers
 
 Use this reference for `scenario-render`, `scenario-coverage` or `showcase-class`
 diagnostics. MCP serves the same guide as `ads://guides/scenarios`.
 
+## Owner-local token previews load their own definitions
+
+Keep the registered token sheet imported by its runtime owner for product use.
+A colocated `kind: "tokens"` scenario may render only the public review pattern
+with its fixture samples. Discovery adds the registered owner sheet to the
+generated record's `stylesheets`; `previewEntriesPlugin` imports those paths
+into the token preview independently of the runtime component. Custom builders
+that replace this plugin must preserve these explicit stylesheet dependencies.
+Do not render the runtime owner merely to retain its CSS or add unrelated sheets.
+
+Open the exact token scenario in a fresh App and verify resolved values and sample
+effects in both themes. A successful ordinary component preview does not prove
+the independently bundled token preview loads the same definitions. Shared
+foundation styling still follows the project's mount/build integration.
+
 ## Public children can share their parent's scenario
 
 Declare the public parts actually demonstrated in `covers`, even when their

package/dist/skills/ads-designer/references/scenarios.md

@@ -1,8 +1,23 @@
-# Scenario render evidence and public class helpers
+# Scenario rendering, token previews and public class helpers
 
 Use this reference for `scenario-render`, `scenario-coverage` or `showcase-class`
 diagnostics. MCP serves the same guide as `ads://guides/scenarios`.
 
+## Owner-local token previews load their own definitions
+
+Keep the registered token sheet imported by its runtime owner for product use.
+A colocated `kind: "tokens"` scenario may render only the public review pattern
+with its fixture samples. Discovery adds the registered owner sheet to the
+generated record's `stylesheets`; `previewEntriesPlugin` imports those paths
+into the token preview independently of the runtime component. Custom builders
+that replace this plugin must preserve these explicit stylesheet dependencies.
+Do not render the runtime owner merely to retain its CSS or add unrelated sheets.
+
+Open the exact token scenario in a fresh App and verify resolved values and sample
+effects in both themes. A successful ordinary component preview does not prove
+the independently bundled token preview loads the same definitions. Shared
+foundation styling still follows the project's mount/build integration.
+
 ## Public children can share their parent's scenario
 
 Declare the public parts actually demonstrated in `covers`, even when their

package/dist/skills/ads-import/references/scenarios.md

@@ -1,8 +1,23 @@
-# Scenario render evidence and public class helpers
+# Scenario rendering, token previews and public class helpers
 
 Use this reference for `scenario-render`, `scenario-coverage` or `showcase-class`
 diagnostics. MCP serves the same guide as `ads://guides/scenarios`.
 
+## Owner-local token previews load their own definitions
+
+Keep the registered token sheet imported by its runtime owner for product use.
+A colocated `kind: "tokens"` scenario may render only the public review pattern
+with its fixture samples. Discovery adds the registered owner sheet to the
+generated record's `stylesheets`; `previewEntriesPlugin` imports those paths
+into the token preview independently of the runtime component. Custom builders
+that replace this plugin must preserve these explicit stylesheet dependencies.
+Do not render the runtime owner merely to retain its CSS or add unrelated sheets.
+
+Open the exact token scenario in a fresh App and verify resolved values and sample
+effects in both themes. A successful ordinary component preview does not prove
+the independently bundled token preview loads the same definitions. Shared
+foundation styling still follows the project's mount/build integration.
+
 ## Public children can share their parent's scenario
 
 Declare the public parts actually demonstrated in `covers`, even when their

package/dist/skills/ads-migrate/references/scenarios.md

@@ -1,8 +1,23 @@
-# Scenario render evidence and public class helpers
+# Scenario rendering, token previews and public class helpers
 
 Use this reference for `scenario-render`, `scenario-coverage` or `showcase-class`
 diagnostics. MCP serves the same guide as `ads://guides/scenarios`.
 
+## Owner-local token previews load their own definitions
+
+Keep the registered token sheet imported by its runtime owner for product use.
+A colocated `kind: "tokens"` scenario may render only the public review pattern
+with its fixture samples. Discovery adds the registered owner sheet to the
+generated record's `stylesheets`; `previewEntriesPlugin` imports those paths
+into the token preview independently of the runtime component. Custom builders
+that replace this plugin must preserve these explicit stylesheet dependencies.
+Do not render the runtime owner merely to retain its CSS or add unrelated sheets.
+
+Open the exact token scenario in a fresh App and verify resolved values and sample
+effects in both themes. A successful ordinary component preview does not prove
+the independently bundled token preview loads the same definitions. Shared
+foundation styling still follows the project's mount/build integration.
+
 ## Public children can share their parent's scenario
 
 Declare the public parts actually demonstrated in `covers`, even when their

package/dist/skills/ads-motion/references/scenarios.md

@@ -1,8 +1,23 @@
-# Scenario render evidence and public class helpers
+# Scenario rendering, token previews and public class helpers
 
 Use this reference for `scenario-render`, `scenario-coverage` or `showcase-class`
 diagnostics. MCP serves the same guide as `ads://guides/scenarios`.
 
+## Owner-local token previews load their own definitions
+
+Keep the registered token sheet imported by its runtime owner for product use.
+A colocated `kind: "tokens"` scenario may render only the public review pattern
+with its fixture samples. Discovery adds the registered owner sheet to the
+generated record's `stylesheets`; `previewEntriesPlugin` imports those paths
+into the token preview independently of the runtime component. Custom builders
+that replace this plugin must preserve these explicit stylesheet dependencies.
+Do not render the runtime owner merely to retain its CSS or add unrelated sheets.
+
+Open the exact token scenario in a fresh App and verify resolved values and sample
+effects in both themes. A successful ordinary component preview does not prove
+the independently bundled token preview loads the same definitions. Shared
+foundation styling still follows the project's mount/build integration.
+
 ## Public children can share their parent's scenario
 
 Declare the public parts actually demonstrated in `covers`, even when their

package/dist/verification.mjs

@@ -170,7 +170,11 @@ export function createVerificationController(root) {
           if (profile.mode === "browser" && group.some(check => check.scenario)) {
             const { startAdsMcp } = await import("./mcp/server.mjs");
             host ??= await startAdsMcp(root, { stdio: false, showcase: true });
-            for (const check of group.filter(check => check.scenario)) { const url = new URL(host.url); url.searchParams.set("scenario", check.scenario); scenarios[check.scenario] = url.href; }
+            for (const check of group.filter(check => check.scenario)) {
+              const url = new URL(host.url), scenario = context.scenarios.find(entry => entry.id === check.scenario);
+              url.searchParams.set(scenario?.kind === "tokens" ? "category" : "scenario", check.scenario);
+              scenarios[check.scenario] = url.href;
+            }
           }
           const requestContext = { schemaVersion: 1, runId, projectRoot: root, framework: options.config.framework, profile: profileName, mode: profile.mode ?? "unit", checks: group.map(({ contract: _contract, ...check }) => check), scenarios };
           writeFileSync(request, JSON.stringify(requestContext));

package/docs/ADS.md

@@ -209,6 +209,11 @@ Measured runtime variables retain their existing exact `styleWrites` boundary.
 
 A colocated scenario sets `kind:"tokens"` and declares real fixture `samples`
 consumed by a public review pattern. Its ID still derives from its source path.
+Discovery attaches its owner's registered definition sheet as `stylesheets` on
+the generated scenario record; `previewEntriesPlugin` imports it directly into
+that preview's module graph. CSS-only package side effects can then tree-shake
+the runtime component without dropping the token definitions. Keep the runtime
+CSS import for product use; the token scenario need not import or render its owner.
 Every local token needs this real sample coverage, just like shared tokens.
 Definitions, metadata, fixture and token scenario belong to the same edit unit.
 Manifests/fixtures are development inputs; production includes the runtime's

package/docs/ARCHITECTURE.md

@@ -434,6 +434,8 @@ verification, and the browser check does not judge design quality.
 An optional owner-local token namespace keeps component/pattern constants beside
 their consumer. Its definition-only stylesheet contains root/theme custom
 properties and is imported by the runtime owner; UI styling remains in Linaria.
+Independent owner-token preview entries also import the registered definition
+sheet directly, so tree-shaking an unused runtime owner cannot remove their values.
 Namespaces, aliases, ownership and actual colocated sample coverage are checked.
 The shared foundation remains the cross-owner vocabulary. See the
 [owner-token contract](ADS.md#owner-local-tokens).

package/docs/CHANGELOG.md

@@ -1,5 +1,14 @@
 # Changelog
 
+## 0.3.10
+
+- Attach registered owner-local token sheets to independently compiled token
+  previews, preserving definitions under CSS-only package side effects without
+  retaining runtime owners or loading peer sheets. Verify resource closure in
+  React/Preact and rendered samples in a sandboxed App in both themes.
+- Route managed browser checks for owner-local token scenarios through the
+  discovered token category, independent of their component/pattern file paths.
+
 ## 0.3.9
 
 - Credit explicitly declared public child renders reached through parents,

package/docs/MCP.md

@@ -560,6 +560,10 @@ framework compilation and Linaria extraction. The starter's
 - Its `buildGraph(entries, options, track)` adapter runs one multi-entry Vite build
   with `previewEntriesPlugin()` and `createPreviewResources()` from
   `@reqvire-org/ads/scenarios/vite`.
+  Generated owner-token entries include `stylesheets` derived from the registered
+  owner manifest. Pass the entries intact: the plugin imports those definition
+  sheets even when the runtime owner is tree-shaken. A replacement entry plugin
+  must preserve these dependencies without importing unrelated owners.
 - Keep `preserveEntrySignatures: "strict"`, `cssCodeSplit: true`,
   `assetsInlineLimit: 0`, `modulePreload: false`, and `write: false`. Include the
   supplied dependency-tracking plugin and the project's Linaria/framework plugins.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@reqvire-org/ads",
-  "version": "0.3.9",
+  "version": "0.3.10",
   "type": "module",
   "description": "A design system your agent can see and shape. Your components. Your look. Your code.",
   "repository": {