@agent-native/core 0.175.4-nightly-20260826190205 → 0.175.4

package/corpus/templates/content/docs/solutions/2026-08-12-toggle-summary-focus-persistence-shape.md

@@ -85,7 +85,7 @@ Proposed replacement fingerprint:
 
 - shipping surfaces: Content's Toggle summary interaction and the shared editor
   toolkit's collaboration-reconciliation focus contract, both integrated through
-  the public Agent Native repository by merge;
+  the public Agent-Native repository by merge;
 - governing architecture: Content reports semantic editor-owned focus to the
   existing shared reconciliation hook; that hook remains the sole owner of
   stale-echo and external-snapshot arbitration;
@@ -561,8 +561,8 @@ architecture-fingerprint:
     - id: shared-editor-reconcile-semantic-focus
       repository: BuilderIO/agent-native
       product-surface: shared editor toolkit collaboration reconciliation
-      constituency: source-blind Agent Native app developers using editor-owned controls outside ProseMirror
-      durable-destination: public Agent Native editor toolkit
+      constituency: source-blind Agent-Native app developers using editor-owned controls outside ProseMirror
+      durable-destination: public Agent-Native editor toolkit
       integration-action: merge
   governing-architecture: Content reports semantic editor-owned focus to the existing shared reconciliation hook, which remains the sole owner of stale-echo and external-snapshot arbitration; no parallel state or save mechanism is added.
   acceptance-story:

package/corpus/templates/content/shared/nfm.ts

@@ -1364,6 +1364,25 @@ function endsWithUnescapedPipe(value: string): boolean {
   return backslashes % 2 === 0;
 }
 
