@reqvire-org/ads 0.3.1 → 0.3.3

package/dist/skills/ads-assimilate/references/cli.md

@@ -55,7 +55,7 @@ If no published distribution exists, build and pack the tooling checkout with
 From inside an existing test project:
 
 ```sh
-ads_tool_package="/absolute/path/to/reqvire-org-ads-0.3.1.tgz"
+ads_tool_package="/absolute/path/to/reqvire-org-ads-0.3.2.tgz"
 npx --yes --package "$ads_tool_package" ads --help
 npx --yes --package "$ads_tool_package" ads init --framework react --tool-package "$ads_tool_package"
 npm install
@@ -93,7 +93,8 @@ component rules through the project's plugin adapter and `ds.config.json`, then
 run its actual build. Use `lint-config` directly for custom pipeline integration
 or debugging, not as a separate routine setup step.
 
-Use ADS 0.3.1 or later for the shared-resource preview compiler. `mcp` starts stdio
+Use ADS 0.3.2 or later for the closed foundation contract and recoverable
+shared-resource preview compiler. `mcp` starts stdio
 plus its local website; `showcase` starts the browser-only MCP runtime. Open the existing runtime URL from `ads_status` when
 connected; otherwise use `npm run dev:showcase` or the installed `ads showcase`.
 The tool client discovers entries and renders MCP Apps. Init adds the launch

package/dist/skills/ads-assimilate/references/native-implementation.md

@@ -55,6 +55,22 @@ target framework. With the default root ADS layout:
   dimensions, positions, or transforms. Document and constrain the exception in
   the shared architecture guard; never broaden it to arbitrary visual styles.
 
+Preserve the reference's required capabilities while assigning each concern to
+its owner. Demo utilities for container size, border or framing become a public
+review/layout pattern around the real component. Add component props for a
+deliberate runtime API requirement; missing demo layout alone is not justification.
+For imperative geometry, register exact `styleWrites` properties. After migrating
+from JSX inline geometry, change source and its own config companion together:
+remove the obsolete `inlineStyleFiles` exception and register only properties the
+implementation actually writes. Verify the final component with that boundary.
+
+Keep presentational building blocks independent of an unnecessary form controller
+or other state engine. Scenario adapters may own demo state and validation. When
+a reusable controller is part of the intended product API, define and test its
+actual contract; a similar method shape alone does not establish compatibility
+with the reference library. Keep state updaters pure and verify submit, focus,
+validation, reset and asynchronous behavior that the API promises.
+
 Use current repository conventions in another target rather than assuming the
 same framework, directory structure, or lint tooling.
 

package/dist/skills/ads-break-ui/SKILL.md

@@ -30,7 +30,11 @@ unrelated statements. Its real re-export may accompany removal of a redundant
 `export {};` placeholder; do not add empty exports. A `tokens` manifest lists the foundation
 entry in `companionFiles`: when creating/deleting a canonical token file such as
 `fonts.css`, include only its required import change there in the same patch.
-Preserve other imports/comments and the canonical order. Use `dryRun: true` to
+Preserve other imports/comments and the canonical order. Runtime owner manifests
+also list a `ds.config.json` companion: change only that owner's `inlineStyleFiles`
+and `boundaries.styleWrites` entries together with its source. Unused permissions
+fail the core checks; do not pre-register a boundary without its implementation.
+Use `dryRun: true` to
 inspect validation; applying re-runs the gates. Fix rejected patches in their
 owner. Report unsupported coupled changes instead of bypassing a rejection with
 direct source writes. Shared styles/helpers use `foundation`, root guides use
@@ -193,6 +197,15 @@ source definitions and values; inspecting definitions does not prove UI parity.
 The tool keeps the shared naming contract; sample templates and their token
 lists belong to the project.
 
+A public review pattern may be covered by real token or composition scenarios;
+it needs no redundant standalone entry. Remove an optional scenario only while
+retaining reachable render coverage. Keep directory ownership anchored by its
+runtime entry (`index` or a file matching the directory name) or colocated fixture.
+Import colocated image/font fixtures so MCP serves them through asset resources.
+For a broken-image case, use a local failing fixture, rather than an external
+network failure or a domain-specific CSP exception. Production asset APIs remain
+unrestricted by this fixture guidance.
+
 Scenarios, colocated fixtures and helpers are development-only. Never export them
 from the runtime barrel or import them in production, including through aliases,
 re-exports or dynamic imports. They may not import application stores, routers,
@@ -203,6 +216,27 @@ Use local simulated services in fixtures. Tests may import fixtures; load real
 foundation CSS rather than assigning shared token values in JavaScript. Keep
 full-app integration harnesses and workflow coverage in application test support.
 
+Foundation CSS is checked, not an escape hatch. Value sheets define shared tokens
+on the document root/themes; `fonts.css` holds font-face metadata. `base.css` has
+three closed roles: root/body typography, canvas and theme defaults; limited native
+normalization; and global focus indicators/reduced-motion rules. Every selector
+branch, property and value must fit its role. Token-backed control skins, layout,
+interactive state rules and owner hooks are rejected even through `:where()`.
+Do not copy an unchecked upstream preflight or turn a component repair into a reset.
+Keep behavior and skin in their runtime owner. Put demo-only sizing and framing
+in a public review/layout pattern; add component props for a deliberate runtime
+API need. Preserve required capabilities while following ownership rules.
+Browser review still verifies the effects.
+
+Invalid metadata and source failures keep the managed compiler alive for repairs.
+Read `ads_status.build` or `ads://project/build`, fix the owner, then wait for current
+successful output. If the builder exited, fix its command and invoke the preview
+again; ADS starts one fresh child without an MCP reconnect. Compiler-code changes
+also reload on the next preview invocation. Reconnect the client when upgrading
+the ADS server package itself. Persistent SSE/notification streams make
+`networkidle` unsuitable: wait for the App's current ready/error state instead.
+
+
 
 
 Register component/project Oxlint plugins and rules in `ds.config.json`. Use
