@reqvire-org/ads 0.3.17 → 0.3.18

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

@@ -101,7 +101,12 @@ failed/cancelled capture does not replace existing image slots or apply source.
 If a scenario/target is newly introduced, `current` is null with an explicit
 `currentAbsent` explanation; only the real candidate image exists.
 
-Review the returned images and diagnostics, fix the draft if necessary, then apply
+The edit reply is a summary. Read `ads_results({resultId,section:"captures"})` for
+the requested image resource URIs and `section:"diagnostics"` for relevant
+messages; follow `nextCursor` when needed. Read image resources explicitly.
+Standalone `ads_capture` continues returning its selected capture directly.
+
+Review those images and diagnostics, fix the draft if necessary, then apply
 with `dryRun:false`. Apply reruns all gates. An image is promoted only when the
 accepted source revision matches the captured candidate; other proposals remain
 stale. Images do not approve a patch or certify interaction/accessibility/parity.

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

@@ -20,21 +20,67 @@ A complete failed run can contain independent passing cases. Suite interruption,
 missing/skipped cases, stale inputs and an unexplained process exit cannot certify
 a pass. Keep the reported case outcome separate from whole-run acceptance.
 
+## Retrieve only the evidence needed
+
+`ads_verify`, `ads_apply_patch` and `ads_apply_transaction` reply with counts,
+bounded acceptance, at most three failure previews and `resultId`, within 4096
+UTF-8 JSON bytes. Full validation still decides acceptance. Do not repeat a suite
+merely to recover its output, or restate the complete report in conversation.
+
+Read a relevant saved section:
+
+```js
+ads_results({resultId: "<returned ID>", section: "outcomes", status: "not_passed"})
+// Continue only when needed, with the same section and status:
+ads_results({resultId: "<returned ID>", section: "outcomes", status: "not_passed", cursor: "<nextCursor>"})
+```
+
+Pages default to 10 rows, allow at most 20 and stay within 8192 JSON bytes. The
+byte cap can return fewer rows; `nextCursor` is the continuation. Other sections
+are `checks` (pipeline steps), `diagnostics`, `advisories`, `warnings`, `changes`,
+`captures`, `acceptance`, `investigation` (mutation boundary) and `selection`.
+A row marked `detailTruncated` is a preview. To read that exact record, pass its
+`recordIndex`, the same result/section, and `offset`/`chars` (maximum 2000 UTF-16
+characters); follow `nextOffset`. Do not combine ranges with a cursor/status filter.
+Read only the relevant log range. Reading pages or ranges never executes checks.
+
+`ads://project/results` lists the latest IDs. `ads://results/<resultId>` reads a
+summary; matching query parameters read pages/ranges. Only the latest verification
+and latest mutation snapshots are retained, independently, up to 8 MiB each.
+A superseded ID fails explicitly. An oversized report retains only its summary
+with a warning; disk failure retains details in server memory until shutdown.
+Neither changes actual acceptance or applied state. These are logical JSON byte
+budgets, not token estimates; compatibility text can duplicate structured JSON.
+Saved outcomes describe completion-time evidence, not current source freshness;
+compare their revisions with `ads_behaviors` before claiming a current pass.
+
+`ads_behaviors` pages owner summaries, then an exact unit's `checks`, `guarantees`,
+`subjects`, `demonstrations` or `profiles`. Use `nextCursor` and identical filters;
+changes invalidate a discovery cursor. Read a truncated contract via its
+`sourceFile` and bounded `ads_read_file`, rather than requesting everything.
+
 ## Get a compact investigation
 
-Discover exact owner/check IDs with `ads_behaviors`, then:
+Take an outcome's exact owner/check/run IDs from `ads_results`, then:
 
 ```json
-{ "unit": "components/Example", "check": "keyboard-navigation" }
+{ "unit": "components/Example", "check": "keyboard-navigation", "runId": "<outcome runId>" }
 ```
 
-Send this to `ads_investigate`. It reads the latest bundle without running code.
+Send this to `ads_investigate`. It reads a summary within 4096 JSON bytes, without
+running code. The run ID rejects evidence superseded by another execution.
+`section: "details"`, `"requests"`, `"browserErrors"` or `"artifacts"` reads separate pages
+(default 10/max 20 rows, at most 8192 JSON bytes); artifacts themselves require
+explicit resource reads. Truncated investigation records also support
+`recordIndex`/`offset`/`chars`; keep the exact `runId` to avoid mixing evidence.
+Without a check, the tool pages available investigations.
 `ads://project/investigations` lists available entries; the returned `resourceUri`
 reads the same bundle. It records:
 
 - Project versus isolated candidate, configured framework/profile and scenario.
 - Exact input revision and the preview revision actually observed by the helper.