+function hasMatchingBacktickRun(
+  value: string,
+  start: number,
+  expectedLength: number,
+): boolean {
+  for (let i = start; i < value.length; i++) {
+    if (value[i] === "\\") {
+      i++;
+      continue;
+    }
+    if (value[i] !== "`") continue;
+    let runLength = 1;
+    while (value[i + runLength] === "`") runLength++;
+    if (runLength === expectedLength) return true;
+    i += runLength - 1;
+  }
+  return false;
+}
+
 function splitGfmPipeRow(line: string): string[] | null {
   const value = line.trim();
   if (!value) return null;
@@ -1382,7 +1401,11 @@ function splitGfmPipeRow(line: string): string[] | null {
     if (char === "`") {
       let runLength = 1;
       while (value[i + runLength] === "`") runLength++;
-      if (codeFenceLength === 0) codeFenceLength = runLength;
+      if (
+        codeFenceLength === 0 &&
+        hasMatchingBacktickRun(value, i + runLength, runLength)
+      )
+        codeFenceLength = runLength;
       else if (codeFenceLength === runLength) codeFenceLength = 0;
       cell += "`".repeat(runLength);
       i += runLength - 1;
@@ -1440,6 +1463,7 @@ function parseGfmPipeTable(
   let ragged = false;
   while (end < lines.length) {
     if (lines[end].trim() === "" || leadingTabs(lines[end]) !== indent) break;
+    if (/^ {0,3}#{1,6}(?:\s|$)/.test(lines[end].slice(indent))) break;
     const row = splitGfmPipeRow(lines[end].slice(indent));
     if (!row) break;
     if (row.length !== header.length) ragged = true;

package/corpus/templates/crm/.agents/skills/adding-a-feature/SKILL.md

@@ -18,7 +18,7 @@ Scope check first: this is the checklist for a feature that adds app data or a n
 
 ## Why
 
-Agent-native apps are defined by parity: everything the UI can do, the agent can do, and vice versa. A feature that only has UI is invisible to the agent. A feature that only has scripts is invisible to the user. A feature without app-state sync means the agent is blind to what the user is doing.
+Agent-Native apps are defined by parity: everything the UI can do, the agent can do, and vice versa. A feature that only has UI is invisible to the agent. A feature that only has scripts is invisible to the user. A feature without app-state sync means the agent is blind to what the user is doing.
 
 ## The Checklist
 

package/corpus/templates/crm/.agents/skills/agent-native-docs/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: agent-native-docs
 description: >-
-  How to find version-matched Agent Native framework docs and source bundled in
+  How to find version-matched Agent-Native framework docs and source bundled in
   node_modules. Use before implementing or answering questions about
   @agent-native/core APIs, generated apps, workspaces, templates, or advanced
   features.
@@ -10,11 +10,11 @@ metadata:
   internal: true
 ---
 
-# Agent Native Docs Lookup
+# Agent-Native Docs Lookup
 
 ## Rule
 
-Before implementing or explaining non-trivial Agent Native behavior, read the
+Before implementing or explaining non-trivial Agent-Native behavior, read the
 version-matched docs installed with `@agent-native/core`. When examples,
 imports, or implementation details matter, inspect the packaged source corpus
 too.

package/corpus/templates/crm/.agents/skills/agent-native-toolkit/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: agent-native-toolkit
 description: >-
-  Inventory and ownership rules for shared Agent Native workspace UI. Use
+  Inventory and ownership rules for shared Agent-Native workspace UI. Use
   before building app chrome, settings, navigation, sharing, collaboration,
   setup, history, comments, chat rails, agent UX, or repeated workspace behavior.
 scope: dev

package/corpus/templates/crm/.agents/skills/customizing-agent-native/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: customizing-agent-native
 description: >-
-  How to configure, compose, or eject Agent Native features into app-owned
+  How to configure, compose, or eject Agent-Native features into app-owned
   code. Use when overriding shared components or integrations, customizing a
   template, adding UI to chat or headless apps, or inspecting package source.
 scope: dev
@@ -9,7 +9,7 @@ metadata:
   internal: true
 ---
 
-# Customizing Agent Native
+# Customizing Agent-Native
 
 ## Rule
 
@@ -205,7 +205,7 @@ UI ownership may change; product contracts should not:
 ## Don't
 
 - Don't edit or import from `node_modules/@agent-native/*/src` at runtime.
-- Don't add `pnpm.overrides`, patches, or resolutions for Agent Native packages.
+- Don't add `pnpm.overrides`, patches, or resolutions for Agent-Native packages.
 - Don't copy Core auth, DB, action, agent-loop, or transport internals.
 - Don't manually copy a first-party unit with a missing recipe; fix its manifest.
 - Don't eject a full package when a prop, slot, wrapper, or smaller unit works.

package/corpus/templates/crm/.agents/skills/frontend-design/SKILL.md

@@ -137,7 +137,7 @@ yours to apply.
 
 ## Agent-Native UI Rules
 
-- Agent-native apps use React and Vite. The default adapter uses Tailwind CSS,
+- Agent-Native apps use React and Vite. The default adapter uses Tailwind CSS,
   shadcn/ui, and `@tabler/icons-react`, but an app may register a different
   company design system in `app/design-system.ts`.
 - **Use the app's design-system seam for standard UI.** Inspect

package/corpus/templates/crm/.agents/skills/shadcn-ui/SKILL.md

@@ -21,7 +21,7 @@ This skill keeps shadcn/ui work project-aware. Components are source files in th
 ## First Steps
 
 1. Work from the app root that owns `components.json`.
-2. In an Agent Native app, inspect `app/design-system.ts` and
+2. In an Agent-Native app, inspect `app/design-system.ts` and
    `ToolkitProvider` before choosing a primitive. A registered company design
    system takes precedence over the default shadcn adapter.
 3. Run `pnpm dlx shadcn@latest info --json` when you need current project context: framework, Tailwind version, aliases, icon library, installed components, and resolved paths.
@@ -29,7 +29,7 @@ This skill keeps shadcn/ui work project-aware. Components are source files in th
 5. Check `app/components/ui/` or the resolved `ui` path before importing a component.
 6. For unfamiliar components, run `pnpm dlx shadcn@latest docs <component>` and read the returned docs or examples before coding.
 
-## Agent Native Adapter Rule
+## Agent-Native Adapter Rule
 
 Pages, routes, and domain components import controls through the app's local UI
 adapter layer. Never import `@agent-native/toolkit/ui/*` directly in app product
@@ -102,7 +102,7 @@ shadcn's built-in component animations are the right level of polish — keep th
 
 ## Icons
 
-- Agent-native apps use `@tabler/icons-react`. Do not add `lucide-react` because a registry example used it.
+- Agent-Native apps use `@tabler/icons-react`. Do not add `lucide-react` because a registry example used it.
 - If registry code imports a different icon package, replace those imports with Tabler equivalents before finishing.
 - Let shadcn components size icons through their CSS. Avoid manual icon sizing inside buttons, menus, alerts, and sidebars unless the local component API requires it.
 

package/corpus/templates/crm/.agents/skills/storing-data/SKILL.md

@@ -23,7 +23,7 @@ When you add a data model, a list, or a read path, also follow the `performance`
 
 ## How It Works
 
-Agent-native apps use Drizzle ORM over the configured SQL backend. Local development works out of the box with a SQLite file at `data/app.db`; production and shared preview deploys need a persistent `DATABASE_URL` because container/serverless filesystems can reset. The code should behave the same across backends, but the local SQLite file is not durable once deployed.
+Agent-Native apps use Drizzle ORM over the configured SQL backend. Local development works out of the box with a SQLite file at `data/app.db`; production and shared preview deploys need a persistent `DATABASE_URL` because container/serverless filesystems can reset. The code should behave the same across backends, but the local SQLite file is not durable once deployed.
 
 For app code, use Drizzle's schema/query DSL by default. Raw SQL is an escape hatch for additive migrations, health checks, or one-off maintenance, not the normal way to build features.
 

package/corpus/templates/crm/.agents/skills/workspace-conventions/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: workspace-conventions
 description: >-
-  Shared conventions for a multi-app Agent Native workspace: finding
+  Shared conventions for a multi-app Agent-Native workspace: finding
   version-matched framework docs and source, shared vs app-owned code, file and
   blob storage, env and secrets, agent scratch files, and Dispatch Resources.
   Use when working across workspace apps, storing files or credentials, or

package/corpus/templates/crm/DEVELOPING.md

@@ -1,6 +1,6 @@
 # CRM — Development Guide
 
-CRM is a React Router + Nitro Agent Native template. The UI and agent share the
+CRM is a React Router + Nitro Agent-Native template. The UI and agent share the
 same `actions/` contract; normal client reads and writes use action hooks, not
 custom CRUD routes.
 

package/corpus/templates/design/.agents/skills/adding-a-feature/SKILL.md

@@ -18,7 +18,7 @@ Scope check first: this is the checklist for a feature that adds app data or a n
 
 ## Why
 
-Agent-native apps are defined by parity: everything the UI can do, the agent can do, and vice versa. A feature that only has UI is invisible to the agent. A feature that only has scripts is invisible to the user. A feature without app-state sync means the agent is blind to what the user is doing.
+Agent-Native apps are defined by parity: everything the UI can do, the agent can do, and vice versa. A feature that only has UI is invisible to the agent. A feature that only has scripts is invisible to the user. A feature without app-state sync means the agent is blind to what the user is doing.
 
 ## The Checklist
 

package/corpus/templates/design/.agents/skills/agent-native-docs/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: agent-native-docs
 description: >-
-  How to find version-matched Agent Native framework docs and source bundled in
+  How to find version-matched Agent-Native framework docs and source bundled in
   node_modules. Use before implementing or answering questions about
   @agent-native/core APIs, generated apps, workspaces, templates, or advanced
   features.
@@ -10,11 +10,11 @@ metadata:
   internal: true
 ---
 
-# Agent Native Docs Lookup
+# Agent-Native Docs Lookup
 
 ## Rule
 
-Before implementing or explaining non-trivial Agent Native behavior, read the
+Before implementing or explaining non-trivial Agent-Native behavior, read the
 version-matched docs installed with `@agent-native/core`. When examples,
 imports, or implementation details matter, inspect the packaged source corpus
 too.

package/corpus/templates/design/.agents/skills/agent-native-toolkit/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: agent-native-toolkit
 description: >-
-  Inventory and ownership rules for shared Agent Native workspace UI. Use
+  Inventory and ownership rules for shared Agent-Native workspace UI. Use
   before building app chrome, settings, navigation, sharing, collaboration,
   setup, history, comments, chat rails, agent UX, or repeated workspace behavior.
 scope: dev

package/corpus/templates/design/.agents/skills/customizing-agent-native/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: customizing-agent-native
 description: >-
-  How to configure, compose, or eject Agent Native features into app-owned
+  How to configure, compose, or eject Agent-Native features into app-owned
   code. Use when overriding shared components or integrations, customizing a
   template, adding UI to chat or headless apps, or inspecting package source.
 scope: dev
@@ -9,7 +9,7 @@ metadata:
   internal: true
 ---
 
-# Customizing Agent Native
+# Customizing Agent-Native
 
 ## Rule
 
@@ -205,7 +205,7 @@ UI ownership may change; product contracts should not:
 ## Don't
 
 - Don't edit or import from `node_modules/@agent-native/*/src` at runtime.
-- Don't add `pnpm.overrides`, patches, or resolutions for Agent Native packages.
+- Don't add `pnpm.overrides`, patches, or resolutions for Agent-Native packages.
 - Don't copy Core auth, DB, action, agent-loop, or transport internals.
 - Don't manually copy a first-party unit with a missing recipe; fix its manifest.
 - Don't eject a full package when a prop, slot, wrapper, or smaller unit works.

package/corpus/templates/design/.agents/skills/frontend-design/SKILL.md

@@ -137,7 +137,7 @@ yours to apply.
 
 ## Agent-Native UI Rules
 
-- Agent-native apps use React and Vite. The default adapter uses Tailwind CSS,
+- Agent-Native apps use React and Vite. The default adapter uses Tailwind CSS,
   shadcn/ui, and `@tabler/icons-react`, but an app may register a different
   company design system in `app/design-system.ts`.
 - **Use the app's design-system seam for standard UI.** Inspect

package/corpus/templates/design/.agents/skills/shadcn-ui/SKILL.md

@@ -21,7 +21,7 @@ This skill keeps shadcn/ui work project-aware. Components are source files in th
 ## First Steps
 
 1. Work from the app root that owns `components.json`.
-2. In an Agent Native app, inspect `app/design-system.ts` and
+2. In an Agent-Native app, inspect `app/design-system.ts` and
    `ToolkitProvider` before choosing a primitive. A registered company design
    system takes precedence over the default shadcn adapter.
 3. Run `pnpm dlx shadcn@latest info --json` when you need current project context: framework, Tailwind version, aliases, icon library, installed components, and resolved paths.
@@ -29,7 +29,7 @@ This skill keeps shadcn/ui work project-aware. Components are source files in th
 5. Check `app/components/ui/` or the resolved `ui` path before importing a component.
 6. For unfamiliar components, run `pnpm dlx shadcn@latest docs <component>` and read the returned docs or examples before coding.
 
-## Agent Native Adapter Rule
+## Agent-Native Adapter Rule
 
 Pages, routes, and domain components import controls through the app's local UI
 adapter layer. Never import `@agent-native/toolkit/ui/*` directly in app product
@@ -102,7 +102,7 @@ shadcn's built-in component animations are the right level of polish — keep th
 
 ## Icons
 
-- Agent-native apps use `@tabler/icons-react`. Do not add `lucide-react` because a registry example used it.
+- Agent-Native apps use `@tabler/icons-react`. Do not add `lucide-react` because a registry example used it.
 - If registry code imports a different icon package, replace those imports with Tabler equivalents before finishing.
 - Let shadcn components size icons through their CSS. Avoid manual icon sizing inside buttons, menus, alerts, and sidebars unless the local component API requires it.
 

package/corpus/templates/design/.agents/skills/storing-data/SKILL.md

@@ -23,7 +23,7 @@ When you add a data model, a list, or a read path, also follow the `performance`
 
 ## How It Works
 
-Agent-native apps use Drizzle ORM over the configured SQL backend. Local development works out of the box with a SQLite file at `data/app.db`; production and shared preview deploys need a persistent `DATABASE_URL` because container/serverless filesystems can reset. The code should behave the same across backends, but the local SQLite file is not durable once deployed.
+Agent-Native apps use Drizzle ORM over the configured SQL backend. Local development works out of the box with a SQLite file at `data/app.db`; production and shared preview deploys need a persistent `DATABASE_URL` because container/serverless filesystems can reset. The code should behave the same across backends, but the local SQLite file is not durable once deployed.
 
 For app code, use Drizzle's schema/query DSL by default. Raw SQL is an escape hatch for additive migrations, health checks, or one-off maintenance, not the normal way to build features.
 

package/corpus/templates/design/.agents/skills/visual-edit/SKILL.md

@@ -42,7 +42,7 @@ launcher, where it is hidden from the model and redeemed once.
   credential-free `openUrl` only when a read-only fallback is acceptable.
 - In Claude Code Desktop's Code tab, prefer the rendered MCP App. Preview
   `openUrl` in the Browser pane only as the read-only fallback.
-- In VS Code, use the Agent Native Design webview/deep link described below.
+- In VS Code, use the Agent-Native Design webview/deep link described below.
 - Inline browser availability is host-dependent. CLI, remote, or restricted
   sessions may not expose one. If the inline surface is unavailable or disabled,
   return the normal **Open design** link instead of claiming it opened.
@@ -363,10 +363,10 @@ Fallback, only when `open-visual-edit` is unavailable:
   one-time local-editor capability. The credential-free `openUrl` / action link
   is the safe read-only fallback; never build a capability URL yourself.
 - Never return or open a hand-built `/design/:id?_session=...` URL.
-- If the user is working in VS Code, the Agent Native extension can open the
+- If the user is working in VS Code, the Agent-Native extension can open the
   same URL via
   `vscode://builder.agent-native/open?url=<encoded-design-url>`. Its
-  `Agent Native: Open Design Canvas` command also starts the local bridge and
+  `Agent-Native: Open Design Canvas` command also starts the local bridge and
   opens hosted Design in the VS Code side panel.
 - After `open-visual-edit`, confirm the Design editor is in overview mode
   with the requested URL-backed frames visible, and that they render the app

package/corpus/templates/design/.agents/skills/workspace-conventions/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: workspace-conventions
 description: >-
-  Shared conventions for a multi-app Agent Native workspace: finding
+  Shared conventions for a multi-app Agent-Native workspace: finding
   version-matched framework docs and source, shared vs app-owned code, file and
   blob storage, env and secrets, agent scratch files, and Dispatch Resources.
   Use when working across workspace apps, storing files or credentials, or

package/corpus/templates/design/CHANGELOG.md

@@ -122,7 +122,7 @@ from the command menu (Cmd+K → "What's new") or from Settings.
 
 ### Improved
 
-- Clicking the Agent Native logo now toggles the app sidebar.
+- Clicking the Agent-Native logo now toggles the app sidebar.
 
 ### Fixed
 
@@ -222,7 +222,7 @@ from the command menu (Cmd+K → "What's new") or from Settings.
 
 ### Improved
 
-- The collapsed sidebar keeps the Agent Native logo visible and removes the theme toggle from the sidebar.
+- The collapsed sidebar keeps the Agent-Native logo visible and removes the theme toggle from the sidebar.
 
 ## 2026-07-26
 
@@ -901,7 +901,7 @@ from the command menu (Cmd+K → "What's new") or from Settings.
 
 - Design editor panel borders are cleaner so the canvas edge stays rounded without doubled dividers.
 - Drawing prompts now reliably open and submit to the design agent.
-- Editor app menus now use an outline Agent Native mark with bordered, instant submenus.
+- Editor app menus now use an outline Agent-Native mark with bordered, instant submenus.
 - Layer selection now updates chat context without opening the agent sidebar.
 - Layer selections now preserve hidden and locked canvas state more faithfully.
 - Screen overview now handles zooming, drawing, opening, and deleting screens more reliably.

package/corpus/templates/design/changelog/2026-06-28-editor-app-menus-now-use-an-outline-agent-native-mark-with-b.md

@@ -3,4 +3,4 @@ type: fixed
 date: 2026-06-28
 ---
 
-Editor app menus now use an outline Agent Native mark with bordered, instant submenus.
+Editor app menus now use an outline Agent-Native mark with bordered, instant submenus.

package/corpus/templates/design/changelog/2026-07-27-collapsed-sidebar-keeps-the-agent-native-logo.md

@@ -3,4 +3,4 @@ type: improved
 date: 2026-07-27
 ---
 
-The collapsed sidebar keeps the Agent Native logo visible and removes the theme toggle from the sidebar.
+The collapsed sidebar keeps the Agent-Native logo visible and removes the theme toggle from the sidebar.

package/corpus/templates/design/changelog/2026-07-31-clicking-the-agent-native-logo-now-toggles-the-app-sidebar.md

@@ -3,4 +3,4 @@ type: improved
 date: 2026-07-31
 ---
 
-Clicking the Agent Native logo now toggles the app sidebar.
+Clicking the Agent-Native logo now toggles the app sidebar.

package/corpus/templates/design/public/manifest.json

@@ -1,7 +1,7 @@
 {
   "name": "Design",
   "short_name": "Design",
-  "description": "Agent-native design and prototyping tool",
+  "description": "Agent-Native design and prototyping tool",
   "start_url": ".",
   "background_color": "#111111",
   "theme_color": "#71717A",

package/corpus/templates/dispatch/.agents/skills/adding-a-feature/SKILL.md

@@ -18,7 +18,7 @@ Scope check first: this is the checklist for a feature that adds app data or a n
 
 ## Why
 
-Agent-native apps are defined by parity: everything the UI can do, the agent can do, and vice versa. A feature that only has UI is invisible to the agent. A feature that only has scripts is invisible to the user. A feature without app-state sync means the agent is blind to what the user is doing.
+Agent-Native apps are defined by parity: everything the UI can do, the agent can do, and vice versa. A feature that only has UI is invisible to the agent. A feature that only has scripts is invisible to the user. A feature without app-state sync means the agent is blind to what the user is doing.
 
 ## The Checklist
 

package/corpus/templates/dispatch/.agents/skills/agent-native-docs/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: agent-native-docs
 description: >-
-  How to find version-matched Agent Native framework docs and source bundled in
+  How to find version-matched Agent-Native framework docs and source bundled in
   node_modules. Use before implementing or answering questions about
   @agent-native/core APIs, generated apps, workspaces, templates, or advanced
   features.
@@ -10,11 +10,11 @@ metadata:
   internal: true
 ---
 
-# Agent Native Docs Lookup
+# Agent-Native Docs Lookup
 
 ## Rule
 
-Before implementing or explaining non-trivial Agent Native behavior, read the
+Before implementing or explaining non-trivial Agent-Native behavior, read the
 version-matched docs installed with `@agent-native/core`. When examples,
 imports, or implementation details matter, inspect the packaged source corpus
 too.

package/corpus/templates/dispatch/.agents/skills/agent-native-toolkit/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: agent-native-toolkit
 description: >-
-  Inventory and ownership rules for shared Agent Native workspace UI. Use
+  Inventory and ownership rules for shared Agent-Native workspace UI. Use
   before building app chrome, settings, navigation, sharing, collaboration,
   setup, history, comments, chat rails, agent UX, or repeated workspace behavior.
 scope: dev

package/corpus/templates/dispatch/.agents/skills/customizing-agent-native/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: customizing-agent-native
 description: >-
-  How to configure, compose, or eject Agent Native features into app-owned
+  How to configure, compose, or eject Agent-Native features into app-owned
   code. Use when overriding shared components or integrations, customizing a
   template, adding UI to chat or headless apps, or inspecting package source.
 scope: dev
@@ -9,7 +9,7 @@ metadata:
   internal: true
 ---
 
-# Customizing Agent Native
+# Customizing Agent-Native
 
 ## Rule
 
@@ -205,7 +205,7 @@ UI ownership may change; product contracts should not:
 ## Don't
 
 - Don't edit or import from `node_modules/@agent-native/*/src` at runtime.
-- Don't add `pnpm.overrides`, patches, or resolutions for Agent Native packages.
+- Don't add `pnpm.overrides`, patches, or resolutions for Agent-Native packages.
 - Don't copy Core auth, DB, action, agent-loop, or transport internals.
 - Don't manually copy a first-party unit with a missing recipe; fix its manifest.
 - Don't eject a full package when a prop, slot, wrapper, or smaller unit works.

package/corpus/templates/dispatch/.agents/skills/frontend-design/SKILL.md

@@ -137,7 +137,7 @@ yours to apply.
 
 ## Agent-Native UI Rules
 
-- Agent-native apps use React and Vite. The default adapter uses Tailwind CSS,
+- Agent-Native apps use React and Vite. The default adapter uses Tailwind CSS,
   shadcn/ui, and `@tabler/icons-react`, but an app may register a different
   company design system in `app/design-system.ts`.
 - **Use the app's design-system seam for standard UI.** Inspect

package/corpus/templates/dispatch/.agents/skills/shadcn-ui/SKILL.md

@@ -21,7 +21,7 @@ This skill keeps shadcn/ui work project-aware. Components are source files in th
 ## First Steps
 
 1. Work from the app root that owns `components.json`.
-2. In an Agent Native app, inspect `app/design-system.ts` and
+2. In an Agent-Native app, inspect `app/design-system.ts` and
    `ToolkitProvider` before choosing a primitive. A registered company design
    system takes precedence over the default shadcn adapter.
 3. Run `pnpm dlx shadcn@latest info --json` when you need current project context: framework, Tailwind version, aliases, icon library, installed components, and resolved paths.
@@ -29,7 +29,7 @@ This skill keeps shadcn/ui work project-aware. Components are source files in th
 5. Check `app/components/ui/` or the resolved `ui` path before importing a component.
 6. For unfamiliar components, run `pnpm dlx shadcn@latest docs <component>` and read the returned docs or examples before coding.
 
-## Agent Native Adapter Rule
+## Agent-Native Adapter Rule
 
 Pages, routes, and domain components import controls through the app's local UI
 adapter layer. Never import `@agent-native/toolkit/ui/*` directly in app product
@@ -102,7 +102,7 @@ shadcn's built-in component animations are the right level of polish — keep th
 
 ## Icons
 
-- Agent-native apps use `@tabler/icons-react`. Do not add `lucide-react` because a registry example used it.
+- Agent-Native apps use `@tabler/icons-react`. Do not add `lucide-react` because a registry example used it.
 - If registry code imports a different icon package, replace those imports with Tabler equivalents before finishing.
 - Let shadcn components size icons through their CSS. Avoid manual icon sizing inside buttons, menus, alerts, and sidebars unless the local component API requires it.
 

package/corpus/templates/dispatch/.agents/skills/storing-data/SKILL.md

@@ -23,7 +23,7 @@ When you add a data model, a list, or a read path, also follow the `performance`
 
 ## How It Works
 
-Agent-native apps use Drizzle ORM over the configured SQL backend. Local development works out of the box with a SQLite file at `data/app.db`; production and shared preview deploys need a persistent `DATABASE_URL` because container/serverless filesystems can reset. The code should behave the same across backends, but the local SQLite file is not durable once deployed.
+Agent-Native apps use Drizzle ORM over the configured SQL backend. Local development works out of the box with a SQLite file at `data/app.db`; production and shared preview deploys need a persistent `DATABASE_URL` because container/serverless filesystems can reset. The code should behave the same across backends, but the local SQLite file is not durable once deployed.
 
 For app code, use Drizzle's schema/query DSL by default. Raw SQL is an escape hatch for additive migrations, health checks, or one-off maintenance, not the normal way to build features.
 

package/corpus/templates/dispatch/.agents/skills/workspace-conventions/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: workspace-conventions
 description: >-
-  Shared conventions for a multi-app Agent Native workspace: finding
+  Shared conventions for a multi-app Agent-Native workspace: finding
   version-matched framework docs and source, shared vs app-owned code, file and
   blob storage, env and secrets, agent scratch files, and Dispatch Resources.
   Use when working across workspace apps, storing files or credentials, or

package/corpus/templates/dispatch/AGENTS.md

@@ -62,7 +62,7 @@ Read the relevant skill before deeper work:
   Destinations for concrete thread, change-history, and delivery investigations;
   Dispatch does not invent a separate issue tracker when those framework
   surfaces contain the operational evidence.
-- Thread Debug accepts the copied request/run ID from an Agent Native chat
+- Thread Debug accepts the copied request/run ID from an Agent-Native chat
   response as well as a chat thread ID; use the exact source that owns the run.
   Hosted production sources appear only when Dispatch has their
   <APP>_DATABASE_URL connection variables (or an equivalent

package/corpus/templates/dispatch/CHANGELOG.md

@@ -119,7 +119,7 @@ time from the command menu (Cmd+K → "What's new").
 ### Improved
 
 - Creating an app from a curated template now uses clearer, more direct language.
-- Thread Debug can open a run directly from the copied request ID in an Agent Native chat.
+- Thread Debug can open a run directly from the copied request ID in an Agent-Native chat.
 
 ## 2026-07-26
 

package/corpus/templates/dispatch/changelog/2026-07-27-thread-debug-accepts-request-run-ids.md

@@ -3,4 +3,4 @@ type: improved
 date: 2026-07-27
 ---
 
-Thread Debug can open a run directly from the copied request ID in an Agent Native chat.
+Thread Debug can open a run directly from the copied request ID in an Agent-Native chat.

package/corpus/templates/dispatch/shared/feature-flags.ts

@@ -13,7 +13,7 @@ export const DESKTOP_WORKSPACE_SSO_FLAG = defineFeatureFlag({
   key: "desktop.workspace-sso",
   displayName: "Desktop workspace sign-in",
   description:
-    "Let the signed Agent Native Desktop broker workspace identity across first-party apps.",
+    "Let the signed Agent-Native Desktop broker workspace identity across first-party apps.",
 });
 
 export const DISPATCH_FEATURE_FLAGS = defineFeatureFlags([

package/corpus/templates/factory/.agents/skills/adding-a-feature/SKILL.md

@@ -18,7 +18,7 @@ Scope check first: this is the checklist for a feature that adds app data or a n
 
 ## Why
 
-Agent-native apps are defined by parity: everything the UI can do, the agent can do, and vice versa. A feature that only has UI is invisible to the agent. A feature that only has scripts is invisible to the user. A feature without app-state sync means the agent is blind to what the user is doing.
+Agent-Native apps are defined by parity: everything the UI can do, the agent can do, and vice versa. A feature that only has UI is invisible to the agent. A feature that only has scripts is invisible to the user. A feature without app-state sync means the agent is blind to what the user is doing.
 
 ## The Checklist
 

package/corpus/templates/factory/.agents/skills/agent-native-docs/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: agent-native-docs
 description: >-
-  How to find version-matched Agent Native framework docs and source bundled in
+  How to find version-matched Agent-Native framework docs and source bundled in
   node_modules. Use before implementing or answering questions about
   @agent-native/core APIs, generated apps, workspaces, templates, or advanced
   features.
@@ -10,11 +10,11 @@ metadata:
   internal: true
 ---
 
-# Agent Native Docs Lookup
+# Agent-Native Docs Lookup
 
 ## Rule
 
-Before implementing or explaining non-trivial Agent Native behavior, read the
+Before implementing or explaining non-trivial Agent-Native behavior, read the
 version-matched docs installed with `@agent-native/core`. When examples,
 imports, or implementation details matter, inspect the packaged source corpus
 too.