@agent-native/core 0.49.9 → 0.49.11

package/src/templates/starter-shell-sync.spec.ts

@@ -53,15 +53,16 @@ function readFile(dir: string, filename: string): string {
 /**
  * Shell files that must be byte-identical between scaffold and starter.
  * Each entry is [filename, reason]:
- *   entry.server.tsx — both now re-export the shared core handler; any
- *     future change to the pattern must land in both places at once.
+ *   entry.server.tsx — both import the app-local React Router ServerRouter
+ *     and pass it into the shared core handler; any future change to the
+ *     pattern must land in both places at once.
  *   entry.client.tsx — lightweight hydration entry that sets basename from
  *     APP_BASE_PATH; must stay in sync for workspace-mount correctness.
  */
 const SHELL_FILES: Array<[string, string]> = [
   [
     "entry.server.tsx",
-    "re-exports @agent-native/core/server/entry-server; must be identical",
+    "uses app-local ServerRouter with core entry-server; must be identical",
   ],
   [
     "entry.client.tsx",

package/src/templates/workspace-core/.agents/skills/extensions/SKILL.md

@@ -363,8 +363,9 @@ end up rendering nonsense like the literal text `true`.
 2. **Call an LLM directly via `extensionFetch`.** Requires a real key the
    user has set up. Reference it via `${keys.OPENAI_API_KEY}` /
    `${keys.ANTHROPIC_API_KEY}` and surface a clear error if the proxy
-   reports the key isn't configured. Tell the user where to add the key
-   (Settings → Secrets) before the extension can work.
+   reports the key isn't configured. Tell the user where to add the key:
+   Dispatch Vault for workspace apps, or app Settings → API Keys & Connections
+   for standalone apps.
 
 If you're not sure a key is configured, ask the user before generating an
 extension whose primary value is the AI step.

package/src/templates/workspace-core/.agents/skills/storing-data/SKILL.md

@@ -12,7 +12,9 @@ metadata:
 
 ## Rule
 
-All application data lives in **SQL** (SQLite locally, persistent database in production). The agent and UI share the same database. Do not store durable app data in the filesystem.
+All application data lives in **SQL** (SQLite locally, persistent database in production). The agent and UI share the same database. Do not store durable app data in the filesystem unless the app is explicitly running a Local File Mode artifact flow described below.
+
+**Local File Mode exception:** some artifact apps (Content, Plans, Slides, Dashboards, Designs, etc.) can intentionally use repo files as the source of truth for the artifact itself. This must be explicit via `agent-native.json`, `AGENT_NATIVE_MODE=local-files`, or an app-owned local-file action helper. In that mode, the UI and agent still go through app actions, but those actions read/write scoped files through `@agent-native/core/local-artifacts` instead of SQL rows. App state, auth, settings, credentials, collaboration metadata, and hosted database mode remain SQL. File-to-database or file-to-provider synchronization is an explicit sync step, not an implicit side effect of editing.
 
 When you add a data model, a list, or a read path, also follow the `performance` skill: project only the columns a list renders, index the columns hot queries filter/sort on, and avoid query waterfalls — so apps stay fast as data grows.