@reqvire-org/ads 0.2.9 → 0.3.1

package/docs/MCP.md

@@ -43,7 +43,7 @@ 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
-styles. The tool contains no token sample templates or named token ordering.
+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
@@ -200,6 +200,15 @@ remain separate owners. `tokens` is one foundation unit covering token definitio
 themes and token scenarios/fixtures, whose coverage spans shared source files.
 Preview IDs remain separate: several token previews belong to `tokens`.
 
+The `tokens` manifest also returns `companionFiles` with the configured foundation
+entry path. When creating or deleting a canonical token foundation file, include
+its required import change in the same `tokens` patch. For example, add
+`tokens/fonts.css` and its first import in `styles.css` together; remove both
+together when removing that font stylesheet. This companion may only change
+imports for canonical files created/deleted in that patch. Preserve other imports
+and comments, retain the foundation entry, and follow the required import order.
+Both files pass the same candidate checks before either is written.
+
 The same discovery covers the rest of the project ADS:
 
 | Unit | Scope |
@@ -259,7 +268,11 @@ so coverage is checked against a complete candidate. New units use a new
 `components/`, `patterns/` 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.
+public-entry changes are limited to re-exports from the selected unit. Alongside
+its real re-export, a patch can remove an obsolete `export {};` placeholder;
+it cannot add one or change unrelated statements. Init generates no empty-export
+placeholder. Report unsupported coupled changes rather than bypassing a rejected
+mutation with direct source writes.
 
 Set `dryRun` to `false` to apply. ADS reconstructs complete candidate files locally
 and validates a temporary project copy with core guards and registered Oxlint
@@ -688,3 +701,32 @@ verify tools, explicit resources, an App entry tool and its UI handshake,
 Refresh/theme behavior, notifications, prompts, then native Skills separately.
 Record the client build and negotiated protocol; HTML delivery or ordinary
 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,
+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.
+
+The renderer identifies its styled sample elements through `data-ads-token` and
+`data-ads-property`. After mounting and font loading, the App uses the browser's CSS
+engine to validate each declared binding and project-supplied probe, then checks
+that changing the token changes the sample's computed property. It restores token
+values synchronously. Failures remain visible and are emitted through App logging
+when the host supports it; a failed sample is not reported as ready.
+
+Source checks establish structural coverage. Browser verification happens when the
+App actually renders, for the active scenario and theme. It is not a pre-write
+browser test in the mutation server and does not establish every interaction or
+pixel-level visual quality. Hosts without Apps retain static diagnostics and the
+showcase URL; they cannot claim rendered verification from a source check alone.
+For browser automation, wait for the selected App's ready/error state. The
+showcase's live notification stream makes `networkidle` unsuitable. Tall previews
+scroll inside the App document; verify their last sample remains reachable.
+
+Existing projects migrate their token fixtures from name lists to explicit sample
+records, pass those records into their public renderer, and add the sample markers.
+Rebuild previews with the updated compiler so the contract is included in resources.
+Tool updates do not overwrite existing project-owned scenarios or renderers.

package/package.json

@@ -1,15 +1,15 @@
 {
   "name": "@reqvire-org/ads",
-  "version": "0.2.9",
+  "version": "0.3.1",
   "type": "module",
   "description": "A design system your agent can see and shape. Your components. Your look. Your code.",
   "repository": {
     "type": "git",
-    "url": "git+https://github.com/reqvire-org/design-system.git"
+    "url": "git+https://github.com/reqvire-org/ads.git"
   },
-  "homepage": "https://github.com/reqvire-org/design-system#readme",
+  "homepage": "https://github.com/reqvire-org/ads#readme",
   "bugs": {
-    "url": "https://github.com/reqvire-org/design-system/issues"
+    "url": "https://github.com/reqvire-org/ads/issues"
   },
   "keywords": [
     "design-system",
@@ -35,7 +35,7 @@
     "sync:skill-starter": "node scripts/sync-skill-starter.mjs",
     "check:skill-starter": "node scripts/sync-skill-starter.mjs --check",
     "lint": "npm run lint:tool",
-    "lint:tool": "npm run check:skill-starter && oxlint --deny-warnings src showcase-client mcp-explorer tests/*.test.mjs scripts/build-ads-tool.mjs scripts/pack-ads-tool.mjs",
+    "lint:tool": "npm run check:skill-starter && oxlint --deny-warnings src preview-client showcase-client mcp-explorer tests/*.test.mjs scripts/build-ads-tool.mjs scripts/pack-ads-tool.mjs",
     "lint:project": "npm run lint:ds && npm run lint:style && npm run check:skill-starter",
     "lint:ds": "node dist/cli.mjs lint-config && node dist/cli.mjs check && oxlint --deny-warnings --config .ds/oxlintrc.json src design-system",
     "lint:style": "biome lint --config-path=biome.css.json .",