-- Failing step/source, observed startup viewport and relevant failed requests.
+- `details.failingStep`, `details.source`, startup viewport and failure boundary.
+- Counts for separately paged relevant requests, browser errors and artifacts.
 - Available registered trace, screenshot or context artifact resource URIs.
 - Explicit `acceptance.established` and `acceptance.unverified` scope.
 
@@ -58,7 +104,8 @@ Candidate evidence never becomes passing live-source evidence. Compare the
 recorded input revision with current `ads_behaviors` evidence; a bundle describes
 its run, and does not claim current source merely because it remains available.
 For a build/architecture rejection before behavior runs, inspect the mutation
-result's `investigation` (also retained in `ads_status.mutations.lastResult`).
+saved `investigation` section via `ads_results`. Status retains the compact
+execution summary and result ID, rather than embedding complete reports.
 
 ## Preserve the design while repairing the failure
 

package/dist/skills/ads-designer/references/guarded-editing.md

@@ -15,8 +15,10 @@ ads_apply_patch({"unit":"components/Example","patchFile":"<returned patchFile>",
 
 The dry run validates the full candidate, including affected registered behavior
 checks in an isolated project copy. Configured browser checks use that candidate's
-managed preview, not the live showcase. Inspect the returned `behavior` failures
-or the registered behavior-check results in `checks`, fix the draft and diff again.
+managed preview, not the live showcase. Read the summary, then page failing
+`outcomes`, `diagnostics` or pipeline `checks` through `ads_results` with its
+`resultId`. Inspect one exact outcome with `ads_investigate({unit,check,runId})`;
+fix the draft and diff again. See [evidence.md](evidence.md) for page/range limits.
 Keep behavior.json/specs with their owner and use registered checks; a scratchpad
 run against live source cannot verify unapplied changes. After validation, apply
 with `dryRun:false`; ADS revalidates before writing. Dry-run evidence is not saved
@@ -120,9 +122,10 @@ them through their actual public composition/customization path and list their r
 render references in covers. Do not count internal production renders as public API
 coverage. Behavioral APIs use exercises and registered guarantees instead.
 Scenario controls still use public UI. A native link/button can supply semantics
-as the single direct child of a public runtime slot when source tracing proves
-that owner clones the child with its props. An `asChild` flag alone is insufficient;
-standalone native controls and custom scenario styling remain rejected. See
+through a public runtime slot that demonstrably clones its child with owned
+props, or through matching runtime-owned selectors attached to the actual rendered
+DOM. Source ownership must be proven; an `asChild` flag or a lookalike marker is
+insufficient. Standalone controls and custom scenario styling remain rejected. See
 [scenarios.md](scenarios.md) for evidence and limits. Preserve the intended
 composition instead of substituting an unrelated styled control or adding a
 demo-only component prop. Review framing belongs in public layout patterns.

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

@@ -50,17 +50,19 @@ For on-demand current/candidate screenshots and visual dry-run review, read
 [captures.md](references/captures.md).
 For a rejected patch, failed check or loading error, read
 [evidence and diagnosis](references/evidence.md); inspect the failing boundary
-and `ads_investigate` bundle before changing APIs or verification policy.
+then page needed `ads_results` sections using the returned result ID. Inspect
+one `ads_investigate({unit,check,runId})` summary before changing APIs or policy;
+load request/error/artifact details only when relevant.
 
 For parent/child `covers`, conditional-control review, reference comparisons,
-public style-helper use, fragment-link navigation, or `scenario-render` /
-`showcase-class` findings, read [scenario contracts](references/scenarios.md). Its verification
+public style-helper use, native slot/selector composition, fragment navigation,
+or `scenario-render` / `showcase-control` / `showcase-class` findings, read [scenario contracts](references/scenarios.md). Its verification
 examples explain API visibility, reference baselines and state-transition checks.
 Traced parents can cover declared public children; verified public Linaria
 helpers do not grant custom scenario CSS.
 
 For atomic base/variant styling, helper/wrapper class composition, extracted
-custom-property arithmetic, or an
+custom-property arithmetic, typed `@property` registrations, or an
 `atomic-composition-review` / `atomic-composition-limit` advisory, read
 [atomic style composition](references/atomic-styles.md). The same guide is served
 as `ads://guides/atomic-styles`. It explains shorthand/logical conflicts and

package/dist/skills/ads-import/references/atomic-styles.md

@@ -81,6 +81,54 @@ const treatment = css`
 This is a distinct state, not two competing base atoms. Whether changing padding
 on hover is desirable remains a product decision.
 
+## Register typed custom properties without atomizing their descriptors
+
+Use a literal `@property` in its component/pattern's Linaria template when the
+browser needs a typed, interpolated runtime variable:
+
+```tsx
+const treatment = css`
+  @property --ds-example-progress {
+    syntax: "<number>";
+    inherits: false;
+    initial-value: 0;
+  }
+  opacity: var(--ds-example-progress);
+`;
+```
+
+The identifier is illustrative; use a unique name owned by the real unit.
+Registrations are document-global, even when authored beside one component.
+Put them at template level or inside conditional at-rules, never element selectors.
+Use the same ADS tag resolver described below in both product and preview builds;
+it preserves each complete registration and its conditional context instead of
+splitting syntax/inherits/initial-value into invalid atomic rules. This works for
+atomic `css` and `styled`; the browser receives CSS without a registration runtime.
+MCP delivers it inside the App document, not the outer showcase host.
+
+`property-registration` validates descriptor shape, CSS syntax/initial-value and
+ownership, and rejects conflicting schemas or registrations shared by unrelated
+owners. Identical registrations from the same owner are permitted. Runtime
+`--ds-*` / `--ux-*` variables stay with their runtime owner. A shared token's
+registration belongs beside its actual definition in a foundation value sheet;
+a namespaced owner token's registration belongs in its registered `tokens.css`.
+Neither `base.css` nor `fonts.css` becomes a registration escape hatch. Registration
+alone does not define a token or satisfy its sample/fixture coverage.
+
+Typed initial values must match their syntax and be computationally independent:
+`0px` is valid metadata; `var(--space-4)`, `1rem` and `currentColor` are not.
+The literal exemption applies only to registration descriptors. Keep design
+assignments outside them token-backed; a technical fallback is not a place to
+hide a component skin. Use literal static descriptors so guards can inspect them.
+See the [W3C registration contract](https://www.w3.org/TR/css-properties-values-api-1/#at-property-rule).
+
+Verify extracted CSS and actual interpolation, including after minification and
+inside the MCP App. A declaration can parse while a browser ignores an invalid
+registration. Keep required browser fallbacks and reduced-motion behavior; do not
+replace a valid CSS implementation with script merely to evade extraction or a
+guard limitation. These checks cover declarative registrations; arbitrary dynamic
+`CSS.registerProperty()` calls are not an ownership proof.
+
 ## Preserve custom-property arithmetic during extraction
 
 Custom properties can hold an unevaluated token stream that becomes arithmetic

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

@@ -101,7 +101,12 @@ failed/cancelled capture does not replace existing image slots or apply source.
 If a scenario/target is newly introduced, `current` is null with an explicit
 `currentAbsent` explanation; only the real candidate image exists.
 
-Review the returned images and diagnostics, fix the draft if necessary, then apply
+The edit reply is a summary. Read `ads_results({resultId,section:"captures"})` for
+the requested image resource URIs and `section:"diagnostics"` for relevant
+messages; follow `nextCursor` when needed. Read image resources explicitly.
+Standalone `ads_capture` continues returning its selected capture directly.
+
+Review those images and diagnostics, fix the draft if necessary, then apply
 with `dryRun:false`. Apply reruns all gates. An image is promoted only when the
 accepted source revision matches the captured candidate; other proposals remain
 stale. Images do not approve a patch or certify interaction/accessibility/parity.

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

@@ -20,21 +20,67 @@ A complete failed run can contain independent passing cases. Suite interruption,
 missing/skipped cases, stale inputs and an unexplained process exit cannot certify
 a pass. Keep the reported case outcome separate from whole-run acceptance.
 
+## Retrieve only the evidence needed
+
+`ads_verify`, `ads_apply_patch` and `ads_apply_transaction` reply with counts,
+bounded acceptance, at most three failure previews and `resultId`, within 4096
+UTF-8 JSON bytes. Full validation still decides acceptance. Do not repeat a suite
+merely to recover its output, or restate the complete report in conversation.
+
+Read a relevant saved section:
+
+```js
+ads_results({resultId: "<returned ID>", section: "outcomes", status: "not_passed"})
+// Continue only when needed, with the same section and status:
+ads_results({resultId: "<returned ID>", section: "outcomes", status: "not_passed", cursor: "<nextCursor>"})
+```
+
+Pages default to 10 rows, allow at most 20 and stay within 8192 JSON bytes. The
+byte cap can return fewer rows; `nextCursor` is the continuation. Other sections
+are `checks` (pipeline steps), `diagnostics`, `advisories`, `warnings`, `changes`,
+`captures`, `acceptance`, `investigation` (mutation boundary) and `selection`.
+A row marked `detailTruncated` is a preview. To read that exact record, pass its
+`recordIndex`, the same result/section, and `offset`/`chars` (maximum 2000 UTF-16
+characters); follow `nextOffset`. Do not combine ranges with a cursor/status filter.
+Read only the relevant log range. Reading pages or ranges never executes checks.
+
+`ads://project/results` lists the latest IDs. `ads://results/<resultId>` reads a
+summary; matching query parameters read pages/ranges. Only the latest verification
+and latest mutation snapshots are retained, independently, up to 8 MiB each.
+A superseded ID fails explicitly. An oversized report retains only its summary
+with a warning; disk failure retains details in server memory until shutdown.
+Neither changes actual acceptance or applied state. These are logical JSON byte
+budgets, not token estimates; compatibility text can duplicate structured JSON.
+Saved outcomes describe completion-time evidence, not current source freshness;
+compare their revisions with `ads_behaviors` before claiming a current pass.
+
+`ads_behaviors` pages owner summaries, then an exact unit's `checks`, `guarantees`,
+`subjects`, `demonstrations` or `profiles`. Use `nextCursor` and identical filters;
+changes invalidate a discovery cursor. Read a truncated contract via its
+`sourceFile` and bounded `ads_read_file`, rather than requesting everything.
+
 ## Get a compact investigation
 
-Discover exact owner/check IDs with `ads_behaviors`, then:
+Take an outcome's exact owner/check/run IDs from `ads_results`, then:
 
 ```json
-{ "unit": "components/Example", "check": "keyboard-navigation" }
+{ "unit": "components/Example", "check": "keyboard-navigation", "runId": "<outcome runId>" }
 ```
 
-Send this to `ads_investigate`. It reads the latest bundle without running code.
+Send this to `ads_investigate`. It reads a summary within 4096 JSON bytes, without
+running code. The run ID rejects evidence superseded by another execution.
+`section: "details"`, `"requests"`, `"browserErrors"` or `"artifacts"` reads separate pages
+(default 10/max 20 rows, at most 8192 JSON bytes); artifacts themselves require
+explicit resource reads. Truncated investigation records also support
+`recordIndex`/`offset`/`chars`; keep the exact `runId` to avoid mixing evidence.
+Without a check, the tool pages available investigations.
 `ads://project/investigations` lists available entries; the returned `resourceUri`
 reads the same bundle. It records:
 
 - Project versus isolated candidate, configured framework/profile and scenario.
 - Exact input revision and the preview revision actually observed by the helper.
-- Failing step/source, observed startup viewport and relevant failed requests.
+- `details.failingStep`, `details.source`, startup viewport and failure boundary.
+- Counts for separately paged relevant requests, browser errors and artifacts.
 - Available registered trace, screenshot or context artifact resource URIs.
 - Explicit `acceptance.established` and `acceptance.unverified` scope.
 
@@ -58,7 +104,8 @@ Candidate evidence never becomes passing live-source evidence. Compare the
 recorded input revision with current `ads_behaviors` evidence; a bundle describes
 its run, and does not claim current source merely because it remains available.
 For a build/architecture rejection before behavior runs, inspect the mutation
-result's `investigation` (also retained in `ads_status.mutations.lastResult`).
+saved `investigation` section via `ads_results`. Status retains the compact
+execution summary and result ID, rather than embedding complete reports.
 
 ## Preserve the design while repairing the failure
 

package/dist/skills/ads-import/references/guarded-editing.md

@@ -15,8 +15,10 @@ ads_apply_patch({"unit":"components/Example","patchFile":"<returned patchFile>",
 
 The dry run validates the full candidate, including affected registered behavior
 checks in an isolated project copy. Configured browser checks use that candidate's
-managed preview, not the live showcase. Inspect the returned `behavior` failures
-or the registered behavior-check results in `checks`, fix the draft and diff again.
+managed preview, not the live showcase. Read the summary, then page failing
+`outcomes`, `diagnostics` or pipeline `checks` through `ads_results` with its
+`resultId`. Inspect one exact outcome with `ads_investigate({unit,check,runId})`;
+fix the draft and diff again. See [evidence.md](evidence.md) for page/range limits.
 Keep behavior.json/specs with their owner and use registered checks; a scratchpad
 run against live source cannot verify unapplied changes. After validation, apply
 with `dryRun:false`; ADS revalidates before writing. Dry-run evidence is not saved
@@ -120,9 +122,10 @@ them through their actual public composition/customization path and list their r
 render references in covers. Do not count internal production renders as public API
 coverage. Behavioral APIs use exercises and registered guarantees instead.
 Scenario controls still use public UI. A native link/button can supply semantics
-as the single direct child of a public runtime slot when source tracing proves
-that owner clones the child with its props. An `asChild` flag alone is insufficient;
-standalone native controls and custom scenario styling remain rejected. See
+through a public runtime slot that demonstrably clones its child with owned
+props, or through matching runtime-owned selectors attached to the actual rendered
+DOM. Source ownership must be proven; an `asChild` flag or a lookalike marker is
+insufficient. Standalone controls and custom scenario styling remain rejected. See
 [scenarios.md](scenarios.md) for evidence and limits. Preserve the intended
 composition instead of substituting an unrelated styled control or adding a
 demo-only component prop. Review framing belongs in public layout patterns.

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

@@ -51,18 +51,20 @@ For on-demand current/candidate screenshots and visual dry-run review, read
 [captures.md](references/captures.md).
 For a rejected patch, failed check or loading error, read
 [evidence and diagnosis](references/evidence.md); inspect the failing boundary
-and `ads_investigate` bundle before changing APIs or verification policy.
+then page needed `ads_results` sections using the returned result ID. Inspect
+one `ads_investigate({unit,check,runId})` summary before changing APIs or policy;
+load request/error/artifact details only when relevant.
 
 
 For parent/child `covers`, conditional-control review, reference comparisons,
-public style-helper use, fragment-link navigation, or `scenario-render` /
-`showcase-class` findings, read [scenario contracts](references/scenarios.md). Its verification
+public style-helper use, native slot/selector composition, fragment navigation,
+or `scenario-render` / `showcase-control` / `showcase-class` findings, read [scenario contracts](references/scenarios.md). Its verification
 examples explain API visibility, reference baselines and state-transition checks.
 Traced parents can cover declared public children; verified public Linaria
 helpers do not grant custom scenario CSS.
 
 For atomic base/variant styling, helper/wrapper class composition, extracted
-custom-property arithmetic, or an
+custom-property arithmetic, typed `@property` registrations, or an
 `atomic-composition-review` / `atomic-composition-limit` advisory, read
 [atomic style composition](references/atomic-styles.md). The same guide is served
 as `ads://guides/atomic-styles`. It explains shorthand/logical conflicts and

package/dist/skills/ads-migrate/references/atomic-styles.md

@@ -81,6 +81,54 @@ const treatment = css`
 This is a distinct state, not two competing base atoms. Whether changing padding
 on hover is desirable remains a product decision.
 
+## Register typed custom properties without atomizing their descriptors
+
+Use a literal `@property` in its component/pattern's Linaria template when the
+browser needs a typed, interpolated runtime variable:
+
+```tsx
+const treatment = css`
+  @property --ds-example-progress {
+    syntax: "<number>";
+    inherits: false;
+    initial-value: 0;
+  }
+  opacity: var(--ds-example-progress);
+`;
+```
+
+The identifier is illustrative; use a unique name owned by the real unit.
+Registrations are document-global, even when authored beside one component.
+Put them at template level or inside conditional at-rules, never element selectors.
+Use the same ADS tag resolver described below in both product and preview builds;
+it preserves each complete registration and its conditional context instead of
+splitting syntax/inherits/initial-value into invalid atomic rules. This works for
+atomic `css` and `styled`; the browser receives CSS without a registration runtime.
+MCP delivers it inside the App document, not the outer showcase host.
+
+`property-registration` validates descriptor shape, CSS syntax/initial-value and
+ownership, and rejects conflicting schemas or registrations shared by unrelated
+owners. Identical registrations from the same owner are permitted. Runtime
+`--ds-*` / `--ux-*` variables stay with their runtime owner. A shared token's
+registration belongs beside its actual definition in a foundation value sheet;
+a namespaced owner token's registration belongs in its registered `tokens.css`.
+Neither `base.css` nor `fonts.css` becomes a registration escape hatch. Registration
+alone does not define a token or satisfy its sample/fixture coverage.
+
+Typed initial values must match their syntax and be computationally independent:
+`0px` is valid metadata; `var(--space-4)`, `1rem` and `currentColor` are not.
+The literal exemption applies only to registration descriptors. Keep design
+assignments outside them token-backed; a technical fallback is not a place to
+hide a component skin. Use literal static descriptors so guards can inspect them.
+See the [W3C registration contract](https://www.w3.org/TR/css-properties-values-api-1/#at-property-rule).
+
+Verify extracted CSS and actual interpolation, including after minification and
+inside the MCP App. A declaration can parse while a browser ignores an invalid
+registration. Keep required browser fallbacks and reduced-motion behavior; do not
+replace a valid CSS implementation with script merely to evade extraction or a
+guard limitation. These checks cover declarative registrations; arbitrary dynamic
+`CSS.registerProperty()` calls are not an ownership proof.
+
 ## Preserve custom-property arithmetic during extraction
 
 Custom properties can hold an unevaluated token stream that becomes arithmetic

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

@@ -101,7 +101,12 @@ failed/cancelled capture does not replace existing image slots or apply source.
 If a scenario/target is newly introduced, `current` is null with an explicit
 `currentAbsent` explanation; only the real candidate image exists.
 
-Review the returned images and diagnostics, fix the draft if necessary, then apply
+The edit reply is a summary. Read `ads_results({resultId,section:"captures"})` for
+the requested image resource URIs and `section:"diagnostics"` for relevant
+messages; follow `nextCursor` when needed. Read image resources explicitly.
+Standalone `ads_capture` continues returning its selected capture directly.
+
+Review those images and diagnostics, fix the draft if necessary, then apply
 with `dryRun:false`. Apply reruns all gates. An image is promoted only when the
 accepted source revision matches the captured candidate; other proposals remain
 stale. Images do not approve a patch or certify interaction/accessibility/parity.

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

@@ -20,21 +20,67 @@ A complete failed run can contain independent passing cases. Suite interruption,
 missing/skipped cases, stale inputs and an unexplained process exit cannot certify
 a pass. Keep the reported case outcome separate from whole-run acceptance.
 
+## Retrieve only the evidence needed
+
+`ads_verify`, `ads_apply_patch` and `ads_apply_transaction` reply with counts,
+bounded acceptance, at most three failure previews and `resultId`, within 4096
+UTF-8 JSON bytes. Full validation still decides acceptance. Do not repeat a suite
+merely to recover its output, or restate the complete report in conversation.
+
+Read a relevant saved section:
+
+```js
+ads_results({resultId: "<returned ID>", section: "outcomes", status: "not_passed"})
+// Continue only when needed, with the same section and status:
+ads_results({resultId: "<returned ID>", section: "outcomes", status: "not_passed", cursor: "<nextCursor>"})
+```
+
+Pages default to 10 rows, allow at most 20 and stay within 8192 JSON bytes. The
+byte cap can return fewer rows; `nextCursor` is the continuation. Other sections
+are `checks` (pipeline steps), `diagnostics`, `advisories`, `warnings`, `changes`,
+`captures`, `acceptance`, `investigation` (mutation boundary) and `selection`.
+A row marked `detailTruncated` is a preview. To read that exact record, pass its
+`recordIndex`, the same result/section, and `offset`/`chars` (maximum 2000 UTF-16
+characters); follow `nextOffset`. Do not combine ranges with a cursor/status filter.
+Read only the relevant log range. Reading pages or ranges never executes checks.
+
+`ads://project/results` lists the latest IDs. `ads://results/<resultId>` reads a
+summary; matching query parameters read pages/ranges. Only the latest verification
+and latest mutation snapshots are retained, independently, up to 8 MiB each.
+A superseded ID fails explicitly. An oversized report retains only its summary
+with a warning; disk failure retains details in server memory until shutdown.
+Neither changes actual acceptance or applied state. These are logical JSON byte
+budgets, not token estimates; compatibility text can duplicate structured JSON.
+Saved outcomes describe completion-time evidence, not current source freshness;
+compare their revisions with `ads_behaviors` before claiming a current pass.
+
+`ads_behaviors` pages owner summaries, then an exact unit's `checks`, `guarantees`,
+`subjects`, `demonstrations` or `profiles`. Use `nextCursor` and identical filters;
+changes invalidate a discovery cursor. Read a truncated contract via its
+`sourceFile` and bounded `ads_read_file`, rather than requesting everything.
+
 ## Get a compact investigation
 
-Discover exact owner/check IDs with `ads_behaviors`, then:
+Take an outcome's exact owner/check/run IDs from `ads_results`, then:
 
 ```json
-{ "unit": "components/Example", "check": "keyboard-navigation" }
+{ "unit": "components/Example", "check": "keyboard-navigation", "runId": "<outcome runId>" }
 ```
 
-Send this to `ads_investigate`. It reads the latest bundle without running code.
+Send this to `ads_investigate`. It reads a summary within 4096 JSON bytes, without
+running code. The run ID rejects evidence superseded by another execution.
+`section: "details"`, `"requests"`, `"browserErrors"` or `"artifacts"` reads separate pages
+(default 10/max 20 rows, at most 8192 JSON bytes); artifacts themselves require
+explicit resource reads. Truncated investigation records also support
+`recordIndex`/`offset`/`chars`; keep the exact `runId` to avoid mixing evidence.
+Without a check, the tool pages available investigations.
 `ads://project/investigations` lists available entries; the returned `resourceUri`
 reads the same bundle. It records:
 
 - Project versus isolated candidate, configured framework/profile and scenario.
 - Exact input revision and the preview revision actually observed by the helper.
-- Failing step/source, observed startup viewport and relevant failed requests.
+- `details.failingStep`, `details.source`, startup viewport and failure boundary.
+- Counts for separately paged relevant requests, browser errors and artifacts.
 - Available registered trace, screenshot or context artifact resource URIs.
 - Explicit `acceptance.established` and `acceptance.unverified` scope.
 
@@ -58,7 +104,8 @@ Candidate evidence never becomes passing live-source evidence. Compare the
 recorded input revision with current `ads_behaviors` evidence; a bundle describes
 its run, and does not claim current source merely because it remains available.
 For a build/architecture rejection before behavior runs, inspect the mutation
-result's `investigation` (also retained in `ads_status.mutations.lastResult`).
+saved `investigation` section via `ads_results`. Status retains the compact
+execution summary and result ID, rather than embedding complete reports.
 
 ## Preserve the design while repairing the failure
 

package/dist/skills/ads-migrate/references/guarded-editing.md

@@ -15,8 +15,10 @@ ads_apply_patch({"unit":"components/Example","patchFile":"<returned patchFile>",
 
 The dry run validates the full candidate, including affected registered behavior
 checks in an isolated project copy. Configured browser checks use that candidate's
-managed preview, not the live showcase. Inspect the returned `behavior` failures
-or the registered behavior-check results in `checks`, fix the draft and diff again.
+managed preview, not the live showcase. Read the summary, then page failing
+`outcomes`, `diagnostics` or pipeline `checks` through `ads_results` with its
+`resultId`. Inspect one exact outcome with `ads_investigate({unit,check,runId})`;
+fix the draft and diff again. See [evidence.md](evidence.md) for page/range limits.
 Keep behavior.json/specs with their owner and use registered checks; a scratchpad
 run against live source cannot verify unapplied changes. After validation, apply
 with `dryRun:false`; ADS revalidates before writing. Dry-run evidence is not saved
@@ -120,9 +122,10 @@ them through their actual public composition/customization path and list their r
 render references in covers. Do not count internal production renders as public API
 coverage. Behavioral APIs use exercises and registered guarantees instead.
 Scenario controls still use public UI. A native link/button can supply semantics
-as the single direct child of a public runtime slot when source tracing proves
-that owner clones the child with its props. An `asChild` flag alone is insufficient;
-standalone native controls and custom scenario styling remain rejected. See
+through a public runtime slot that demonstrably clones its child with owned
+props, or through matching runtime-owned selectors attached to the actual rendered
+DOM. Source ownership must be proven; an `asChild` flag or a lookalike marker is
+insufficient. Standalone controls and custom scenario styling remain rejected. See
 [scenarios.md](scenarios.md) for evidence and limits. Preserve the intended
 composition instead of substituting an unrelated styled control or adding a
 demo-only component prop. Review framing belongs in public layout patterns.

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

@@ -71,18 +71,20 @@ For on-demand current/candidate screenshots and visual dry-run review, read
 [captures.md](references/captures.md).
 For a rejected patch, failed check or loading error, read
 [evidence and diagnosis](references/evidence.md); inspect the failing boundary
-and `ads_investigate` bundle before changing APIs or verification policy.
+then page needed `ads_results` sections using the returned result ID. Inspect
+one `ads_investigate({unit,check,runId})` summary before changing APIs or policy;
+load request/error/artifact details only when relevant.
 
 
 For parent/child `covers`, conditional-control review, reference comparisons,
-public style-helper use, fragment-link navigation, or `scenario-render` /
-`showcase-class` findings, read [scenario contracts](references/scenarios.md). Its verification
+public style-helper use, native slot/selector composition, fragment navigation,
+or `scenario-render` / `showcase-control` / `showcase-class` findings, read [scenario contracts](references/scenarios.md). Its verification
 examples explain API visibility, reference baselines and state-transition checks.
 Traced parents can cover declared public children; verified public Linaria
 helpers do not grant custom scenario CSS.
 
 For atomic base/variant styling, helper/wrapper class composition, extracted
-custom-property arithmetic, or an
+custom-property arithmetic, typed `@property` registrations, or an
 `atomic-composition-review` / `atomic-composition-limit` advisory, read
 [atomic style composition](references/atomic-styles.md). The same guide is served
 as `ads://guides/atomic-styles`. It explains shorthand/logical conflicts and

package/dist/skills/ads-motion/references/atomic-styles.md

@@ -81,6 +81,54 @@ const treatment = css`
 This is a distinct state, not two competing base atoms. Whether changing padding
 on hover is desirable remains a product decision.
 
+## Register typed custom properties without atomizing their descriptors
+
+Use a literal `@property` in its component/pattern's Linaria template when the
+browser needs a typed, interpolated runtime variable:
+
+```tsx
+const treatment = css`
+  @property --ds-example-progress {
+    syntax: "<number>";
+    inherits: false;
+    initial-value: 0;
+  }
+  opacity: var(--ds-example-progress);
+`;
+```
+
+The identifier is illustrative; use a unique name owned by the real unit.
+Registrations are document-global, even when authored beside one component.
+Put them at template level or inside conditional at-rules, never element selectors.
+Use the same ADS tag resolver described below in both product and preview builds;
+it preserves each complete registration and its conditional context instead of
+splitting syntax/inherits/initial-value into invalid atomic rules. This works for
+atomic `css` and `styled`; the browser receives CSS without a registration runtime.
+MCP delivers it inside the App document, not the outer showcase host.
+
+`property-registration` validates descriptor shape, CSS syntax/initial-value and
+ownership, and rejects conflicting schemas or registrations shared by unrelated
+owners. Identical registrations from the same owner are permitted. Runtime
+`--ds-*` / `--ux-*` variables stay with their runtime owner. A shared token's
+registration belongs beside its actual definition in a foundation value sheet;
+a namespaced owner token's registration belongs in its registered `tokens.css`.
+Neither `base.css` nor `fonts.css` becomes a registration escape hatch. Registration
+alone does not define a token or satisfy its sample/fixture coverage.
+
+Typed initial values must match their syntax and be computationally independent:
+`0px` is valid metadata; `var(--space-4)`, `1rem` and `currentColor` are not.
+The literal exemption applies only to registration descriptors. Keep design
+assignments outside them token-backed; a technical fallback is not a place to
+hide a component skin. Use literal static descriptors so guards can inspect them.
+See the [W3C registration contract](https://www.w3.org/TR/css-properties-values-api-1/#at-property-rule).
+
+Verify extracted CSS and actual interpolation, including after minification and
+inside the MCP App. A declaration can parse while a browser ignores an invalid
+registration. Keep required browser fallbacks and reduced-motion behavior; do not
+replace a valid CSS implementation with script merely to evade extraction or a
+guard limitation. These checks cover declarative registrations; arbitrary dynamic
+`CSS.registerProperty()` calls are not an ownership proof.
+
 ## Preserve custom-property arithmetic during extraction
 
 Custom properties can hold an unevaluated token stream that becomes arithmetic