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

package/corpus/templates/plan/.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/plan/.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/plan/.agents/skills/plan-source-sync/SKILL.md

@@ -52,7 +52,7 @@ Annotation/Connector markup, optional `assets/`, and optional
   pass that read's `plan.updatedAt` as `expectedUpdatedAt`. Re-read the plan
   after the patch and verify that unrelated MDX files and visual surfaces were
   preserved.
-- In Agent Native Desktop, the Plan menu can link a user-chosen local folder for
+- In Agent-Native Desktop, the Plan menu can link a user-chosen local folder for
   the current plan, write the exported MDX files to it, import local edits back
   through `import-visual-plan-source`, and optionally auto-export whenever the
   hosted plan changes. This is a native desktop bridge; it does not require a

package/corpus/templates/plan/.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/plan/.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/plan/.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/plan/CHANGELOG.md

@@ -49,7 +49,7 @@ time from the command menu (Cmd+K → "What's new").
 
 ### Improved
 
-- Clicking the Agent Native logo now toggles the app sidebar.
+- Clicking the Agent-Native logo now toggles the app sidebar.
 
 ## 2026-07-30
 

package/corpus/templates/plan/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/slides/.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/slides/.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/slides/.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/slides/.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/slides/.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/slides/.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/slides/.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/slides/.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/slides/CHANGELOG.md

@@ -227,7 +227,7 @@ time from the command menu (Cmd+K → "What's new").
 - Design system setup keeps focus rings visible and uses a simpler dialog title.
 - Skip prompt is now available in the new deck prompt header
 - Slides now detect real text and box overflow across the deck and verify bounded repairs.
-- The Agent Native logo stays visible when the sidebar is collapsed and toggles the sidebar when clicked.
+- The Agent-Native logo stays visible when the sidebar is collapsed and toggles the sidebar when clicked.
 
 ### Fixed
 

package/corpus/templates/slides/actions/export-pptx.ts

@@ -1965,7 +1965,7 @@ export default defineAction({
       });
       pptx.layout = "AGENT_NATIVE";
     }
-    pptx.author = "Agent Native Slides";
+    pptx.author = "Agent-Native Slides";
     pptx.title = row.title;
     // The font scheme is the one half of the theme pptxgenjs does expose;
     // without it a themed deck re-imports as Calibri Light / Calibri.

package/corpus/templates/slides/changelog/2026-07-31-the-agent-native-logo-stays-visible-when-the-sidebar-is-coll.md

@@ -3,4 +3,4 @@ type: improved
 date: 2026-07-31
 ---
 
-The Agent Native logo stays visible when the sidebar is collapsed and toggles the sidebar when clicked.
+The Agent-Native logo stays visible when the sidebar is collapsed and toggles the sidebar when clicked.

package/corpus/templates/tasks/.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/tasks/.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/tasks/.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/tasks/.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/tasks/.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/tasks/.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/tasks/.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/tasks/.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/tasks/CHANGELOG.md

@@ -18,7 +18,7 @@ All notable user-facing changes to this app are documented here.
 
 ### Improved
 
-- Clicking the Agent Native logo now toggles the app sidebar.
+- Clicking the Agent-Native logo now toggles the app sidebar.
 
 ## 2026-07-29
 

package/corpus/templates/tasks/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/videos/.agents/skills/upgrade-agent-native/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: upgrade-agent-native
 description: >-
-  Bring an older Agent Native app or workspace current. Use when updating
+  Bring an older Agent-Native app or workspace current. Use when updating
   @agent-native/core, fixing a broken upgrade, or when tempted to patch or
   override core/dispatch packages to make an old branch run.
 scope: dev
@@ -9,11 +9,11 @@ metadata:
   internal: true
 ---
 
-# Upgrade Agent Native
+# Upgrade Agent-Native
 
 ## Rule
 
-When an older Agent Native app/branch needs to run on current packages, use
+When an older Agent-Native app/branch needs to run on current packages, use
 `agent-native upgrade`. Never "fix" upgrade breakage with
 `pnpm.overrides`, `patchedDependencies`, `resolutions`, local patches, or
 edits under `node_modules/@agent-native/*` — especially not against

package/dist/a2a/client.d.ts

@@ -59,7 +59,7 @@ export declare class A2AClient {
     });
     /**
      * Detect which A2A path the target agent uses.
-     * Agent-native apps use /_agent-native/a2a, external agents may use /a2a.
+     * Agent-Native apps use /_agent-native/a2a, external agents may use /a2a.
      */
     resolveEndpoint(): Promise<void>;
     /** Resolve the card-advertised endpoint without sending an RPC request. */

package/dist/a2a/client.js