@@ -210,7 +244,14 @@ scoped `oxlint.overrides` for justified file-specific settings; never edit
 `.ds/oxlintrc.json`. These overrides configure Oxlint, not the independent
 architecture checks in `ads check`. Measured renderer properties and documented
 non-state hooks use explicit `boundaries`; shared token writes and primitive
-state overrides cannot be allowlisted. Add generic architectural protections to
+state overrides cannot be allowlisted. When migrating JSX inline geometry to
+imperative writes, port the source and replace its own boundary entries together
+in the owner's patch. Remove obsolete `inlineStyleFiles` entries and unused
+`styleWrites` properties; do not broaden permissions to keep a migration passing.
+Pointer-capture advisories call for review of cancellation, capture loss and
+teardown, including cleanup delegated to hooks. Verify actual cleanup in a browser;
+a locally present handler alone does not prove correctness.
+Add generic architectural protections to
 ADS core and keep domain/component-specific rules registered in project setup.
 
 Read [references/verification.md](references/verification.md) for viewport,

package/dist/skills/ads-designer/SKILL.md

@@ -62,7 +62,11 @@ unrelated statements. Its real re-export may accompany removal of a redundant
 `export {};` placeholder; do not add empty exports. A `tokens` manifest lists the foundation
 entry in `companionFiles`: when creating/deleting a canonical token file such as
 `fonts.css`, include only its required import change there in the same patch.
-Preserve other imports/comments and the canonical order. Use `dryRun: true` to
+Preserve other imports/comments and the canonical order. Runtime owner manifests
+also list a `ds.config.json` companion: change only that owner's `inlineStyleFiles`
+and `boundaries.styleWrites` entries together with its source. Unused permissions
+fail the core checks; do not pre-register a boundary without its implementation.
+Use `dryRun: true` to
 inspect validation; applying re-runs the gates. Fix rejected patches in their
 owner. Report unsupported coupled changes instead of bypassing a rejection with
 direct source writes. Shared styles/helpers use `foundation`, root guides use
@@ -331,6 +335,15 @@ source definitions and values; inspecting definitions does not prove UI parity.
 The tool keeps the shared naming contract; sample templates and their token
 lists belong to the project.
 
+A public review pattern may be covered by real token or composition scenarios;
+it needs no redundant standalone entry. Remove an optional scenario only while
+retaining reachable render coverage. Keep directory ownership anchored by its
+runtime entry (`index` or a file matching the directory name) or colocated fixture.
+Import colocated image/font fixtures so MCP serves them through asset resources.
+For a broken-image case, use a local failing fixture, rather than an external
+network failure or a domain-specific CSP exception. Production asset APIs remain
+unrestricted by this fixture guidance.
+
 Scenarios, colocated fixtures and helpers are development-only. Never export them
 from the runtime barrel or import them in production, including through aliases,
 re-exports or dynamic imports. They may not import application stores, routers,
@@ -341,6 +354,27 @@ Use local simulated services in fixtures. Tests may import fixtures; load real
 foundation CSS rather than assigning shared token values in JavaScript. Keep
 full-app integration harnesses and workflow coverage in application test support.
 
+Foundation CSS is checked, not an escape hatch. Value sheets define shared tokens
+on the document root/themes; `fonts.css` holds font-face metadata. `base.css` has
+three closed roles: root/body typography, canvas and theme defaults; limited native
+normalization; and global focus indicators/reduced-motion rules. Every selector
+branch, property and value must fit its role. Token-backed control skins, layout,
+interactive state rules and owner hooks are rejected even through `:where()`.
+Do not copy an unchecked upstream preflight or turn a component repair into a reset.
+Keep behavior and skin in their runtime owner. Put demo-only sizing and framing
+in a public review/layout pattern; add component props for a deliberate runtime
+API need. Preserve required capabilities while following ownership rules.
+Browser review still verifies the effects.
+
+Invalid metadata and source failures keep the managed compiler alive for repairs.
+Read `ads_status.build` or `ads://project/build`, fix the owner, then wait for current
+successful output. If the builder exited, fix its command and invoke the preview
+again; ADS starts one fresh child without an MCP reconnect. Compiler-code changes
+also reload on the next preview invocation. Reconnect the client when upgrading
+the ADS server package itself. Persistent SSE/notification streams make
+`networkidle` unsuitable: wait for the App's current ready/error state instead.
+
+
 
 
 Register component/project Oxlint plugins and rules in `ds.config.json`. Use
