@agent-native/core 0.152.1 → 0.153.0

package/corpus/templates/factory/app/routes/settings.tsx

@@ -22,7 +22,7 @@ export function meta() {
 
 export default function SettingsRoute() {
   const t = useT();
-  const agentSettingsTabs = useAgentSettingsTabs();
+  const agentSettingsTabs = useAgentSettingsTabs({ usageAppId: "factory" });
   useSetPageTitle(t("settings.title"));
 
   const generalSearchEntries = useMemo<SettingsSearchEntry[]>(

package/corpus/templates/factory/server/connectors/credentials.ts

@@ -1,6 +1,7 @@
 import { resolveCredential } from "@agent-native/core/credentials";
 import { orgMembers, resolveOrgIdForEmail } from "@agent-native/core/org";
 import { readAppSecret } from "@agent-native/core/secrets";
+import { resolveWorkspaceConnectionCredentialForApp } from "@agent-native/core/workspace-connections";
 import { eq, sql } from "drizzle-orm";
 
 import { getDb } from "../db/index.js";
@@ -13,6 +14,14 @@ export interface ResolveConnectorSecretOptions {
   orgId?: string | null;
 }
 
+const WORKSPACE_PROVIDER_BY_KEY: Record<string, string> = {
+  GITHUB_TOKEN: "github",
+  SENTRY_AUTH_TOKEN: "sentry",
+  SENTRY_SERVER_TOKEN: "sentry",
+  SLACK_BOT_TOKEN: "slack",
+  SLACK_BOT_TOKEN_2: "slack",
+};
+
 function isMissingTableError(err: unknown): boolean {
   const message = err instanceof Error ? err.message : String(err);
   return (
@@ -79,6 +88,22 @@ export async function resolveConnectorSecret(
   const primaryOrgId =
     options.orgId?.trim() || (await resolveOrgIdForEmail(userEmail));
 
+  const workspaceProvider = WORKSPACE_PROVIDER_BY_KEY[key];
+  if (workspaceProvider) {
+    try {
+      const connected = await resolveWorkspaceConnectionCredentialForApp({
+        appId: "factory",
+        provider: workspaceProvider,
+        key,
+        userEmail,
+        orgId: primaryOrgId,
+      });
+      if (connected.available && connected.value) return connected.value.trim();
+    } catch (error) {
+      if (!isMissingTableError(error)) throw error;
+    }
+  }
+
   const userSecret = await readVaultSecret(key, "user", userEmail);
   if (userSecret) return userSecret;
 

package/corpus/templates/factory/server/lib/provider-api.ts

@@ -0,0 +1,34 @@
+import {
+  createProviderApiRuntime,
+  type ProviderApiDocsOptions,
+  type ProviderApiRequestArgs,
+} from "@agent-native/core/provider-api";
+import { getCredentialContext } from "@agent-native/core/server";
+
+export const FACTORY_APP_ID = "factory";
+
+const runtime = createProviderApiRuntime({
+  appId: FACTORY_APP_ID,
+  localCredentialSource: "factory_local",
+  getCredentialContext: () => {
+    const ctx = getCredentialContext();
+    if (!ctx) {
+      throw new Error(
+        "Factory provider API requests require an authenticated request context.",
+      );
+    }
+    return ctx;
+  },
+});
+
+export function listProviderApiCatalog(provider?: string) {
+  return runtime.listCatalog(provider);
+}
+
+export function fetchProviderApiDocs(options: ProviderApiDocsOptions) {
+  return runtime.fetchDocs(options);
+}
+
+export function executeProviderApiRequest(args: ProviderApiRequestArgs) {
+  return runtime.executeRequest(args);
+}

package/corpus/templates/factory/server/plugins/agent-chat.ts

@@ -18,6 +18,9 @@ const INITIAL_TOOL_NAMES = [
   "get-triage-item",
   "poll-slack-channel",
   "get-slack-feedback-context",
+  "provider-api-catalog",
+  "provider-api-docs",
+  "provider-api-request",
   "poll-github-sources",
   "poll-sentry-errors",
   "evaluate-triage-item",
@@ -33,15 +36,16 @@ const INITIAL_TOOL_NAMES = [
 
 const options = {
   appId: "factory",
+  backgroundMcpTools: "all",
   actions: loadActionsFromStaticRegistry(actionsRegistry),
   leanPrompt: true,
   initialToolNames: INITIAL_TOOL_NAMES,
   resolveOrgId: async (event) => (await getOrgContext(event)).orgId,
   systemPrompt: `You are the Factory agent.
 
-Factory is a visual factory builder. It observes Slack feedback, GitHub issues,
-Sentry errors, and pull-request evidence, renders the current factory graph, and
-executes only the explicit automation prompts that are stored in the organization.
+Factory is a visual factory builder. It observes source evidence, renders the
+current factory graph, and executes only the explicit automation prompts that
+are stored in the organization.
 Use the Factory actions as the source of truth. When a user asks to
 create or change a factory, first inspect the current graph, then propose a complete
 versioned graph through save-factory-graph with source=ai and a concise changeSummary.
@@ -49,6 +53,14 @@ Never hide a graph change in prose: the visual map and the saved graph must agre
 The graph is currently a reviewable blueprint, not the runtime router: automation
 markdown resources are the runtime prompts, while enabled triage rules are evaluated
 in parallel against the same evidence. Do not claim that an edge changes execution.
+Workspace integrations and credentials are shared agent capabilities, configured in
+Dispatch or the shared app settings. Factory never asks for, copies, or stores
+provider keys per factory. Start with provider-api-catalog to discover the
+workspace's connected provider APIs, use provider-api-docs when an endpoint is
+unclear, and use provider-api-request with the shared credentials. The normalized
+poll-slack-channel, poll-github-sources, and poll-sentry-errors actions are legacy
+observer adapters for the default triage queue, not a list of Factory integrations
+or a limit on what agents can use.
 For rule or guard changes, use the triage rule actions and preserve
 normalizeTriagePolicyGuards; do not encode policy in graph JSON.
 Use add-factory-comment for durable comments attached to the selected node or edge.

package/corpus/templates/factory/server/plugins/factory-scheduler-job.ts

@@ -157,22 +157,36 @@ function subscribeToAutomationFailures(): void {
 type AutomationSeed = {
   name: string;
   schedule: string;
+  legacySchedules?: string[];
   timezone?: string;
+  model: string;
+  maxIterations: number;
+  maxRunInputTokens: number;
   body: string;
 };
 
+const FACTORY_DEFAULT_MODEL =
+  process.env.FACTORY_AUTOMATION_MODEL?.trim() || "gpt-5.6-luna";
+const FACTORY_DEFAULT_MAX_ITERATIONS = 32;
+const FACTORY_DEFAULT_MAX_RUN_INPUT_TOKENS = 1_000_000;
+
 const AUTOMATION_SEEDS: AutomationSeed[] = [
   {
     name: "factory-slack-feedback",
-    schedule: "* * * * *",
+    schedule: "*/5 * * * *",
+    legacySchedules: ["* * * * *"],
+    model: FACTORY_DEFAULT_MODEL,
+    maxIterations: FACTORY_DEFAULT_MAX_ITERATIONS,
+    maxRunInputTokens: FACTORY_DEFAULT_MAX_RUN_INPUT_TOKENS,
     body: `
 # Factory Slack feedback triage
 
 Read the Factory configuration. When Slack polling is enabled and a channel is
-configured, call poll-slack-channel first. Then list at most 2 received Slack
-items by passing limit 2, process them sequentially, and call
-get-slack-feedback-context for each item before classifying it. Never use the
-action's default page size.
+configured, call poll-slack-channel first. Then list at most 2 new or changed
+Slack items by passing needsReview true, source slack, and limit 2. Process
+them sequentially, and call get-slack-feedback-context for each item before
+classifying it. Never list the full queue or use the action's default page
+size.
 
 Start work only for a clear bug: a concrete broken behavior, reproducible
 failure, error, regression, stuck run, incorrect result, or a report with a
@@ -200,13 +214,17 @@ PR, merge, or fix unless an action returned that state.
     name: "factory-sentry-errors",
     schedule: "0 9 * * *",
     timezone: "America/Los_Angeles",
+    model: FACTORY_DEFAULT_MODEL,
+    maxIterations: 24,
+    maxRunInputTokens: FACTORY_DEFAULT_MAX_RUN_INPUT_TOKENS,
     body: `
 # Factory Sentry error triage
 
 Read the Factory configuration. When Sentry polling is enabled and a Sentry
-organization is configured, call poll-sentry-errors. List at most 3 received
-Sentry items by passing limit 3 and inspect the title, culprit, level, event
-count, and errorReport metadata. Never use the action's default page size.
+organization is configured, call poll-sentry-errors. List at most 3 new or
+changed errors by passing needsReview true, source sentry, and limit 3. Inspect
+the title, culprit, level, event count, and errorReport metadata. Never list the
+full queue or use the action's default page size.
 
 Only classify a concrete unresolved error as a clear bug when the Sentry
 evidence is sufficient to investigate. Do not dispatch on noise, expected
@@ -221,14 +239,19 @@ run callback or PR observation confirms it.
   },
   {
     name: "factory-github-issues",
-    schedule: "* * * * *",
+    schedule: "0 * * * *",
+    legacySchedules: ["* * * * *", "*/5 * * * *"],
+    model: FACTORY_DEFAULT_MODEL,
+    maxIterations: FACTORY_DEFAULT_MAX_ITERATIONS,
+    maxRunInputTokens: FACTORY_DEFAULT_MAX_RUN_INPUT_TOKENS,
     body: `
 # Factory GitHub issue triage
 
 Read the Factory configuration. When GitHub source polling is enabled and a
 repository is configured, call poll-github-sources with includeIssues true and
-includePullRequests false. List at most 3 received github_issue items by
-passing limit 3. Never use the action's default page size.
+includePullRequests false. List at most 3 new or changed issues by passing
+needsReview true, source github_issue, and limit 3. Never list the full queue or
+use the action's default page size.
 
 Treat an issue as a clear bug only when it has a concrete error report,
 reproduction, incorrect behavior, regression, or specific failing path. Do
@@ -243,14 +266,19 @@ confirmation.
   },
   {
     name: "factory-pr-governance",
-    schedule: "*/5 * * * *",
+    schedule: "*/10 * * * *",
+    legacySchedules: ["*/5 * * * *"],
+    model: FACTORY_DEFAULT_MODEL,
+    maxIterations: 40,
+    maxRunInputTokens: 2_000_000,
     body: `
 # Factory pull-request governance
 
 Read the Factory configuration. When GitHub polling is enabled and a repository
 is configured, call poll-github-sources with includeIssues false and
-includePullRequests true. List at most 3 github pull-request items by passing
-limit 3. Never use the action's default page size.
+includePullRequests true. List at most 3 new or changed pull requests by
+passing needsReview true, source github, and limit 3. Never list the full queue
+or use the action's default page size.
 
 For each open agent-native PR, inspect the item and classify whether it is a
 clear bug fix or has product or UX implications. Call
@@ -272,14 +300,19 @@ governance action confirms it.
   },
   {
     name: "factory-pr-babysit",
-    schedule: "*/2 * * * *",
+    schedule: "*/5 * * * *",
+    legacySchedules: ["*/2 * * * *"],
+    model: FACTORY_DEFAULT_MODEL,
+    maxIterations: FACTORY_DEFAULT_MAX_ITERATIONS,
+    maxRunInputTokens: FACTORY_DEFAULT_MAX_RUN_INPUT_TOKENS,
     body: `
 # Factory builder-io-bot PR babysitting
 
 Read the Factory configuration. When GitHub polling is enabled and a repository
 is configured, call poll-github-sources with includeIssues false and
-includePullRequests true. List at most 3 open github pull-request items by
-passing limit 3. Never use the action's default page size.
+includePullRequests true. List at most 3 new or changed pull requests by
+passing needsReview true, source github, and limit 3. Never list the full queue
+or use the action's default page size.
 
 For each item, call babysit-agent-native-pull-request. That action fetches fresh
 GitHub and ai-services evidence and is the only place allowed to decide whether
@@ -319,14 +352,14 @@ function defaultGithubPollingEnabled(): 0 | 1 {
 function automationPromptGuard(name: string): string | undefined {
   switch (name) {
     case "factory-slack-feedback":
-      return "Runtime safety bound: pass limit 2 to list-triage-items, process at most two Slack items sequentially, and never use the default page size.";
+      return "Runtime safety bound: call list-triage-items with needsReview true, source slack, and limit 2; process at most two Slack items sequentially, and never use the default page size.";
     case "factory-sentry-errors":
-      return "Runtime safety bound: pass limit 3 to list-triage-items and process at most three Sentry items.";
+      return "Runtime safety bound: call list-triage-items with needsReview true, source sentry, and limit 3; process at most three Sentry items.";
     case "factory-github-issues":
-      return "Runtime safety bound: pass limit 3 to list-triage-items and process at most three GitHub issue items.";
+      return "Runtime safety bound: call list-triage-items with needsReview true, source github_issue, and limit 3; process at most three GitHub issue items.";
     case "factory-pr-governance":
     case "factory-pr-babysit":
-      return "Runtime safety bound: pass limit 3 to list-triage-items and process at most three pull-request items.";
+      return "Runtime safety bound: call list-triage-items with needsReview true, source github, and limit 3; process at most three pull-request items.";
     default:
       return undefined;
   }
@@ -348,6 +381,18 @@ function setFrontmatterField(
   return `${content.slice(0, end)}\n${key}: ${value}${content.slice(end)}`;
 }
 
+function frontmatterField(content: string, key: string): string | undefined {
+  if (!content.startsWith("---\n")) return undefined;
+  const end = content.indexOf("\n---", 4);
+  if (end === -1) return undefined;
+  const match = content
+    .slice(4, end)
+    .match(new RegExp(`^${key}:\\s*(.*)$`, "m"));
+  const value = match?.[1]?.trim();
+  if (!value) return undefined;
+  return value.replace(/^(\"|')|((\"|')$)/g, "");
+}
+
 function automationContent(
   ownerEmail: string,
   orgId: string,
@@ -362,6 +407,9 @@ appId: factory
 orgId: ${orgId}
 createdBy: ${ownerEmail}
 runAs: creator
+model: ${seed.model}
+maxIterations: ${seed.maxIterations}
+maxRunInputTokens: ${seed.maxRunInputTokens}
 ---
 ${seed.body.trim()}
 `;
@@ -400,9 +448,9 @@ async function ensureOrganizationAutomations(
         return;
       }
 
-      // Earlier Factory versions created these rows without the metadata the
-      // list and action guards use. Patch only identity metadata and keep the
-      // user's prompt, model, schedule, and enabled state intact.
+      // Earlier Factory versions created these rows without identity and run
+      // budget metadata. Preserve explicit prompt/model/budget edits, while
+      // repairing only missing defaults and the old built-in poll cadence.
       let repaired = existing.content;
       repaired = setFrontmatterField(repaired, "triggerType", "schedule");
       repaired = setFrontmatterField(repaired, "domain", "factory");
@@ -410,6 +458,30 @@ async function ensureOrganizationAutomations(
       repaired = setFrontmatterField(repaired, "orgId", orgId);
       repaired = setFrontmatterField(repaired, "createdBy", ownerEmail);
       repaired = setFrontmatterField(repaired, "runAs", "creator");
+      if (!frontmatterField(repaired, "model")) {
+        repaired = setFrontmatterField(repaired, "model", seed.model);
+      }
+      if (!frontmatterField(repaired, "maxIterations")) {
+        repaired = setFrontmatterField(
+          repaired,
+          "maxIterations",
+          String(seed.maxIterations),
+        );
+      }
+      if (!frontmatterField(repaired, "maxRunInputTokens")) {
+        repaired = setFrontmatterField(
+          repaired,
+          "maxRunInputTokens",
+          String(seed.maxRunInputTokens),
+        );
+      }
+      if (
+        (seed.legacySchedules ?? []).includes(
+          frontmatterField(repaired, "schedule") ?? "",
+        )
+      ) {
+        repaired = setFrontmatterField(repaired, "schedule", seed.schedule);
+      }
       const promptGuard = automationPromptGuard(seed.name);
       if (promptGuard && !repaired.includes(promptGuard)) {
         repaired = `${repaired.trimEnd()}\n\n${promptGuard}\n`;

package/corpus/templates/factory/server/triage/review-state.ts

@@ -0,0 +1,33 @@
+export interface TriageReviewSnapshot {
+  title?: string | null;
+  summary?: string | null;
+  sourceUrl?: string | null;
+  coverage?: string | null;
+  lastSeenAt?: string | null;
+  headSha?: string | null;
+}
+
+/** Reopen an item only when the provider evidence changed since the last poll. */
+export function hasTriageSourceChanged(
+  existing: TriageReviewSnapshot | undefined,
+  next: TriageReviewSnapshot,
+): boolean {
+  if (!existing) return true;
+  return (
+    (next.title !== undefined && existing.title !== next.title) ||
+    (next.summary !== undefined && existing.summary !== next.summary) ||
+    (next.sourceUrl !== undefined && existing.sourceUrl !== next.sourceUrl) ||
+    (next.coverage !== undefined && existing.coverage !== next.coverage) ||
+    (next.lastSeenAt !== undefined &&
+      existing.lastSeenAt !== next.lastSeenAt) ||
+    (next.headSha !== undefined && existing.headSha !== next.headSha)
+  );
+}
+
+export function statusAfterTriageSourceUpdate(
+  existingStatus: string | undefined,
+  sourceChanged: boolean,
+  reviewStatus: string,
+): string {
+  return sourceChanged ? reviewStatus : (existingStatus ?? reviewStatus);
+}

package/corpus/templates/factory/server/triage/slack-poller.ts

@@ -67,6 +67,7 @@ function toEnvelope(
     summary: compactText(message.text),
     channelId,
     threadTs,
+    metadata: { messageTs: message.ts },
     coverage:
       message.reply_count && message.reply_count > 0 ? "partial" : "complete",
   };

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

@@ -0,0 +1,208 @@
+---
+name: adding-a-feature
+description: >-
+  The four-area checklist every new feature must complete. Use when adding any
+  feature, integration, or capability to ensure the agent and UI stay in parity.
+scope: dev
+metadata:
+  internal: true
+---
+
+# Adding a Feature — The Four-Area Checklist
+
+## Rule
+
+Every new feature MUST update all four areas. Skipping any one breaks the agent-native contract — the agent and UI must always be equal partners.
+
+Scope check first: this is the checklist for a feature that adds app data or a new capability. A restyle, a copy change, or a screen with no new data model and no new agent-visible operation only needs the areas it actually touches — do not manufacture actions, state keys, or a skill for it.
+
+## 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.
+
+## The Checklist
+
+When you add a new feature, work through these four areas in order:
+
+### 1. UI Component
+
+Build the user-facing interface — a page, component, dialog, or route. Use `useActionQuery` and `useActionMutation` from `@agent-native/core/client` to call actions for data fetching and mutations. Do not create a custom REST endpoint just so React can call action-backed data; the action endpoint already exists.
+
+**Auto-refresh on agent writes is non-negotiable** — when the agent mutates data, the UI must reflect the change without a manual refresh. There are two paths, and you must pick the right one:
+
+- **`useActionQuery` / `useActionMutation`** — covered automatically. The framework's `useDbSync` invalidates `["action"]` on every change event, so every `useActionQuery` hook refetches on agent activity. No extra wiring required. **Prefer this path.**
+- **Raw `useQuery` with custom keys** — needs explicit wiring. Fold `useChangeVersions([<source>, "action"])` from `@agent-native/core/client` into the `queryKey` and set `placeholderData: (prev) => prev`. The `action` source is the reliable signal (the agent runner emits it after every successful tool call); the resource-specific source (`"dashboards"`, `"analyses"`, `"settings"`, etc.) is bonus when emitted. Without this wiring, agent writes will be invisible until manual refresh — that breaks the framework's #1 promise.
+
+  ```tsx
+  import { useChangeVersions } from "@agent-native/core/client/hooks";
+  import { useQuery } from "@tanstack/react-query";
+
+  const v = useChangeVersions(["dashboards", "action"]);
+  useQuery({
+    queryKey: ["dashboard", id, v],
+    queryFn: () => fetchDashboard(id),
+    placeholderData: (prev) => prev, // no flicker on refetch
+  });
+  ```
+
+  See the `real-time-sync` skill for the full pattern and source catalog.
+
+### 2. Action
+
+Create an action in `actions/` using `defineAction`. This serves double duty: the agent calls it as a tool, and the UI calls it through `useActionQuery` / `useActionMutation` while the framework owns the HTTP transport. Set `http: { method: "GET" }` for read actions, leave default for writes, or set `http: false` for agent-only actions like `navigate` and `view-screen`.
+
+Before adding a new route or endpoint, inspect the existing actions. Reuse an
+action if it already covers the business operation, extend it if the shared
+contract is incomplete, or create a new `defineAction` if the agent and UI both
+need the capability. Do not add pass-through `/api/*` routes that re-export
+actions. If client code needs a new framework/app route, expose a named helper
+or hook first and use that helper from components and docs.
+
+For provider-backed analysis/query/reporting integrations, do not turn every
+provider endpoint or filter into a rigid action. Prefer the shared
+`provider-api-catalog` / `provider-api-docs` / `provider-api-request` pattern
+from `@agent-native/core/provider-api`, then add narrow convenience actions only
+for workflows that truly deserve a first-class shortcut. Treat this as a
+capability requirement, not a nice-to-have: convenience actions must not become
+the ceiling of what the agent can ask the provider to do. Pair broad provider
+access with staging or sandboxed code execution when responses may be too large
+for chat context. If provider credentials live on resource/share rows, add the
+scoped resolver first so broad access preserves the same ownership boundary as
+the app UI.
+
+If the feature needs credentials, design the credential path in the same change.
+Never hardcode API keys, tokens, webhook URLs, signing secrets, private
+Builder/internal data, or customer data in the action, UI, seed data, fixtures,
+docs, prompts, or generated extension/app content. Register required secrets,
+use OAuth helpers, or read scoped values from the vault/credential store.
+
+If the feature involves attachments, images, recordings, screenshots, exports,
+or other file-like payloads, design the upload path in the same change:
+provider upload first, then URL/id/blob handle in SQL. Do not add base64/binary
+columns or stuff files into `application_state`.
+
+If the feature adds a server-side dependency carrying a native binary or heavy
+runtime — headless browser, ffmpeg, image/video processing, ML runtime — read
+the `performance` skill §9 before adding it. A deployed app has one `/*` page
+function that every visitor's cache miss wakes, and it ships whatever the server
+bundle depends on. Run that work from a background function or a job so the page
+function never carries the weight.
+
+**If the action produces or lists a navigable resource**, add a `link` builder that returns `{ url: buildDeepLink({ app, view, params }), label }`. External coding agents and MCP hosts (Claude / ChatGPT / Claude Code / Cowork / Codex, over MCP/A2A) then surface an "Open in … →" deep link that drops the user back into the running UI focused on the record — for free. If a compatible MCP host should render an inline review/edit surface, also add `mcpApp` with `embedApp()` so the action embeds the real React app route instead of a one-off HTML UI. The `link` builder and `mcpApp` metadata must be pure and synchronous (no I/O). Any external-agent read/ingest action must be `http: { method: "GET" }` + `readOnly: true` + `publicAgent: { expose: true, readOnly: true, requiresAuth: true }`. See the `external-agents` skill.
+
+### 3. Skills / Instructions
+
+Update `AGENTS.md` and/or create a skill in `.agents/skills/` if the feature introduces patterns the agent needs to know. At minimum, add the new actions to the action table in the template's `AGENTS.md`.
+
+Reusable actions are part of the app contract, not just implementation detail. When an action is useful outside one screen, update agent instructions in the same change so app agents know when to call it, which arguments matter, and what output to preserve. If the capability is workflow-heavy, cross-app, provider-backed, or has a non-obvious sequence of actions, add or update a skill instead of burying the behavior in one long `AGENTS.md` paragraph.
+
+Instruction examples may name secret keys like `SLACK_WEBHOOK`, but must use
+placeholders such as `${keys.SLACK_WEBHOOK}` or `<SLACK_WEBHOOK>`. Do not paste
+real keys, internal data, or customer data into instructions as examples.
+
+If the feature adds or changes visible UI copy, prompts, toasts, labels, empty
+states, or formatting, update the English source copy. Read the optional
+`internationalization` skill and update additional catalogs only when
+`translations.locales` in `agent-native.config.ts` includes them.
+
+For app-backed skills, declare skill visibility in the app-skill manifest:
+
+- `internal` — only the app's own agents should use it.
+- `exported` — marketplace installs receive it, but the app does not need it loaded internally.
+- `both` — shared between the app's internal agents and exported marketplace bundles.
+
+### 4. Application State Sync
+
+Expose navigation and selection state so the agent knows what the user is looking at. Write to the `navigation` app-state key on route changes. Update the `view-screen` action to fetch relevant data for the new feature. Add a `navigate` command if the agent needs to open the new view.
+
+## Examples
+
+### Adding "compose email" to a mail app
+
+| Area            | What to build                                                                            |
+| --------------- | ---------------------------------------------------------------------------------------- |
+| UI              | Compose panel with tabs, to/cc/bcc fields, body editor. Use `useActionQuery`/`useActionMutation` for data. |
+| Action          | `manage-draft` action (create/update/delete drafts), `send-email` action                 |
+| Skills/AGENTS   | Document compose state shape, draft lifecycle, action args in AGENTS.md                  |
+| App-state sync  | `compose-{id}` keys for each draft tab, `navigation` includes compose state              |
+
+### Adding "create form" to a forms app
+
+| Area            | What to build                                                                            |
+| --------------- | ---------------------------------------------------------------------------------------- |
+| UI              | Form builder page with drag-and-drop fields, preview, settings. Use `useActionQuery` for lists. |
+| Action          | `create-form` action, `update-form` action, `list-forms` action (GET)                    |
+| Skills/AGENTS   | Document form schema shape, field types, validation rules in AGENTS.md                   |
+| App-state sync  | `navigation` includes `{ view: "form-builder", formId: "..." }`, `view-screen` fetches form data |
+
+### Adding "chart type" to an analytics app
+
+| Area            | What to build                                                                            |
+| --------------- | ---------------------------------------------------------------------------------------- |
+| UI              | New chart component, chart type selector in dashboard                                    |
+| Action          | `create-chart` or `update-dashboard` action that sets chart type and config              |
+| Skills/AGENTS   | Document supported chart types, config options, data requirements                        |
+| App-state sync  | `navigation` includes selected chart/dashboard, `view-screen` returns chart config       |
+
+## Adding a new route
+
+Templates are single-page apps with client-side routing. The app shell (AgentSidebar + top-level nav) MUST persist across navigation — it is mounted once, either in `root.tsx` around `<Outlet />` or via a pathless `_app.tsx` layout route that all authed routes nest under.
+
+**Never wrap each new route in its own `<AppLayout>` / `<Layout>`.** That causes React to unmount the entire app shell on every navigation, reloading the agent sidebar and destroying in-progress work.
+
+- If the template has `<AppLayout>` in `root.tsx` — just render page content in your new route file, nothing else.
+- If the template has `app/routes/_app.tsx` (pathless layout) — name your new route `_app.<segment>.tsx` to inherit the shell, or bare `<segment>.tsx` for public routes that should NOT have the shell.
+- If a page needs per-route data (e.g. highlighting the active item in the sidebar), read it in the layout from `useParams()` / `useLocation()`. Don't pass it as a prop through every route file.
+
+See the "Client-Side Routing" section in the root `CLAUDE.md` for full details.
+
+## Anti-Patterns
+
+- **Per-route `<AppLayout>` wrappers** — Every route file wraps its content in `<AppLayout>` or `<Layout>`. React sees a different component at the outlet on each nav and unmounts the whole shell, causing the agent sidebar to reload on every click. Mount the shell once above `<Outlet />` (root.tsx or `_app.tsx` pathless layout).
+- **UI without actions** — The user can create forms but the agent cannot. The agent says "I don't have access to that" when it should be able to do it.
+- **Actions without AGENTS.md** — The actions exist but the agent doesn't know about them because they're not documented. The agent reinvents solutions instead of using the actions.
+- **Duplicate API routes** — Creating `/api/` routes for operations that actions already handle, including pass-through routes that just call or repackage an action. Use `useActionQuery`/`useActionMutation` instead.
+- **Raw client route calls** — Teaching or adding `fetch("/_agent-native/...")`,
+  `fetch(agentNativePath(...))`, or template `/api/*` calls in components for
+  normal app work. Add a named client helper/hook and call that instead.
+- **Features without app-state** — The agent cannot see that the user is looking at a specific form, email, or chart. It asks "which one?" instead of acting on the current selection.
+- **Actions without UI** — The agent can do something the user cannot. This is less common but still breaks parity.
+
+## Verification
+
+After completing all four areas, verify:
+
+1. Can the user perform the operation from the UI?
+2. Can the agent perform the same operation via actions?
+3. Does `pnpm action view-screen` show the relevant state when the user is using the feature?
+4. Can the agent navigate to the feature view via the `navigate` action?
+5. Is the feature documented in AGENTS.md with action names and args?
+6. Are credentials and sensitive data supplied only through approved runtime
+   channels, with no hardcoded real keys, tokens, webhook URLs, Builder/internal
+   data, or customer data?
+
+## One more area — sharing
+
+If the feature stores **user-authored resources** (documents, dashboards, forms, decks, etc.), make them ownable so they get private-by-default semantics and a share dialog for free. See the `sharing` skill.
+
+TL;DR: spread `ownableColumns()` into the resource table, pair it with `createSharesTable(...)`, call `registerShareableResource(...)`, wrap list/read queries with `accessFilter`, guard writes with `assertAccess`, and drop `<ShareButton>` in the resource header. The `share-resource`, `unshare-resource`, `list-resource-shares`, and `set-resource-visibility` actions are auto-mounted framework-wide.
+
+## One more area — who inside the app may do it
+
+If the feature is one **only some teammates should be able to perform inside this app** (an admin-only import, a settings reset), that is a per-app role — not a new organization, and not a share grant. See the `authentication` skill.
+
+TL;DR: declare the vocabulary once with `defineAppRoles({ appId, roles, defaultRole })`, guard the action with `authorize: appAccess.requireAny("...")`, and render the picker with `<TeamPage appRoles={descriptor} />`. `defaultRole` is display only — it never satisfies a guard — and `authorize` gates the operation while `accessFilter` / `assertAccess` still scope the rows.
+
+## Related Skills
+
+- **authentication** — Per-app member roles (`defineAppRoles`) when only some teammates may use a feature
+- **sharing** — How to make a new resource ownable (private by default, share with users/orgs/public)
+- **context-awareness** — How to expose UI state to the agent (area 4 in detail)
+- **actions** — How to create actions with `defineAction` and the `http` option (area 2 in detail)
+- **external-agents** — Add a `link` builder so external agents (MCP/A2A) get an "Open in … →" deep link
+- **create-skill** — How to create skills for new patterns (area 3 in detail)
+- **storing-data** — Where to store the feature's data
+- **real-time-sync** — How the UI stays in sync when the agent writes data
+- **performance** — Query/load cost, and (§9) cold-start artifact size when a
+  feature adds a server-side dependency
+- **internationalization** — How to update localized UI copy and catalogs