@reqvire-org/ads 0.3.2 → 0.3.5

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
@@ -42,6 +46,23 @@ ADS gates. For binary/large assets, generate `git diff --binary --full-index` in
 stay out of model context. Binary changes require Git. When editing is disabled,
 use the client's normal source-editing tools.
 
+
+Controllers are UI behavior owners: private helpers stay with their component or
+pattern; reusable controllers use discovered `controllers/<Name>` units. Use the
+project's configured framework and declared dependencies, or plain TypeScript,
+browser APIs and local helpers. MCP hosts supply no ad hoc runtime APIs. The
+framework setting selects compilation/mounting; controller checks also validate
+imports. For controller/behavior work, read `ads://guides/behaviors` (offline:
+the installed ADS package's `docs/BEHAVIORS.md`). Discover registered guarantees
+with `ads_behaviors`; use `ads_verify` for selected real checks. Optional
+`exercises` links public behavioral APIs to scenarios; keep `covers` for rendered
+UI. Registration and demonstration are not passing evidence. `behavior.json`,
+scenarios, fixtures and checks stay out of production exports/imports. Verify
+current results, including lifecycle setup/cleanup/setup and the actual browser
+profile when promised. React StrictMode needs a development harness; wrapping a
+production widget cannot replay development effects. Keep dynamic behavior and
+capabilities intact rather than rewriting them only for static coverage.
+
 Before trusting a preview after edits, check `ads_status.build` or
 `ads://project/build`. Fix build diagnostics in owned source; an older view or
 unreported freshness is not evidence of current code. Notifications may not
@@ -193,6 +214,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,
@@ -210,8 +240,15 @@ 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.
-Put skin/state/animation in the Linaria owner, and scenario layout variations in
-the public review pattern's typed API. Browser review still verifies the effects.
+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.
+Use tokens for absolute/font-relative lengths, including `ch`, `ex`, `cap`, `ic`
+and `lh`; calculations and fallback values follow the same rule. Structural
+angle units remain available for orientation, skew and spin. Put tunable visual
+angles in project tokens; static checks cannot infer that intent. Percentages,
+grid fractions and viewport/container relationships retain structural use.
+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
@@ -229,7 +266,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
@@ -74,6 +78,23 @@ ADS gates. For binary/large assets, generate `git diff --binary --full-index` in
 stay out of model context. Binary changes require Git. When editing is disabled,
 use the client's normal source-editing tools.
 
+Controllers are UI behavior owners: private helpers stay with their component or
+pattern; reusable controllers use discovered `controllers/<Name>` units. Use the
+project's configured framework and declared dependencies, or plain TypeScript,
+browser APIs and local helpers. MCP hosts supply no ad hoc runtime APIs. The
+framework setting selects compilation/mounting; controller checks also validate
+imports. For controller/behavior work, read `ads://guides/behaviors` (offline:
+the installed ADS package's `docs/BEHAVIORS.md`). Discover registered guarantees
+with `ads_behaviors`; use `ads_verify` for selected real checks. Optional
+`exercises` links public behavioral APIs to scenarios; keep `covers` for rendered
+UI. Registration and demonstration are not passing evidence. `behavior.json`,
+scenarios, fixtures and checks stay out of production exports/imports. Verify
+current results, including lifecycle setup/cleanup/setup and the actual browser
+profile when promised. React StrictMode needs a development harness; wrapping a
+production widget cannot replay development effects. Keep dynamic behavior and
+capabilities intact rather than rewriting them only for static coverage.
+
+
 Check `ads_status.previewWatch` before launching another preview builder. With a
 managed watcher, edit owned sources, wait for the rebuild and invoke the preview
 again; the client already starts and stops the builder through `ads mcp`. Check
@@ -149,7 +170,7 @@ Do not assume it has a particular component, hook, font, or token helper.
 Record the source revision and required dependencies.
 
 Use the ADS import workflow to bring selected existing ADS items into the target,
-or assimilation to create a native component from an upstream library. Follow
+or migration to create a native component from an upstream library. Follow
 those workflows directly if the corresponding skills are unavailable: copy
 selected source and its dependency closure, or study/reproduce the upstream
 contract; integrate local ownership, exports, styles, assets, credits, applicable
@@ -331,6 +352,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,
@@ -348,8 +378,15 @@ 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.
-Put skin/state/animation in the Linaria owner, and scenario layout variations in
-the public review pattern's typed API. Browser review still verifies the effects.
+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.
+Use tokens for absolute/font-relative lengths, including `ch`, `ex`, `cap`, `ic`
+and `lh`; calculations and fallback values follow the same rule. Structural
+angle units remain available for orientation, skew and spin. Put tunable visual
+angles in project tokens; static checks cannot infer that intent. Percentages,
+grid fractions and viewport/container relationships retain structural use.
+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
@@ -367,7 +404,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

@@ -241,3 +241,10 @@ Run `npm run build` after adding or changing components. Add meaningful tests
 for stateful behavior, accessibility, gestures, or async lifecycle where needed.
 Run `npm run dev` to inspect the real showcase. A screenshot alone does not
 verify interaction or animation. Generated output and dependencies are not source.
+
+Shared behavior may live in `controllers/<Name>/`; private controllers stay with
+their component/pattern. Use the configured framework and declared dependencies.
+Behavior contracts/checks are development-only, and scenario `exercises` links
+public hooks to demonstrations separately from rendered `covers`. Read the
+installed ADS package's `docs/BEHAVIORS.md` or MCP `ads://guides/behaviors` before
+registering guarantees, profiles and verification.

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

@@ -102,7 +102,7 @@ script but does not install the project preview compiler. Integrate its graph
 compiler/mount adapter and configure `mcp.previewManifest` plus `mcp.previewWatch`;
 then use the same foundation and Linaria extraction as the application. Source discovery,
 selected component/pattern/style/brand imports, explicit theme-value imports, and
-assimilation are agent workflows. There is no CLI `import` command. Core checks
+migration are agent workflows. There is no CLI `import` command. Core checks
 do not copy source, import values, or establish behavior/motion parity; continue
 project type checking, meaningful tests, and browser comparisons.
 

package/dist/skills/ads-designer/references/design-craft.md

@@ -56,7 +56,7 @@ changing them to a generic default.
 
 Keep typed props, examples, state behavior, token hooks, and important tradeoffs
 in the item README. Record concrete upstream influences, authors, revision, and
-applicable notices when importing or assimilating source. Do not describe an
+applicable notices when importing or migrating source. Do not describe an
 adapted implementation as independent solely because it uses native primitives.
 
 Run the actual project's checks after changes and inspect the real consumer

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
@@ -38,6 +42,23 @@ ADS gates. For binary/large assets, generate `git diff --binary --full-index` in
 stay out of model context. Binary changes require Git. When editing is disabled,
 use the client's normal source-editing tools.
 
+Controllers are UI behavior owners: private helpers stay with their component or
+pattern; reusable controllers use discovered `controllers/<Name>` units. Use the
+project's configured framework and declared dependencies, or plain TypeScript,
+browser APIs and local helpers. MCP hosts supply no ad hoc runtime APIs. The
+framework setting selects compilation/mounting; controller checks also validate
+imports. For controller/behavior work, read `ads://guides/behaviors` (offline:
+the installed ADS package's `docs/BEHAVIORS.md`). Discover registered guarantees
+with `ads_behaviors`; use `ads_verify` for selected real checks. Optional
+`exercises` links public behavioral APIs to scenarios; keep `covers` for rendered
+UI. Registration and demonstration are not passing evidence. `behavior.json`,
+scenarios, fixtures and checks stay out of production exports/imports. Verify
+current results, including lifecycle setup/cleanup/setup and the actual browser
+profile when promised. React StrictMode needs a development harness; wrapping a
+production widget cannot replay development effects. Keep dynamic behavior and
+capabilities intact rather than rewriting them only for static coverage.
+
+
 Before trusting a preview after edits, check `ads_status.build` or
 `ads://project/build`. Fix build diagnostics in owned source; an older view or
 unreported freshness is not evidence of current code. Notifications may not
@@ -298,6 +319,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,
@@ -315,8 +345,15 @@ 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.
-Put skin/state/animation in the Linaria owner, and scenario layout variations in
-the public review pattern's typed API. Browser review still verifies the effects.
+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.
+Use tokens for absolute/font-relative lengths, including `ch`, `ex`, `cap`, `ic`
+and `lh`; calculations and fallback values follow the same rule. Structural
+angle units remain available for orientation, skew and spin. Put tunable visual
+angles in project tokens; static checks cannot infer that intent. Percentages,
+grid fractions and viewport/container relationships retain structural use.
+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
@@ -334,7 +371,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

@@ -102,7 +102,7 @@ script but does not install the project preview compiler. Integrate its graph
 compiler/mount adapter and configure `mcp.previewManifest` plus `mcp.previewWatch`;
 then use the same foundation and Linaria extraction as the application. Source discovery,
 selected component/pattern/style/brand imports, explicit theme-value imports, and
-assimilation are agent workflows. There is no CLI `import` command. Core checks
+migration are agent workflows. There is no CLI `import` command. Core checks
 do not copy source, import values, or establish behavior/motion parity; continue
 project type checking, meaningful tests, and browser comparisons.
 

package/dist/skills/{ads-assimilate → ads-migrate}/SKILL.md

@@ -1,9 +1,9 @@
 ---
-name: ads-assimilate
-description: "Implement or refine a native design-system component from a component-library URL, studying the original implementation and verifying behavior, visuals, and motion against the real reference. Use for component assimilation, including local documentation and justified usage lint rules; not for simply installing or wrapping a dependency."
+name: ads-migrate
+description: "Implement or refine a native design-system component from a component-library URL, studying the original implementation and verifying behavior, visuals, and motion against the real reference. Use for component migration, including local documentation and justified usage lint rules; not for simply installing or wrapping a dependency."
 ---
 
-# ADS Assimilate
+# ADS Migrate
 
 When ADS MCP is connected, discover public UI and addressable scenarios with
 `ads_status`/`ads_catalog`; use `ads_tokens` for definitions and values, and
@@ -27,7 +27,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
@@ -39,6 +43,23 @@ ADS gates. For binary/large assets, generate `git diff --binary --full-index` in
 stay out of model context. Binary changes require Git. When editing is disabled,
 use the client's normal source-editing tools.
 
+
+Controllers are UI behavior owners: private helpers stay with their component or
+pattern; reusable controllers use discovered `controllers/<Name>` units. Use the
+project's configured framework and declared dependencies, or plain TypeScript,
+browser APIs and local helpers. MCP hosts supply no ad hoc runtime APIs. The
+framework setting selects compilation/mounting; controller checks also validate
+imports. For controller/behavior work, read `ads://guides/behaviors` (offline:
+the installed ADS package's `docs/BEHAVIORS.md`). Discover registered guarantees
+with `ads_behaviors`; use `ads_verify` for selected real checks. Optional
+`exercises` links public behavioral APIs to scenarios; keep `covers` for rendered
+UI. Registration and demonstration are not passing evidence. `behavior.json`,
+scenarios, fixtures and checks stay out of production exports/imports. Verify
+current results, including lifecycle setup/cleanup/setup and the actual browser
+profile when promised. React StrictMode needs a development harness; wrapping a
+production widget cannot replay development effects. Keep dynamic behavior and
+capabilities intact rather than rewriting them only for static coverage.
+
 Before trusting a preview after edits, check `ads_status.build` or
 `ads://project/build`. Fix build diagnostics in owned source; an older view or
 unreported freshness is not evidence of current code. Notifications may not
@@ -71,8 +92,8 @@ workflows. Do not look for a built-in or optional UI catalogue in the tool.
 Invocation accepts a library/repository/documentation URL as its first argument:
 
 ```text
-$ads-assimilate <library-url> [component-name] [requirements]
-$ads-assimilate https://github.com/emilkowalski/sonner toast
+$ads-migrate <library-url> [component-name] [requirements]
+$ads-migrate https://github.com/emilkowalski/sonner toast
 ```
 
 The URL is the required reference, not a request to install the library into the
@@ -143,7 +164,7 @@ the scenario; larger entries belong under `composition/`. Browsing pages only
 select these entries. The scenario labels, controls and review layouts are public ADS entities with defined
 APIs. The outer shell belongs to the tool client. Showcase/scenario files define no CSS, custom classes, or widget markup.
 Change the owning ADS pattern when a frame layout is missing; do not recreate
-the assimilated UI there or override its internals.
+the migrated UI there or override its internals.
 
 The showcase is a minimal shell plus an MCP client and Apps host, supplied by ADS
 tooling. It discovers Tokens/Components/Patterns/Composition entries through MCP
@@ -241,6 +262,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,
@@ -258,8 +288,15 @@ 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.
-Put skin/state/animation in the Linaria owner, and scenario layout variations in
-the public review pattern's typed API. Browser review still verifies the effects.
+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.
+Use tokens for absolute/font-relative lengths, including `ch`, `ex`, `cap`, `ic`
+and `lh`; calculations and fallback values follow the same rule. Structural
+angle units remain available for orientation, skew and spin. Put tunable visual
+angles in project tokens; static checks cannot infer that intent. Percentages,
+grid fractions and viewport/container relationships retain structural use.
+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
@@ -277,7 +314,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.
 
 Update meaningful variants, states, content, themes, and container sizes in the

package/dist/skills/ads-migrate/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "ADS Migrate"
+  short_description: "Adapt reference components into a native design system"
+  default_prompt: "Use $ads-migrate with a component-library URL to implement and verify a native design-system component."

package/dist/skills/{ads-assimilate → ads-migrate}/references/cli.md

@@ -102,7 +102,7 @@ script but does not install the project preview compiler. Integrate its graph
 compiler/mount adapter and configure `mcp.previewManifest` plus `mcp.previewWatch`;
 then use the same foundation and Linaria extraction as the application. Source discovery,
 selected component/pattern/style/brand imports, explicit theme-value imports, and
-assimilation are agent workflows. There is no CLI `import` command. Core checks
+migration are agent workflows. There is no CLI `import` command. Core checks
 do not copy source, import values, or establish behavior/motion parity; continue
 project type checking, meaningful tests, and browser comparisons.
 

package/dist/skills/{ads-assimilate → ads-migrate}/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.
 
@@ -96,3 +112,14 @@ README and in a References and credits section in the component-local README.
 Link the library and the actual source/docs/articles studied, identify the
 version or commit, name the authors, and explain the concrete influences.
 Document material adaptations and agreed deviations beside the public contract.
+
+## Behavioral evidence
+
+Keep private controllers in their owner; extract a shared controller only for a
+real reuse need. Register optional behavior guarantees and real colocated checks;
+see `ads://guides/behaviors` or the installed package's `docs/BEHAVIORS.md`. Link
+public hooks with scenario `exercises`, while `covers` still requires rendered UI.
+Move reviewed scratchpad investigations into maintained owner checks. Disabling
+StrictMode can isolate an upstream lifecycle defect; keep a development StrictMode
+check and verify the native port's setup/cleanup/setup independently. Use first-
+render browser cases for lazy intrinsic sizing, retaining offscreen rendering.

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
@@ -59,6 +63,23 @@ ADS gates. For binary/large assets, generate `git diff --binary --full-index` in
 stay out of model context. Binary changes require Git. When editing is disabled,
 use the client's normal source-editing tools.
 
+
+Controllers are UI behavior owners: private helpers stay with their component or
+pattern; reusable controllers use discovered `controllers/<Name>` units. Use the
+project's configured framework and declared dependencies, or plain TypeScript,
+browser APIs and local helpers. MCP hosts supply no ad hoc runtime APIs. The
+framework setting selects compilation/mounting; controller checks also validate
+imports. For controller/behavior work, read `ads://guides/behaviors` (offline:
+the installed ADS package's `docs/BEHAVIORS.md`). Discover registered guarantees
+with `ads_behaviors`; use `ads_verify` for selected real checks. Optional
+`exercises` links public behavioral APIs to scenarios; keep `covers` for rendered
+UI. Registration and demonstration are not passing evidence. `behavior.json`,
+scenarios, fixtures and checks stay out of production exports/imports. Verify
+current results, including lifecycle setup/cleanup/setup and the actual browser
+profile when promised. React StrictMode needs a development harness; wrapping a
+production widget cannot replay development effects. Keep dynamic behavior and
+capabilities intact rather than rewriting them only for static coverage.
+
 Before trusting a preview after edits, check `ads_status.build` or
 `ads://project/build`. Fix build diagnostics in owned source; an older view or
 unreported freshness is not evidence of current code. Notifications may not
@@ -188,6 +209,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,
@@ -205,8 +235,15 @@ 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.
-Put skin/state/animation in the Linaria owner, and scenario layout variations in
-the public review pattern's typed API. Browser review still verifies the effects.
+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.
+Use tokens for absolute/font-relative lengths, including `ch`, `ex`, `cap`, `ic`
+and `lh`; calculations and fallback values follow the same rule. Structural
+angle units remain available for orientation, skew and spin. Put tunable visual
+angles in project tokens; static checks cannot infer that intent. Percentages,
+grid fractions and viewport/container relationships retain structural use.
+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
@@ -224,7 +261,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