@@ -348,7 +382,14 @@ scoped `oxlint.overrides` for justified file-specific settings; never edit
 `.ds/oxlintrc.json`. These overrides configure Oxlint, not the independent
 architecture checks in `ads check`. Measured renderer properties and documented
 non-state hooks use explicit `boundaries`; shared token writes and primitive
-state overrides cannot be allowlisted. Add generic architectural protections to
+state overrides cannot be allowlisted. When migrating JSX inline geometry to
+imperative writes, port the source and replace its own boundary entries together
+in the owner's patch. Remove obsolete `inlineStyleFiles` entries and unused
+`styleWrites` properties; do not broaden permissions to keep a migration passing.
+Pointer-capture advisories call for review of cancellation, capture loss and
+teardown, including cleanup delegated to hooks. Verify actual cleanup in a browser;
+a locally present handler alone does not prove correctness.
+Add generic architectural protections to
 ADS core and keep domain/component-specific rules registered in project setup.
 
 Examples and composition scenarios must consume the same public components, patterns,

package/dist/skills/ads-designer/assets/bootstrap-ds/ADS.md

@@ -40,6 +40,35 @@ Token names and prefixes are fixed by ADS architecture; foreign brand prefixes
 are rejected. Shared assignments belong in token files. Components own
 `--ds-*`, patterns `--ux-*`, and the showcase `--showcase-*`; token files cannot
 assign those local variables or override component state.
+
+Foundation roles are enforced by `foundation-role`, `foundation-selector` and
+`foundation-import`, alongside the regular token checks. Shared definitions
+belong on the document root or explicit root themes; ordinary declarations belong
+in `base.css`, and font-face descriptors in optional `fonts.css`. The entry imports
+canonical sheets; those sheets cannot import another styling layer. Component
+classes, IDs, data/ARIA hooks, contextual selectors, keyframes and scoped UI rules
+are rejected in the foundation, including nested functional selectors. Raw visual
+values and undefined token references are checked in native defaults too; literal
+font-face metadata keeps its separate asset role.
+
+`base.css` has three closed roles:
+
+- Document defaults: root/body typography, canvas colors and theme behavior,
+  global text selection and document scrollbars.
+- Native resets: permitted normalization properties and values, such as zero
+  spacing, inherited control typography, list resets and responsive replaced media.
+- Global accessibility: universal `:focus-visible` outline rules, and reduced-motion
+  overrides inside `@media (prefers-reduced-motion: reduce)`.
+
+The `foundation-role` check validates every selector branch, property and value.
+Native selectors are not a bypass: token-backed button backgrounds, flex/grid
+layout, component-specific focus rules and hover/disabled skins are rejected.
+Shared token definitions belong in value sheets, not `base.css`. No project token
+names are embedded in this policy. A zero-specificity `:where()` wrapper does not
+change ownership. Put component design and animation in Linaria owners, and
+scenario layout variations in typed public review-pattern props. Browser review
+still checks the effects and accessibility of permitted defaults.
+
 Own primitive markup, focus, hover, selected, disabled, loading, and motion in
 the primitive. Use typed props for variations. Keep reusable structure and skin
 in colocated Linaria blocks using `css` and `cx` from `@linaria/atomic`.

package/dist/skills/ads-designer/assets/bootstrap-ds/design-system/tokens/base.css

