@reqvire-org/ads 0.3.13 → 0.3.15

package/dist/scenario-slots.mjs

@@ -0,0 +1,124 @@
+import ts from "typescript";
+import { isDevelopmentFile } from "./config.mjs";
+import { publicApi } from "./public-api.mjs";
+import { createSourceValues, isFunction, reference, unwrap } from "./source-values.mjs";
+import { uiOperation } from "./ui-framework.mjs";
+
+/** A native scenario child may supply semantics to a public runtime slot. The
+ * proof follows actual child cloning, never a prop/component/helper spelling. */
+export function createScenarioSlots(program, options) {
+  const checker = program.getTypeChecker(), cache = new WeakMap();
+  const operation = node => uiOperation(node, checker);
+  const values = createSourceValues(program, options, { strict: true, preserveCall: node => ["createElement", "cloneElement", "Children.only"].includes(operation(node)) });
+  const { state, next, resolve, get, keys, props, returns, declaration } = values;
+  const publicNodes = new Set(publicApi(program, options).filter(item => item.renderable).map(item => resolve(reference(item.declaration.name ?? item.declaration), state())).filter(value => value.kind === "node").map(value => value.node));
+
+  function element(node, env = new Map(), via = []) {
+    if (ts.isJsxElement(node) || ts.isJsxSelfClosingElement(node)) {
+      const opening = ts.isJsxElement(node) ? node.openingElement : node;
+      const attributes = props(opening, env, via);
+      const children = ts.isJsxElement(node) ? node.children.filter(child => !ts.isJsxText(child) || child.text.trim()).filter(child => !ts.isJsxExpression(child) || child.expression) : [];
+      if (children.length) attributes.layers.push(new Map([["children", children.length === 1 ? reference(children[0], env, via) : { kind: "array", values: children.map(child => reference(child, env, via)) }]]));
+      return { tag: reference(opening.tagName, env, via), attributes, intrinsic: ts.isIdentifier(opening.tagName) && /^[a-z]/.test(opening.tagName.text) };
+    }
+    if (ts.isCallExpression(node) && operation(node.expression) === "createElement") {
+      const attributes = { kind: "object", layers: node.arguments[1] && node.arguments[1].kind !== ts.SyntaxKind.NullKeyword ? [reference(node.arguments[1], env, via)] : [] };
+      const children = node.arguments.slice(2).map(child => reference(child, env, via));
+      if (children.length) attributes.layers.push(new Map([["children", children.length === 1 ? children[0] : { kind: "array", values: children }]]));
+      return { tag: reference(node.arguments[0], env, via), attributes, intrinsic: !!node.arguments[0] && ts.isStringLiteralLike(node.arguments[0]) };
+    }
+    return null;
+  }
+
+  return function nativeSlot(site) {
+    if (cache.has(site)) return cache.get(site);
+    const reasons = new Set(); let cloned = false, exposed = false, uncertain = false, steps = 0;
+    const fail = reason => { uncertain = true; reasons.add(reason); };
+    function childValue(input, context) {
+      const value = resolve(input, next(context));
+      if (value.kind === "node" && ts.isJsxExpression(value.node)) return childValue(reference(value.node.expression, value.env, value.via), next(context));
+      if (value.kind === "node" && ts.isCallExpression(value.node) && operation(value.node.expression) === "Children.only") return childValue(reference(value.node.arguments[0], value.env, value.via), next(context));
+      return value;
+    }
+    function ownedProps(input, context, seen = new Set()) {
+      if (context.depth > 40) return false;
+      const value = resolve(input, next(context));
+      const opaque = value.kind === "unknown" || value.kind === "union" && value.values.length <= 32 && value.values.every(branch => resolve(branch, next(context)).kind === "unknown");
+      if (value.kind === "union" && !opaque) return value.values.length <= 32 && value.values.every(branch => ownedProps(branch, next(context), new Set(seen)));
+      if (keys(value, next(context)).some(key => key !== "children")) return true;
+      // Local prop mergers may use loops and a ref assignment, beyond the value
+      // evaluator. Retain runtime ownership through their actual input props;
+      // a known empty result, external call or arbitrary identifier cannot qualify.
+      if (!opaque || input.kind !== "node") return false;
+      const node = unwrap(input.node), { env, via } = input;
+      if (seen.has(node)) return false;
+      seen.add(node);
+      if (ts.isIdentifier(node)) {
+        if (env.has(checker.getSymbolAtLocation(node))) return ownedProps(env.get(checker.getSymbolAtLocation(node)), next(context), seen);
+        const binding = declaration(node);
+        return !!(binding && ts.isVariableDeclaration(binding) && binding.parent.flags & ts.NodeFlags.Const && binding.initializer && !isDevelopmentFile(binding.getSourceFile().fileName, options) && ownedProps(reference(binding.initializer, env, via), next(context), seen));
+      }
+      if (ts.isCallExpression(node)) {
+        const target = resolve(reference(node.expression, env, via), next(context));
+        return target.kind === "node" && isFunction(target.node) && !isDevelopmentFile(target.node.getSourceFile().fileName, options) && node.arguments.some(argument => ownedProps(reference(argument, env, via), next(context), new Set(seen)));
+      }
+      return false;
+    }
+    function render(input, context) {
+      if (++steps > 500 || context.depth > 48) { fail("Slot tracing reached its source work limit."); return; }
+      const value = childValue(input, context);
+      context = value.context ?? input.context ?? context;
+      if (value.kind === "slot-child") { exposed = true; return; }
+      if (["union", "array"].includes(value.kind)) {
+        if (value.values.length > 32) { fail("Slot tracing reached its alternative limit."); return; }
+        for (const child of value.values) render(child, next(context));
+        return;
+      }
+      if (value.kind === "unknown") { fail(value.reason || "The runtime slot's render path could not be traced."); return; }
+      if (value.kind !== "node") return;
+      const { node, env, via } = value;
+      if (ts.isJsxFragment(node)) { for (const child of node.children) render(reference(child, env, via), next(context)); return; }
+      if (ts.isArrayLiteralExpression(node)) { for (const child of node.elements) render(reference(ts.isSpreadElement(child) ? child.expression : child, env, via), next(context)); return; }
+      if (ts.isCallExpression(node) && operation(node.expression) === "cloneElement") {
+        const child = childValue(reference(node.arguments[0], env, via), next(context));
+        if (child.kind === "slot-child") {
+          if (!node.arguments[1] || !ownedProps(reference(node.arguments[1], env, via), state())) fail("A slot must clone its child with runtime-owned props.");
+          else cloned = true;
+        } else render(child, next(context));
+        return;
+      }
+      const view = element(node, env, via);
+      if (!view) return;
+      function component(input) {
+        const target = resolve(input, next(context));
+        if (target.kind === "union") {
+          if (target.values.length > 32) { fail("Slot tracing reached its alternative limit."); return; }
+          for (const branch of target.values) component(branch);
+        } else if (view.intrinsic || ["provider", "context"].includes(target.kind) || target.kind === "literal" && typeof target.value === "string") render(get(view.attributes, "children", next(context)), next(context));
+        else if (target.kind === "node" && isFunction(target.node) && !isDevelopmentFile(target.node.getSourceFile().fileName, options)) {
+          for (const output of returns(target, [view.attributes], next(context), "component")) render(output, next(context));
+        } else fail("The runtime slot's component target could not be traced.");
+      }
+      component(view.tag);
+    }
+
+    const native = ts.isJsxOpeningElement(site) ? site.parent : site;
+    let child = native;
+    while (child.parent && (ts.isJsxExpression(child.parent) || ts.isParenthesizedExpression(child.parent) || ts.isAsExpression(child.parent) || ts.isSatisfiesExpression(child.parent) || ts.isNonNullExpression(child.parent))) child = child.parent;
+    let parent = child.parent;
+    if (parent && ts.isJsxAttribute(parent) && parent.name.text === "children") parent = parent.parent.parent;
+    if (parent && ts.isPropertyAssignment(parent) && parent.name.getText().replace(/^["']|["']$/g, "") === "children" && ts.isObjectLiteralExpression(parent.parent) && ts.isCallExpression(parent.parent.parent) && parent.parent.parent.arguments[1] === parent.parent) parent = parent.parent.parent;
+    const view = parent && element(parent), context = state();
+    if (view) {
+      const target = resolve(view.tag, next(context));
+      const original = childValue(get(view.attributes, "children", next(context)), next(context));
+      if (target.kind === "node" && publicNodes.has(target.node) && original.kind === "node" && original.node === native) {
+        view.attributes.layers.push(new Map([["children", { kind: "slot-child" }]]));
+        for (const output of returns(target, [view.attributes], next(context), "component")) render(output, next(context));
+      }
+    }
+    const result = { ok: cloned && !exposed && !uncertain, reasons: [...reasons].slice(0, 2) };
+    cache.set(site, result);
+    return result;
+  };
+}

package/dist/showcase/sandbox.bundle.js

@@ -0,0 +1 @@
+function c(e,t){let n=new DOMParser().parseFromString(e,"text/html"),r=n.createElement("meta");if(r.httpEquiv="Content-Security-Policy",r.content=t,n.head.prepend(r),!n.querySelector("base[href]")){let i=n.querySelector("base")??n.createElement("base");i.setAttribute("href","about:srcdoc"),r.after(i)}return"<!doctype html>"+n.documentElement.outerHTML}var a=new URL(location.href).searchParams.get("parent"),o;function s(e=[]){return e.filter(t=>/^(?:https?:\/\/[a-z0-9.*:[\]-]+(?::\d+)?|data:|blob:|about:)$/i.test(t)).join(" ")}function d(e={}){let t=s(e.resourceDomains);return`default-src 'none';script-src 'unsafe-inline' ${t};style-src 'unsafe-inline' ${t};img-src data: ${t};font-src ${t||"'none'"};media-src ${t||"'none'"};worker-src ${t||"'none'"};connect-src ${s(e.connectDomains)||"'none'"};frame-src ${s(e.frameDomains)||"'none'"};base-uri about: ${s(e.baseUriDomains)};object-src 'none'`}window.addEventListener("message",e=>{if(e.source===parent&&e.origin===a){let t=e.data;if(t?.method==="ui/notifications/sandbox-resource-ready"){let{html:n,csp:r}=t.params??{};if(typeof n!="string")return;o?.remove(),o=window.document.createElement("iframe"),o.title="Design-system App",o.setAttribute("sandbox","allow-scripts"),window.document.body.append(o),o.srcdoc=c(n,d(r))}else t?.jsonrpc==="2.0"&&!t.method?.startsWith("ui/notifications/sandbox-")&&o?.contentWindow.postMessage(t,"*")}else e.source===o?.contentWindow&&e.data?.jsonrpc==="2.0"&&!e.data.method?.startsWith("ui/notifications/sandbox-")&&parent.postMessage(e.data,a)});parent.postMessage({jsonrpc:"2.0",method:"ui/notifications/sandbox-proxy-ready",params:{}},a);

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

@@ -55,8 +55,8 @@ For on-demand current/candidate screenshots and visual dry-run review, read
 
 
 For parent/child `covers`, conditional-control review, reference comparisons,
-public style-helper use in scenarios, or `scenario-render` / `showcase-class`
-findings, read [scenario contracts](references/scenarios.md). Its verification
+public style-helper use, fragment-link navigation, or `scenario-render` /
+`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.

package/dist/skills/ads-break-ui/references/guarded-editing.md

@@ -107,6 +107,17 @@ Keep contextual public parts public when they are intended consumer API. Demonst
 them through their actual public composition/customization path and list their real
 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; native link/button markup belongs in an
-owned public primitive/pattern or an owner-local test, including polymorphic/slot
-adaptation. Do not add demo-only component props or global styles for review glue.
+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
+[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.
+
+A complete runner report containing an ordinary failed assertion preserves each
+passing check as `passed`; the failed check remains `failed`, and overall
+verification still rejects the mutation. Fix the actual failing checks instead of
+assuming every affected owner failed. Suite errors, unexplained runner exits,
+missing results and interrupted runs cannot certify passing guarantees. Use the
+case's `reportedStatus`, message and report to distinguish these conditions.

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

@@ -1,6 +1,6 @@
 # Scenario rendering, token previews and public class helpers
 
-Use this reference for `scenario-render`, `scenario-coverage` or `showcase-class`
+Use this reference for `scenario-render`, `scenario-coverage`, `showcase-control` or `showcase-class`
 diagnostics. MCP serves the same guide as `ads://guides/scenarios`.
 
 All preview kinds open at `?scenario=<discovered-id>`. Use the returned showcase
@@ -23,6 +23,17 @@ on-demand element screenshots. It grants no render/behavior coverage and no extr
 styling permission. Use [captures.md](captures.md) for current/candidate review,
 target selection, resource reads and storage lifecycle.
 
+## Fragment links inside Apps
+
+Keep intended `href="#"` and named fragments in the project API and fixtures.
+ADS's inline-document loader supplies an `about:srcdoc` base when the App has no
+explicit base, preserving native scrolling, events and state. If a fragment
+replaces the App with a sandbox URL or browser error, inspect `location.href`,
+`document.baseURI` and the resolved anchor URL. Report a host loading defect;
+do not add scenario `preventDefault` handlers merely to hide it. Explicit App
+bases retain their declared behavior and CSP requirements; external hosts own
+their document-loading policy. Verify link activation as well as rendering.
+
 ## Owner-local token previews load their own definitions
 
 Keep the registered token sheet imported by its runtime owner for product use.
@@ -90,6 +101,40 @@ do not export the helper solely for a test. Public/private ownership is a produc
 decision, not a coverage workaround. Browser checks verify transitions but do not
 replace the current static `covers` requirement; `exercises` does not waive it.
 
+## Native semantics through a public runtime slot
+
+A native element can be the direct child of a public runtime component that
+actually clones that child with its own props:
+
+```tsx
+<Action asChild>
+  <a href={fixture.destination}>Documentation</a>
+</Action>
+```
+
+`Action` and the fixture are illustrative; use the project's intended public API.
+The runtime owner supplies presentation and interaction; the anchor supplies link
+semantics. Keep this composition when it is the product contract. Do not replace
+the anchor with an unrelated styled link, add a demo-only prop, disable the guard
+or write outside MCP merely to silence a diagnostic.
+
+ADS follows the selected runtime render path, the exact child and real imported
+React/Preact `cloneElement` operations, including local slot/prop-merging helpers.
+The prop need not be named `asChild`; the spelling alone grants no permission.
+JSX and recognized framework factories follow the same rule. The native element
+must be the single direct child: another native control nested inside it remains
+subject to the ordinary ownership rule. Passing children through a container,
+a scenario-local wrapper or an opaque component does not establish a slot.
+
+This grants no scenario styling permission. Inline styles and arbitrary class
+names remain rejected, including on the slotted child. Public style helpers retain
+their own provenance checks. Unknown branches that could render the native child
+directly, multiple children and untraceable replacement props remain blocked.
+If a valid slot contract cannot be traced, keep the intended API and report a
+small reproduction rather than inventing a product workaround. Static proof
+establishes ownership, not correct prop merging, focus, keyboard or navigation
+behavior; verify those in the built App and registered checks.
+
 ## Scenarios may consume verified public style helpers
 
 A deliberately public helper can expose its owner's Linaria treatment:

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

@@ -86,8 +86,8 @@ For on-demand current/candidate screenshots and visual dry-run review, read
 [captures.md](references/captures.md).
 
 For parent/child `covers`, conditional-control review, reference comparisons,
-public style-helper use in scenarios, or `scenario-render` / `showcase-class`
-findings, read [scenario contracts](references/scenarios.md). Its verification
+public style-helper use, fragment-link navigation, or `scenario-render` /
+`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.

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

@@ -197,7 +197,10 @@ or applies the right CSS property. Browser review still verifies the samples.
 
 Scenarios and fixture helpers are development-only wherever colocated. Runtime
 source and the public barrel cannot import or re-export them. Showcase/scenario
-code defines no CSS, custom classes or native controls; use public ADS APIs.
+code defines no CSS, custom classes or standalone native controls; use public ADS
+APIs. A single direct native child can supply semantics to a public runtime slot
+when source tracing proves that owner clones the exact child with its own props.
+An `asChild` flag alone is not evidence; scenario styling remains forbidden.
 Neither ADS implementations nor scenarios import application code. Live business
 data belongs to application adapters; ADS receives inputs or injected callbacks.
 Direct global `fetch`, XHR, WebSocket and EventSource use is rejected. Renderer

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

@@ -107,6 +107,17 @@ Keep contextual public parts public when they are intended consumer API. Demonst
 them through their actual public composition/customization path and list their real
 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; native link/button markup belongs in an
-owned public primitive/pattern or an owner-local test, including polymorphic/slot
-adaptation. Do not add demo-only component props or global styles for review glue.
+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
+[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.
+
+A complete runner report containing an ordinary failed assertion preserves each
+passing check as `passed`; the failed check remains `failed`, and overall
+verification still rejects the mutation. Fix the actual failing checks instead of
+assuming every affected owner failed. Suite errors, unexplained runner exits,
+missing results and interrupted runs cannot certify passing guarantees. Use the
+case's `reportedStatus`, message and report to distinguish these conditions.

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

@@ -1,6 +1,6 @@
 # Scenario rendering, token previews and public class helpers
 
-Use this reference for `scenario-render`, `scenario-coverage` or `showcase-class`
+Use this reference for `scenario-render`, `scenario-coverage`, `showcase-control` or `showcase-class`
 diagnostics. MCP serves the same guide as `ads://guides/scenarios`.
 
 All preview kinds open at `?scenario=<discovered-id>`. Use the returned showcase
@@ -23,6 +23,17 @@ on-demand element screenshots. It grants no render/behavior coverage and no extr
 styling permission. Use [captures.md](captures.md) for current/candidate review,
 target selection, resource reads and storage lifecycle.
 
+## Fragment links inside Apps
+
+Keep intended `href="#"` and named fragments in the project API and fixtures.
+ADS's inline-document loader supplies an `about:srcdoc` base when the App has no
+explicit base, preserving native scrolling, events and state. If a fragment
+replaces the App with a sandbox URL or browser error, inspect `location.href`,
+`document.baseURI` and the resolved anchor URL. Report a host loading defect;
+do not add scenario `preventDefault` handlers merely to hide it. Explicit App
+bases retain their declared behavior and CSP requirements; external hosts own
+their document-loading policy. Verify link activation as well as rendering.
+
 ## Owner-local token previews load their own definitions
 
 Keep the registered token sheet imported by its runtime owner for product use.
@@ -90,6 +101,40 @@ do not export the helper solely for a test. Public/private ownership is a produc
 decision, not a coverage workaround. Browser checks verify transitions but do not
 replace the current static `covers` requirement; `exercises` does not waive it.
 
+## Native semantics through a public runtime slot
+
+A native element can be the direct child of a public runtime component that
+actually clones that child with its own props:
+
+```tsx
+<Action asChild>
+  <a href={fixture.destination}>Documentation</a>
+</Action>
+```
+
+`Action` and the fixture are illustrative; use the project's intended public API.
+The runtime owner supplies presentation and interaction; the anchor supplies link
+semantics. Keep this composition when it is the product contract. Do not replace
+the anchor with an unrelated styled link, add a demo-only prop, disable the guard
+or write outside MCP merely to silence a diagnostic.
+
+ADS follows the selected runtime render path, the exact child and real imported
+React/Preact `cloneElement` operations, including local slot/prop-merging helpers.
+The prop need not be named `asChild`; the spelling alone grants no permission.
+JSX and recognized framework factories follow the same rule. The native element
+must be the single direct child: another native control nested inside it remains
+subject to the ordinary ownership rule. Passing children through a container,
+a scenario-local wrapper or an opaque component does not establish a slot.
+
+This grants no scenario styling permission. Inline styles and arbitrary class
+names remain rejected, including on the slotted child. Public style helpers retain
+their own provenance checks. Unknown branches that could render the native child
+directly, multiple children and untraceable replacement props remain blocked.
+If a valid slot contract cannot be traced, keep the intended API and report a
+small reproduction rather than inventing a product workaround. Static proof
+establishes ownership, not correct prop merging, focus, keyboard or navigation
+behavior; verify those in the built App and registered checks.
+
 ## Scenarios may consume verified public style helpers
 
 A deliberately public helper can expose its owner's Linaria treatment:

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

@@ -50,8 +50,8 @@ For on-demand current/candidate screenshots and visual dry-run review, read
 [captures.md](references/captures.md).
 
 For parent/child `covers`, conditional-control review, reference comparisons,
-public style-helper use in scenarios, or `scenario-render` / `showcase-class`
-findings, read [scenario contracts](references/scenarios.md). Its verification
+public style-helper use, fragment-link navigation, or `scenario-render` /
+`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.

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

@@ -107,6 +107,17 @@ Keep contextual public parts public when they are intended consumer API. Demonst
 them through their actual public composition/customization path and list their real
 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; native link/button markup belongs in an
-owned public primitive/pattern or an owner-local test, including polymorphic/slot
-adaptation. Do not add demo-only component props or global styles for review glue.
+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
+[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.
+
+A complete runner report containing an ordinary failed assertion preserves each
+passing check as `passed`; the failed check remains `failed`, and overall
+verification still rejects the mutation. Fix the actual failing checks instead of
+assuming every affected owner failed. Suite errors, unexplained runner exits,
+missing results and interrupted runs cannot certify passing guarantees. Use the
+case's `reportedStatus`, message and report to distinguish these conditions.

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

@@ -1,6 +1,6 @@
 # Scenario rendering, token previews and public class helpers
 
-Use this reference for `scenario-render`, `scenario-coverage` or `showcase-class`
+Use this reference for `scenario-render`, `scenario-coverage`, `showcase-control` or `showcase-class`
 diagnostics. MCP serves the same guide as `ads://guides/scenarios`.
 
 All preview kinds open at `?scenario=<discovered-id>`. Use the returned showcase
@@ -23,6 +23,17 @@ on-demand element screenshots. It grants no render/behavior coverage and no extr
 styling permission. Use [captures.md](captures.md) for current/candidate review,
 target selection, resource reads and storage lifecycle.
 
+## Fragment links inside Apps
+
+Keep intended `href="#"` and named fragments in the project API and fixtures.
+ADS's inline-document loader supplies an `about:srcdoc` base when the App has no
+explicit base, preserving native scrolling, events and state. If a fragment
+replaces the App with a sandbox URL or browser error, inspect `location.href`,
+`document.baseURI` and the resolved anchor URL. Report a host loading defect;
+do not add scenario `preventDefault` handlers merely to hide it. Explicit App
+bases retain their declared behavior and CSP requirements; external hosts own
+their document-loading policy. Verify link activation as well as rendering.
+
 ## Owner-local token previews load their own definitions
 
 Keep the registered token sheet imported by its runtime owner for product use.
@@ -90,6 +101,40 @@ do not export the helper solely for a test. Public/private ownership is a produc
 decision, not a coverage workaround. Browser checks verify transitions but do not
 replace the current static `covers` requirement; `exercises` does not waive it.
 
+## Native semantics through a public runtime slot
+
+A native element can be the direct child of a public runtime component that
+actually clones that child with its own props:
+
+```tsx
+<Action asChild>
+  <a href={fixture.destination}>Documentation</a>
+</Action>
+```
+
+`Action` and the fixture are illustrative; use the project's intended public API.
+The runtime owner supplies presentation and interaction; the anchor supplies link
+semantics. Keep this composition when it is the product contract. Do not replace
+the anchor with an unrelated styled link, add a demo-only prop, disable the guard
+or write outside MCP merely to silence a diagnostic.
+
+ADS follows the selected runtime render path, the exact child and real imported
+React/Preact `cloneElement` operations, including local slot/prop-merging helpers.
+The prop need not be named `asChild`; the spelling alone grants no permission.
+JSX and recognized framework factories follow the same rule. The native element
+must be the single direct child: another native control nested inside it remains
+subject to the ordinary ownership rule. Passing children through a container,
+a scenario-local wrapper or an opaque component does not establish a slot.
+
+This grants no scenario styling permission. Inline styles and arbitrary class
+names remain rejected, including on the slotted child. Public style helpers retain
+their own provenance checks. Unknown branches that could render the native child
+directly, multiple children and untraceable replacement props remain blocked.
+If a valid slot contract cannot be traced, keep the intended API and report a
+small reproduction rather than inventing a product workaround. Static proof
+establishes ownership, not correct prop merging, focus, keyboard or navigation
+behavior; verify those in the built App and registered checks.
+
 ## Scenarios may consume verified public style helpers
 
 A deliberately public helper can expose its owner's Linaria treatment:

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

@@ -52,8 +52,8 @@ For on-demand current/candidate screenshots and visual dry-run review, read
 
 
 For parent/child `covers`, conditional-control review, reference comparisons,
-public style-helper use in scenarios, or `scenario-render` / `showcase-class`
-findings, read [scenario contracts](references/scenarios.md). Its verification
+public style-helper use, fragment-link navigation, or `scenario-render` /
+`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.

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

@@ -107,6 +107,17 @@ Keep contextual public parts public when they are intended consumer API. Demonst
 them through their actual public composition/customization path and list their real
 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; native link/button markup belongs in an
-owned public primitive/pattern or an owner-local test, including polymorphic/slot
-adaptation. Do not add demo-only component props or global styles for review glue.
+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
+[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.
+
+A complete runner report containing an ordinary failed assertion preserves each
+passing check as `passed`; the failed check remains `failed`, and overall
+verification still rejects the mutation. Fix the actual failing checks instead of
+assuming every affected owner failed. Suite errors, unexplained runner exits,
+missing results and interrupted runs cannot certify passing guarantees. Use the
+case's `reportedStatus`, message and report to distinguish these conditions.

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

@@ -1,6 +1,6 @@
 # Scenario rendering, token previews and public class helpers
 
-Use this reference for `scenario-render`, `scenario-coverage` or `showcase-class`
+Use this reference for `scenario-render`, `scenario-coverage`, `showcase-control` or `showcase-class`
 diagnostics. MCP serves the same guide as `ads://guides/scenarios`.
 
 All preview kinds open at `?scenario=<discovered-id>`. Use the returned showcase
@@ -23,6 +23,17 @@ on-demand element screenshots. It grants no render/behavior coverage and no extr
 styling permission. Use [captures.md](captures.md) for current/candidate review,
 target selection, resource reads and storage lifecycle.
 
+## Fragment links inside Apps
+
+Keep intended `href="#"` and named fragments in the project API and fixtures.
+ADS's inline-document loader supplies an `about:srcdoc` base when the App has no
+explicit base, preserving native scrolling, events and state. If a fragment
+replaces the App with a sandbox URL or browser error, inspect `location.href`,
+`document.baseURI` and the resolved anchor URL. Report a host loading defect;
+do not add scenario `preventDefault` handlers merely to hide it. Explicit App
+bases retain their declared behavior and CSP requirements; external hosts own
+their document-loading policy. Verify link activation as well as rendering.
+
 ## Owner-local token previews load their own definitions
 
 Keep the registered token sheet imported by its runtime owner for product use.
@@ -90,6 +101,40 @@ do not export the helper solely for a test. Public/private ownership is a produc
 decision, not a coverage workaround. Browser checks verify transitions but do not
 replace the current static `covers` requirement; `exercises` does not waive it.
 
+## Native semantics through a public runtime slot
+
+A native element can be the direct child of a public runtime component that
+actually clones that child with its own props:
+
+```tsx
+<Action asChild>
+  <a href={fixture.destination}>Documentation</a>
+</Action>
+```
+
+`Action` and the fixture are illustrative; use the project's intended public API.
+The runtime owner supplies presentation and interaction; the anchor supplies link
+semantics. Keep this composition when it is the product contract. Do not replace
+the anchor with an unrelated styled link, add a demo-only prop, disable the guard
+or write outside MCP merely to silence a diagnostic.
+
+ADS follows the selected runtime render path, the exact child and real imported
+React/Preact `cloneElement` operations, including local slot/prop-merging helpers.
+The prop need not be named `asChild`; the spelling alone grants no permission.
+JSX and recognized framework factories follow the same rule. The native element
+must be the single direct child: another native control nested inside it remains
+subject to the ordinary ownership rule. Passing children through a container,
+a scenario-local wrapper or an opaque component does not establish a slot.
+
+This grants no scenario styling permission. Inline styles and arbitrary class
+names remain rejected, including on the slotted child. Public style helpers retain
+their own provenance checks. Unknown branches that could render the native child
+directly, multiple children and untraceable replacement props remain blocked.
+If a valid slot contract cannot be traced, keep the intended API and report a
+small reproduction rather than inventing a product workaround. Static proof
+establishes ownership, not correct prop merging, focus, keyboard or navigation
+behavior; verify those in the built App and registered checks.
+
 ## Scenarios may consume verified public style helpers
 
 A deliberately public helper can expose its owner's Linaria treatment:

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

@@ -72,8 +72,8 @@ For on-demand current/candidate screenshots and visual dry-run review, read
 
 
 For parent/child `covers`, conditional-control review, reference comparisons,
-public style-helper use in scenarios, or `scenario-render` / `showcase-class`
-findings, read [scenario contracts](references/scenarios.md). Its verification
+public style-helper use, fragment-link navigation, or `scenario-render` /
+`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.

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

@@ -107,6 +107,17 @@ Keep contextual public parts public when they are intended consumer API. Demonst
 them through their actual public composition/customization path and list their real
 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; native link/button markup belongs in an
-owned public primitive/pattern or an owner-local test, including polymorphic/slot
-adaptation. Do not add demo-only component props or global styles for review glue.
+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
+[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.
+
+A complete runner report containing an ordinary failed assertion preserves each
+passing check as `passed`; the failed check remains `failed`, and overall
+verification still rejects the mutation. Fix the actual failing checks instead of
+assuming every affected owner failed. Suite errors, unexplained runner exits,
+missing results and interrupted runs cannot certify passing guarantees. Use the
+case's `reportedStatus`, message and report to distinguish these conditions.