@@ -161,7 +161,7 @@ export class A2AClient {
     }
     /**
      * Detect which A2A path the target agent uses.
-     * Agent-native apps use /_agent-native/a2a, external agents may use /a2a.
+     * Agent-Native apps use /_agent-native/a2a, external agents may use /a2a.
      */
     async resolveEndpoint() {
         await this.ensureEndpointCandidates();

package/dist/agent/engine/builder-engine.js

@@ -96,7 +96,7 @@ function mapReasoningEffort(budgetTokens) {
  * `/app/organizations/Nicholas%20kipchumba%20Space/billing` which Builder's
  * router treats as unknown and silently bounces to `/app/projects`. The
  * Builder CLI-auth callback doesn't expose the org slug/id today, so we route
- * to the org-agnostic subscription page. Agent Native attribution lets Builder
+ * to the org-agnostic subscription page. Agent-Native attribution lets Builder
  * skip generic onboarding for new users who land there from an upgrade CTA.
  */
 async function buildUpgradeUrl() {
@@ -167,7 +167,7 @@ class BuilderEngine {
             }, creditsLane);
             return;
         }
-        // The Builder gateway has an "auto" fallback mode, but Agent Native owns
+        // The Builder gateway has an "auto" fallback mode, but Agent-Native owns
         // model selection. Always send a concrete model so the gateway cannot
         // select an organization-level override or another fallback model.
         const requestedModel = opts.model.trim();

package/dist/agent/harness/hosted.js

@@ -95,6 +95,6 @@ export function hostedHarnessSystemPrompt(runtime) {
 You are running as a hosted ${HOSTED_HARNESS_AGENT_LABELS[runtime]} inside a production app.
 This is a tools-only mode. You have no repository, shell, filesystem, code-editing, or code-execution tools.
 Use the app's typed actions and SQL-backed resources for mail, calendar, analytics, and working state.
-For full coding work, tell the user to use the Agent Native Electron app.
+For full coding work, tell the user to use the Agent-Native Electron app.
 </hosted-tools-only-harness>`;
 }

package/dist/agent/harness/types.d.ts

@@ -7,7 +7,7 @@ export interface AgentHarnessCapabilities {
     resumable: boolean;
     /** Runtime can pause for human approval before continuing. */
     approvals: boolean;
-    /** Runtime can execute host-defined tools supplied by Agent Native. */
+    /** Runtime can execute host-defined tools supplied by Agent-Native. */
     hostTools: boolean;
     /** Runtime emits file mutation or artifact events. */
     fileEvents: boolean;
@@ -25,7 +25,7 @@ export interface AgentHarnessAdapter {
     createSession(opts: AgentHarnessCreateSessionOptions): Promise<AgentHarnessSession>;
 }
 export interface AgentHarnessCreateSessionOptions {
-    /** Agent Native session id. Adapters may map this to a native runtime id. */
+    /** Agent-Native session id. Adapters may map this to a native runtime id. */
     sessionId?: string;
     threadId?: string;
     runId?: string;
@@ -36,7 +36,7 @@ export interface AgentHarnessCreateSessionOptions {
     permissionMode?: AgentHarnessPermissionMode;
     sandbox?: unknown;
     /**
-     * Opaque value previously returned by detach()/stop(). Agent Native stores it
+     * Opaque value previously returned by detach()/stop(). Agent-Native stores it
      * but does not interpret it.
      */
     resumeState?: unknown;

package/dist/agent/production-agent.js

@@ -2207,7 +2207,7 @@ export async function executeAgentToolCall(options) {
     let streamCalls = 0;
     const engine = {
         name: "agent-native:single-tool",
-        label: "Agent Native tool runtime",
+        label: "Agent-Native tool runtime",
         defaultModel: "agent-native:single-tool",
         supportedModels: ["agent-native:single-tool"],
         capabilities: {
@@ -2253,7 +2253,7 @@ export async function executeAgentToolCall(options) {
         await runAgentLoop({
             engine,
             model: engine.defaultModel,
-            systemPrompt: "Execute the selected Agent Native tool call.",
+            systemPrompt: "Execute the selected Agent-Native tool call.",
             tools,
             availableTools: tools,
             messages: [

package/dist/cli/agent.js

@@ -230,7 +230,7 @@ export async function createHeadlessBuiltinActions() {
         "framework-search": {
             readOnly: true,
             tool: {
-                description: "Search version-matched Agent Native docs and readable Core, Toolkit, and first-party template source together. Use this first when a docs answer may require implementation evidence; supports substring, glob, SQL-like, and safe regex modes.",
+                description: "Search version-matched Agent-Native docs and readable Core, Toolkit, and first-party template source together. Use this first when a docs answer may require implementation evidence; supports substring, glob, SQL-like, and safe regex modes.",
                 parameters: {
                     type: "object",
                     properties: {
@@ -271,7 +271,7 @@ export async function createHeadlessBuiltinActions() {
         "docs-search": {
             readOnly: true,
             tool: {
-                description: "Search and read version-matched Agent Native framework documentation bundled in @agent-native/core, plus bundled AGENTS.md and codebase skills. Use --list to see pages, --query to search, and --slug to read a page.",
+                description: "Search and read version-matched Agent-Native framework documentation bundled in @agent-native/core, plus bundled AGENTS.md and codebase skills. Use --list to see pages, --query to search, and --slug to read a page.",
                 parameters: {
                     type: "object",
                     properties: {

package/dist/cli/app-skill.js

@@ -142,7 +142,7 @@ export function normalizeAppSkillManifest(raw) {
         id,
         displayName: stringValue(raw.displayName) ?? id,
         description: stringValue(raw.description) ??
-            `Agent-native app-backed skill for ${id}.`,
+            `Agent-Native app-backed skill for ${id}.`,
         ...(stringValue(raw.version) ? { version: stringValue(raw.version) } : {}),
         hosted: {
             url: hostedUrl,

package/dist/cli/clean.js

@@ -7,7 +7,7 @@
  * `PROTECTED_NAMES` and `isSafeTarget`), every target is a real directory
  * entry read from disk and re-verified immediately before the delete (see
  * `addTarget` and `verifyTargetUnchanged`), the root has to be a confirmed
- * Agent Native project root (see `checkProjectRoot`), and under `apps/` each
+ * Agent-Native project root (see `checkProjectRoot`), and under `apps/` each
  * app has to confirm the same thing for itself (see `splitAppDirs`). Those
  * checks are the whole safety contract, not a nicety.
  *
@@ -479,7 +479,7 @@ function dropNested(targets) {
 /**
  * Splits `apps/` into the apps this command may clean and the ones it may not.
  *
- * One Agent Native app under `apps/` authorizes cleaning *that app*, not its
+ * One Agent-Native app under `apps/` authorizes cleaning *that app*, not its
  * neighbours: `build/`, `dist/` and `.output/` are ordinary directory names,
  * and a workspace can hold a Rust project or a personal folder beside the app.
  * This is `checkProjectRoot`'s question asked one level down, and the reason
@@ -501,7 +501,7 @@ function splitAppDirs(root, failures) {
         if (marker.kind === "unreadable") {
             addFailure(failures, {
                 path: marker.path,
-                message: `could not be read (${marker.message}), so ${dir} is not treated as an Agent Native app`,
+                message: `could not be read (${marker.message}), so ${dir} is not treated as an Agent-Native app`,
             });
         }
         dirs.foreign.push(dir);
@@ -791,7 +791,7 @@ function formatCleanHuman(report) {
     return lines.join("\n");
 }
 /**
- * Is `dir` an Agent Native app root? Three answers, never two: the manifest
+ * Is `dir` an Agent-Native app root? Three answers, never two: the manifest
  * says yes, the manifest says no, or nobody could read the manifest.
  */
 function readAgentNativeMarker(dir) {
@@ -837,7 +837,7 @@ function readAgentNativeMarker(dir) {
  * outside a project is still a plausible personal folder, and every npm, pnpm
  * or yarn monorepo on the machine — `$HOME` included, if its `package.json`
  * has a `workspaces` key — carries a workspace marker. A workspace root is
- * accepted only when an app under `apps/` actually is Agent Native, which is
+ * accepted only when an app under `apps/` actually is Agent-Native, which is
  * also the only part of a workspace this command ever cleans.
  */
 function checkProjectRoot(root) {
@@ -845,7 +845,7 @@ function checkProjectRoot(root) {
     if (marker.kind === "unreadable") {
         return {
             ok: false,
-            reason: `${marker.path} could not be read (${marker.message}), so this cannot be confirmed as an Agent Native project.`,
+            reason: `${marker.path} could not be read (${marker.message}), so this cannot be confirmed as an Agent-Native project.`,
         };
     }
     if (marker.kind === "agent-native")
@@ -856,7 +856,7 @@ function checkProjectRoot(root) {
         return { ok: true };
     return {
         ok: false,
-        reason: "no package.json depending on @agent-native/core, no agent-native.json, and no apps/* with either, so this is not the root of an Agent Native project.",
+        reason: "no package.json depending on @agent-native/core, no agent-native.json, and no apps/* with either, so this is not the root of an Agent-Native project.",
     };
 }
 /** `agent-native clean` CLI entrypoint. Returns the process exit code —