@@ -1,3 +1,6 @@
+:root { color-scheme: light; }
+:root[data-theme="dark"] { color-scheme: dark; }
+
 *,
 *::before,
 *::after {
@@ -5,7 +8,7 @@
 }
 
 body {
-  margin: var(--space-0);
+  margin: 0;
   background: var(--bg-canvas);
   color: var(--text-body);
   font-family: var(--font-sans);

package/dist/skills/ads-designer/assets/bootstrap-ds/design-system/tokens/colors.css

@@ -1,5 +1,5 @@
 :root {
-  color-scheme: light;
+
   --bg-canvas: #faf9f6;
   --bg-surface: #fff;
   --bg-hover: #f1efea;
@@ -15,7 +15,7 @@
 }
 
 :root[data-theme="dark"] {
-  color-scheme: dark;
+
   --bg-canvas: #17191e;
   --bg-surface: #20232a;
   --bg-hover: #2c3039;

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

@@ -55,7 +55,7 @@ If no published distribution exists, build and pack the tooling checkout with
 From inside an existing test project:
 
 ```sh
-ads_tool_package="/absolute/path/to/reqvire-org-ads-0.3.1.tgz"
+ads_tool_package="/absolute/path/to/reqvire-org-ads-0.3.2.tgz"
 npx --yes --package "$ads_tool_package" ads --help
 npx --yes --package "$ads_tool_package" ads init --framework react --tool-package "$ads_tool_package"
 npm install
@@ -93,7 +93,8 @@ component rules through the project's plugin adapter and `ds.config.json`, then
 run its actual build. Use `lint-config` directly for custom pipeline integration
 or debugging, not as a separate routine setup step.
 
-Use ADS 0.3.1 or later for the shared-resource preview compiler. `mcp` starts stdio
+Use ADS 0.3.2 or later for the closed foundation contract and recoverable
+shared-resource preview compiler. `mcp` starts stdio
 plus its local website; `showcase` starts the browser-only MCP runtime. Open the existing runtime URL from `ads_status` when
 connected; otherwise use `npm run dev:showcase` or the installed `ads showcase`.
 The tool client discovers entries and renders MCP Apps. Init adds the launch

package/dist/skills/ads-import/SKILL.md

@@ -26,7 +26,11 @@ unrelated statements. Its real re-export may accompany removal of a redundant
 `export {};` placeholder; do not add empty exports. A `tokens` manifest lists the foundation
 entry in `companionFiles`: when creating/deleting a canonical token file such as
 `fonts.css`, include only its required import change there in the same patch.
-Preserve other imports/comments and the canonical order. Use `dryRun: true` to
+Preserve other imports/comments and the canonical order. Runtime owner manifests
+also list a `ds.config.json` companion: change only that owner's `inlineStyleFiles`
+and `boundaries.styleWrites` entries together with its source. Unused permissions
+fail the core checks; do not pre-register a boundary without its implementation.
+Use `dryRun: true` to
 inspect validation; applying re-runs the gates. Fix rejected patches in their
 owner. Report unsupported coupled changes instead of bypassing a rejection with
 direct source writes. Shared styles/helpers use `foundation`, root guides use
@@ -298,6 +302,15 @@ source definitions and values; inspecting definitions does not prove UI parity.
 The tool keeps the shared naming contract; sample templates and their token
 lists belong to the project.
 
+A public review pattern may be covered by real token or composition scenarios;
+it needs no redundant standalone entry. Remove an optional scenario only while
+retaining reachable render coverage. Keep directory ownership anchored by its
+runtime entry (`index` or a file matching the directory name) or colocated fixture.
+Import colocated image/font fixtures so MCP serves them through asset resources.
+For a broken-image case, use a local failing fixture, rather than an external
+network failure or a domain-specific CSP exception. Production asset APIs remain
+unrestricted by this fixture guidance.
+
 Scenarios, colocated fixtures and helpers are development-only. Never export them
 from the runtime barrel or import them in production, including through aliases,
 re-exports or dynamic imports. They may not import application stores, routers,
@@ -308,6 +321,27 @@ Use local simulated services in fixtures. Tests may import fixtures; load real
 foundation CSS rather than assigning shared token values in JavaScript. Keep
 full-app integration harnesses and workflow coverage in application test support.
 
+Foundation CSS is checked, not an escape hatch. Value sheets define shared tokens
+on the document root/themes; `fonts.css` holds font-face metadata. `base.css` has
+three closed roles: root/body typography, canvas and theme defaults; limited native
+normalization; and global focus indicators/reduced-motion rules. Every selector
+branch, property and value must fit its role. Token-backed control skins, layout,
+interactive state rules and owner hooks are rejected even through `:where()`.
+Do not copy an unchecked upstream preflight or turn a component repair into a reset.
+Keep behavior and skin in their runtime owner. Put demo-only sizing and framing
+in a public review/layout pattern; add component props for a deliberate runtime
+API need. Preserve required capabilities while following ownership rules.
+Browser review still verifies the effects.
+
+Invalid metadata and source failures keep the managed compiler alive for repairs.
+Read `ads_status.build` or `ads://project/build`, fix the owner, then wait for current
+successful output. If the builder exited, fix its command and invoke the preview
+again; ADS starts one fresh child without an MCP reconnect. Compiler-code changes
+also reload on the next preview invocation. Reconnect the client when upgrading
+the ADS server package itself. Persistent SSE/notification streams make
+`networkidle` unsuitable: wait for the App's current ready/error state instead.
+
+
 
 
 Register component/project Oxlint plugins and rules in `ds.config.json`. Use
@@ -315,7 +349,14 @@ scoped `oxlint.overrides` for justified file-specific settings; never edit
 `.ds/oxlintrc.json`. These overrides configure Oxlint, not the independent
 architecture checks in `ads check`. Measured renderer properties and documented
 non-state hooks use explicit `boundaries`; shared token writes and primitive
-state overrides cannot be allowlisted. Add generic architectural protections to
+state overrides cannot be allowlisted. When migrating JSX inline geometry to
+imperative writes, port the source and replace its own boundary entries together
+in the owner's patch. Remove obsolete `inlineStyleFiles` entries and unused
+`styleWrites` properties; do not broaden permissions to keep a migration passing.
+Pointer-capture advisories call for review of cancellation, capture loss and
+teardown, including cleanup delegated to hooks. Verify actual cleanup in a browser;
+a locally present handler alone does not prove correctness.
+Add generic architectural protections to
 ADS core and keep domain/component-specific rules registered in project setup.
 
 Write or update the imported item's local README with public usage, required

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

@@ -55,7 +55,7 @@ If no published distribution exists, build and pack the tooling checkout with
 From inside an existing test project:
 
 ```sh
-ads_tool_package="/absolute/path/to/reqvire-org-ads-0.3.1.tgz"
+ads_tool_package="/absolute/path/to/reqvire-org-ads-0.3.2.tgz"
 npx --yes --package "$ads_tool_package" ads --help
 npx --yes --package "$ads_tool_package" ads init --framework react --tool-package "$ads_tool_package"
 npm install
@@ -93,7 +93,8 @@ component rules through the project's plugin adapter and `ds.config.json`, then
 run its actual build. Use `lint-config` directly for custom pipeline integration
 or debugging, not as a separate routine setup step.
 
-Use ADS 0.3.1 or later for the shared-resource preview compiler. `mcp` starts stdio
+Use ADS 0.3.2 or later for the closed foundation contract and recoverable
+shared-resource preview compiler. `mcp` starts stdio
 plus its local website; `showcase` starts the browser-only MCP runtime. Open the existing runtime URL from `ads_status` when
 connected; otherwise use `npm run dev:showcase` or the installed `ads showcase`.
 The tool client discovers entries and renders MCP Apps. Init adds the launch

package/dist/skills/ads-motion/SKILL.md

@@ -47,7 +47,11 @@ unrelated statements. Its real re-export may accompany removal of a redundant
 `export {};` placeholder; do not add empty exports. A `tokens` manifest lists the foundation
 entry in `companionFiles`: when creating/deleting a canonical token file such as
 `fonts.css`, include only its required import change there in the same patch.
-Preserve other imports/comments and the canonical order. Use `dryRun: true` to
+Preserve other imports/comments and the canonical order. Runtime owner manifests
+also list a `ds.config.json` companion: change only that owner's `inlineStyleFiles`
+and `boundaries.styleWrites` entries together with its source. Unused permissions
+fail the core checks; do not pre-register a boundary without its implementation.
+Use `dryRun: true` to
 inspect validation; applying re-runs the gates. Fix rejected patches in their
 owner. Report unsupported coupled changes instead of bypassing a rejection with
 direct source writes. Shared styles/helpers use `foundation`, root guides use
@@ -188,6 +192,15 @@ source definitions and values; inspecting definitions does not prove UI parity.
 The tool keeps the shared naming contract; sample templates and their token
 lists belong to the project.
 
+A public review pattern may be covered by real token or composition scenarios;
+it needs no redundant standalone entry. Remove an optional scenario only while
+retaining reachable render coverage. Keep directory ownership anchored by its
+runtime entry (`index` or a file matching the directory name) or colocated fixture.
+Import colocated image/font fixtures so MCP serves them through asset resources.
+For a broken-image case, use a local failing fixture, rather than an external
+network failure or a domain-specific CSP exception. Production asset APIs remain
+unrestricted by this fixture guidance.
+
 Scenarios, colocated fixtures and helpers are development-only. Never export them
 from the runtime barrel or import them in production, including through aliases,
 re-exports or dynamic imports. They may not import application stores, routers,
@@ -198,6 +211,27 @@ Use local simulated services in fixtures. Tests may import fixtures; load real
 foundation CSS rather than assigning shared token values in JavaScript. Keep
 full-app integration harnesses and workflow coverage in application test support.
 
+Foundation CSS is checked, not an escape hatch. Value sheets define shared tokens
+on the document root/themes; `fonts.css` holds font-face metadata. `base.css` has
+three closed roles: root/body typography, canvas and theme defaults; limited native
+normalization; and global focus indicators/reduced-motion rules. Every selector
+branch, property and value must fit its role. Token-backed control skins, layout,
+interactive state rules and owner hooks are rejected even through `:where()`.
+Do not copy an unchecked upstream preflight or turn a component repair into a reset.
+Keep behavior and skin in their runtime owner. Put demo-only sizing and framing
+in a public review/layout pattern; add component props for a deliberate runtime
+API need. Preserve required capabilities while following ownership rules.
+Browser review still verifies the effects.
+
+Invalid metadata and source failures keep the managed compiler alive for repairs.
+Read `ads_status.build` or `ads://project/build`, fix the owner, then wait for current
+successful output. If the builder exited, fix its command and invoke the preview
+again; ADS starts one fresh child without an MCP reconnect. Compiler-code changes
+also reload on the next preview invocation. Reconnect the client when upgrading
+the ADS server package itself. Persistent SSE/notification streams make
+`networkidle` unsuitable: wait for the App's current ready/error state instead.
+
+
 
 
 Register component/project Oxlint plugins and rules in `ds.config.json`. Use
@@ -205,7 +239,14 @@ scoped `oxlint.overrides` for justified file-specific settings; never edit
 `.ds/oxlintrc.json`. These overrides configure Oxlint, not the independent
 architecture checks in `ads check`. Measured renderer properties and documented
 non-state hooks use explicit `boundaries`; shared token writes and primitive
-state overrides cannot be allowlisted. Add generic architectural protections to
+state overrides cannot be allowlisted. When migrating JSX inline geometry to
+imperative writes, port the source and replace its own boundary entries together
+in the owner's patch. Remove obsolete `inlineStyleFiles` entries and unused
+`styleWrites` properties; do not broaden permissions to keep a migration passing.
+Pointer-capture advisories call for review of cancellation, capture loss and
+teardown, including cleanup delegated to hooks. Verify actual cleanup in a browser;
+a locally present handler alone does not prove correctness.
+Add generic architectural protections to
 ADS core and keep domain/component-specific rules registered in project setup.
 
 - Motion constants belong in the project's token layer. Shared token meanings

package/dist/style-boundaries.mjs

@@ -0,0 +1,59 @@
+import path from "node:path";
+import ts from "typescript";
+import { isUiCssProperties, styleAccessProperty } from "./boundaries.mjs";
+import { uiOperation } from "./ui-framework.mjs";
+
+const nameOf = node => node && (ts.isIdentifier(node) || ts.isStringLiteralLike(node)) ? node.text : null;
+
+/** Audit explicit permissions without inferring project-specific style APIs. */
+export function inspectStyleBoundaries({ root, config }, program, report) {
+  const checker = program.getTypeChecker(), usage = new Map();
+  function inspect(file) {
+    if (usage.has(file)) return usage.get(file);
+    const result = { inline: false, writes: new Set() }, source = program.getSourceFile(file);
+    function visit(node) {
+      if ((ts.isJsxAttribute(node) && nameOf(node.name) === "style") || isUiCssProperties(node, checker)) result.inline = true;
+      if (ts.isCallExpression(node) && uiOperation(node.expression, checker) === "createElement") {
+        const props = node.arguments[1];
+        if (props && ts.isObjectLiteralExpression(props) && props.properties.some(property => nameOf(property.name) === "style")) result.inline = true;
+      }
+      const property = styleAccessProperty(node);
+      if (typeof property === "string") result.writes.add(property);
+      ts.forEachChild(node, visit);
+    }
+    if (source) visit(source);
+    usage.set(file, result);
+    return result;
+  }
+  const configFile = path.join(root, "ds.config.json");
+  for (const file of config.inlineStyleFiles) {
+    if (!inspect(path.resolve(root, file)).inline) report(configFile, "stale-style-boundary", `inlineStyleFiles entry ${file} has no JSX/factory style or UI CSSProperties use. Remove the unused permission; migrate source and its own boundary entries together in the owner's patch.`);
+  }
+  for (const { file, properties } of config.boundaries.styleWrites) {
+    const used = inspect(path.resolve(root, file)).writes;
+    for (const property of properties) if (!used.has(property)) report(configFile, "stale-style-boundary", `styleWrites entry ${file} never writes ${property}. Remove the unused property in the owner's source/boundary patch.`);
+  }
+}
+
+/** A local review signal, never proof that delegated cleanup is absent/correct. */
+export function pointerCaptureAdvisories(source) {
+  const captures = [], cleanup = [];
+  function hasHandler(node) {
+    while (node && (ts.isJsxExpression(node) || ts.isParenthesizedExpression(node) || ts.isAsExpression(node) || ts.isNonNullExpression(node))) node = node.expression;
+    return !!node && ![ts.SyntaxKind.NullKeyword, ts.SyntaxKind.FalseKeyword].includes(node.kind) && !(ts.isIdentifier(node) && node.text === "undefined");
+  }
+  function visit(node) {
+    if (ts.isCallExpression(node) && ts.isPropertyAccessExpression(node.expression)) {
+      if (node.expression.name.text === "setPointerCapture") captures.push(node);
+      if (node.expression.name.text === "addEventListener" && node.arguments[0] && ts.isStringLiteralLike(node.arguments[0]) && node.arguments[0].text === "lostpointercapture" && hasHandler(node.arguments[1])) cleanup.push(node);
+    }
+    if ((ts.isJsxAttribute(node) || ts.isPropertyAssignment(node) || ts.isMethodDeclaration(node)) && /^(?:onLostPointerCapture(?:Capture)?|onlostpointercapture)$/.test(nameOf(node.name) ?? "") && (ts.isMethodDeclaration(node) || hasHandler(node.initializer))) cleanup.push(node);
+    if (ts.isBinaryExpression(node) && node.operatorToken.kind === ts.SyntaxKind.EqualsToken && ts.isPropertyAccessExpression(node.left) && node.left.name.text === "onlostpointercapture" && hasHandler(node.right)) cleanup.push(node);
+    ts.forEachChild(node, visit);
+  }
+  visit(source);
+  return cleanup.length ? [] : captures.map(node => {
+    const position = source.getLineAndCharacterOfPosition(node.getStart(source));
+    return { rule: "pointer-capture-review", line: position.line + 1, column: position.character + 1, message: "Pointer capture has no locally visible lostpointercapture cleanup handler. Verify cancellation and capture-loss cleanup, including any delegated hook/helper. This advisory does not prove cleanup is missing or correct." };
+  });
+}

package/dist/units.mjs

@@ -84,7 +84,19 @@ export function inspectUnits(options) {
   }
   walk(dsRoot);
   files.sort();
-  const directoryUnits = files.filter(file => /(?:^|\/)Scenario\.[cm]?[jt]sx?$/.test(file)).map(file => slash(path.dirname(file))).sort((a, b) => b.length - a.length);
+  // Runtime entry conventions keep directory ownership stable when an optional
+  // preview is removed. A flat scenario family still denotes separate owners.
+  const sameName = name => name.replace(/[-_]/g, "").toLowerCase();
+  const flatFamilies = new Set(files.filter(file => /\.scenario\.[cm]?[jt]sx?$/.test(file)).map(file => path.posix.dirname(file)));
+  const directories = new Set(files.filter(file => /(?:^|\/)Scenario\.[cm]?[jt]sx?$/.test(file)).map(file => slash(path.dirname(file))));
+  for (const file of files) {
+    if (!/^(?:components|patterns|composition)\//.test(file) || !source.test(file)) continue;
+    const directory = slash(path.dirname(file)), name = path.basename(file).replace(source, "");
+    if (!directory.includes("/") || /\.(?:scenario|fixture|scenario-adapter)$/.test(name)) continue;
+    if (flatFamilies.has(directory)) continue;
+    if (name === "index" || sameName(name) === sameName(path.posix.basename(directory)) || name === "fixture") directories.add(directory);
+  }
+  const directoryUnits = [...directories].sort((a, b) => b.length - a.length);
   const flatUnits = [...new Set(files.filter(file => /^(?:components|patterns|composition)\//.test(file) && source.test(file) && !directoryUnits.some(directory => file.startsWith(directory + "/"))).map(file => {
     const base = path.basename(file).split(".")[0];
     return slash(path.join(path.dirname(file), base));
@@ -120,10 +132,15 @@ export function inspectUnits(options) {
     const file = slash(path.relative(root, path.join(dsRoot, relative)));
     if (!units.get(id).files.includes(file)) units.get(id).files.push(file);
   }
+  for (const unit of units.values()) if (boundaryCompanion(unit.id)) {
+    (unit.companionFiles ??= []).push({ path: "ds.config.json", allowedChanges: "Only this owner's inlineStyleFiles and boundaries.styleWrites entries, together with its source change; preserve all other configuration and peer permissions." });
+  }
   return { units: [...units.values()].sort((a, b) => a.id.localeCompare(b.id)), owner, publicEntry, stylesEntry, tokenDir,
     relative: file => slash(path.relative(dsRoot, path.resolve(root, file))) };
 }
 
+function boundaryCompanion(unit) { return !["configuration", "documentation", "assets"].includes(unit.split("/")[0]); }
+
 export function validateUnitId(unit) {
   if (typeof unit !== "string" || unit.length > 256 || !/^[A-Za-z0-9_-]+(?:\/[A-Za-z0-9_-]+)*$/.test(unit) || ["components", "patterns", "composition"].includes(unit)) throw fail("Select one ADS unit ID from ads_units or an unoccupied owner path following its colocation convention.");
 }
@@ -134,6 +151,7 @@ export function checkUnitFiles(options, unit, changes, inventory = inspectUnits(
   for (const change of changes) {
     const relative = inventory.relative(change.path);
     if (allowNew && unit === "configuration") continue; // The candidate must register every setup/extension file.
+    if (change.path === "ds.config.json" && boundaryCompanion(unit)) continue; // Validated against only this owner below.
     if (relative === inventory.publicEntry) continue;
     if (unit === "tokens" && relative === inventory.stylesEntry) continue; // Controlled foundation import bookkeeping.
     if (allowNew && change.originalContent === null && (relative.startsWith(unit + "/") || relative.startsWith(unit + "."))) continue;
@@ -153,6 +171,24 @@ export function checkUnitCandidate(afterOptions, unit, changes, before) {
     if (unit === "configuration" && (entry.id === "configuration" || after.owner(relative) === "configuration")) continue;
     if (after.owner(relative) !== entry.id) throw fail("A patch cannot change ownership of existing peer units. Choose an unoccupied owner path.", file);
   }
+  const boundaryChange = changes.find(change => change.path === "ds.config.json");
+  if (boundaryChange && unit !== "configuration") {
+    if (!boundaryCompanion(unit) || typeof boundaryChange.originalContent !== "string" || typeof boundaryChange.content !== "string") throw fail("This unit cannot create/delete configuration.", boundaryChange.path);
+    if (!changes.some(change => change.path !== boundaryChange.path && (before.owner(before.relative(change.path)) === unit || after.owner(after.relative(change.path)) === unit))) throw fail("Boundary companions require a source change in the selected owner.", boundaryChange.path);
+    function peerPolicy(content, inventory) {
+      const config = JSON.parse(content);
+      const owns = file => typeof file === "string" && inventory.owner(inventory.relative(file)) === unit;
+      config.inlineStyleFiles = (config.inlineStyleFiles ?? []).filter(file => !owns(file));
+      config.boundaries = { ...config.boundaries, styleWrites: (config.boundaries?.styleWrites ?? []).filter(entry => !owns(entry.file)) };
+      return config;
+    }
+    function canonical(value) {
+      if (Array.isArray(value)) return value.map(canonical);
+      if (value && typeof value === "object") return Object.fromEntries(Object.keys(value).sort().map(key => [key, canonical(value[key])]));
+      return value;
+    }
+    if (JSON.stringify(canonical(peerPolicy(boundaryChange.originalContent, before))) !== JSON.stringify(canonical(peerPolicy(boundaryChange.content, after)))) throw fail("Boundary companion patches may change only inlineStyleFiles and styleWrites entries owned by the selected unit; preserve all other configuration and peer permissions.", boundaryChange.path);
+  }
   const foundationChange = changes.find(change => before.relative(change.path) === before.stylesEntry);
   if (unit === "tokens" && foundationChange) {
     const { originalContent: current, content: proposed } = foundationChange;

package/docs/ADS.md

@@ -169,6 +169,35 @@ custom styling in fixture files. The ADS frame pattern uses `--ux-*`. Foreign br
 CSS imports the approved token files in order; shared assignments belong in
 those token files, never in consumer styles or component state overrides.
 
+Foundation roles are enforced by `foundation-role`, `foundation-selector` and
+`foundation-import`, alongside the regular token checks. Shared definitions
+belong on the document root or explicit root themes; ordinary declarations belong
+in `base.css`, and font-face descriptors in optional `fonts.css`. The entry imports
+canonical sheets; those sheets cannot import another styling layer. Component
+classes, IDs, data/ARIA hooks, contextual selectors, keyframes and scoped UI rules
+are rejected in the foundation, including nested functional selectors. Raw visual
+values and undefined token references are checked in native defaults too; literal
+font-face metadata keeps its separate asset role.
+
+`base.css` has three closed roles:
+
+- Document defaults: root/body typography, canvas colors and theme behavior,
+  global text selection and document scrollbars.
+- Native resets: permitted normalization properties and values, such as zero
+  spacing, inherited control typography, list resets and responsive replaced media.
+- Global accessibility: universal `:focus-visible` outline rules, and reduced-motion
+  overrides inside `@media (prefers-reduced-motion: reduce)`.
+
+The `foundation-role` check validates every selector branch, property and value.
+Native selectors are not a bypass: token-backed button backgrounds, flex/grid
+layout, component-specific focus rules and hover/disabled skins are rejected.
+Shared token definitions belong in value sheets, not `base.css`. No project token
+names are embedded in this policy. A zero-specificity `:where()` wrapper does not
+change ownership. Put component design and animation in Linaria owners, and
+scenario layout variations in typed public review-pattern props. Browser review
+still checks the effects and accessibility of permitted defaults.
+
+
 Store original branding and its usage, credits, and licenses in
 `assets/brand/`, and fonts in `assets/fonts/`. Configure generated icons and
 asset mounts as described in the [branding guide](GUIDE.md#branding).
@@ -262,10 +291,14 @@ The checks enforce the architecture's ownership boundaries:
 | Tokens and styles | Fixed token vocabulary, required definitions, declared value types and references, raw visual values, shared-token assignments, foundation import order, and component/pattern namespaces |
 | Public API and dependencies | Consumers use public ADS imports; ADS implementations and showcase do not import application source; runtime code does not import showcase fixtures |
 | Interaction policy | Primitive state variables stay inside components; non-state customization hooks require explicit registration |
-| Renderer exceptions | Inline JSX styles and imperative style writes require narrow configured boundaries; public props omit inherited style and reject open-ended visual strings |
+| Renderer exceptions | Inline styles and imperative writes require used, narrow configured boundaries; stale entries fail; public props omit inherited style and reject open-ended visual strings |
 | Preview ownership | Scenarios define no CSS, custom classes, or native controls; all declared tokens and public renderable UI have reachable registered scenarios; token references must exist; legacy catalogue pages are checked when present |
 | Assets | Source/public collisions and configured generated artifacts in source are rejected |
 
+Pointer capture without locally visible capture-loss cleanup produces a
+nonblocking advisory. Review delegated cleanup and browser behavior; neither a
+warning nor a handler's presence establishes lifecycle correctness.
+
 Document a new ownership exception with its guard/configuration change and
 tests. Passing static checks establishes only the policies and source formats
 they cover. Browser review and behavior tests still verify accessibility,