@agent-native/core 0.22.5 → 0.22.8

package/docs/content/template-starter.md

@@ -10,14 +10,14 @@ Starter is the minimum viable agent-native app. You get the six-rules architectu
 <!-- screenshot:
   app: starter
   view: /
-  shows: Blank-slate app with sidebar (Starter brand, Home / New App / Observability), centered "Blank app" card with Start building prompt button + 3 quick-action tiles (New app / Documentation / Theme), agent chat panel on the right
+  shows: Blank-slate app with sidebar (Blank app brand, Home / Observability), centered "Blank app" card with Start building prompt button + quick-action tiles for Documentation and Theme, agent chat panel on the right
   account: screenshot-account (no domain data needed — starter ships with no seed schema)
   capture: 1400x800 viewport, cropped 90px from bottom (final 1400x710)
 -->
 
 ![Starter scaffold with the agent sidebar and a clean blank-slate UI](/screenshots/starter.png)
 
-Pick Starter when you're not sure which domain template fits, or when you want to learn the framework by doing — there's almost nothing to delete.
+Pick Starter when you're not sure which domain template fits, or when you want to learn the framework by doing. It is scaffolding for your app, not a launcher for more apps, so starter-derived apps should be renamed and reshaped into the actual product.
 
 ## What's in it {#whats-in-it}
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@agent-native/core",
-  "version": "0.22.5",
+  "version": "0.22.8",
   "type": "module",
   "description": "Framework for agent-native application development — where AI agents and UI share state via files",
   "license": "MIT",

package/src/templates/workspace-core/AGENTS.md

@@ -55,11 +55,14 @@ available to every workspace app. Only create or request per-app vault grants
 when Dispatch's vault access setting is switched to manual mode.
 
 Workspace apps are discovered from `apps/<app-name>/package.json`. There is no
-separate workspace app registry to edit for Dispatch to list the app. Use
-relative workspace links like `/<app-name>` and never hardcode `localhost`,
-`127.0.0.1`, `8080`, `8100`, or any dev port in app cards, instructions,
-redirects, or navigation; the active workspace gateway/browser origin owns the
-port. React Router apps must preserve `APP_BASE_PATH` / `VITE_APP_BASE_PATH` in
+separate workspace app registry to edit for Dispatch to list the app. Always
+save a concise, human-readable `description` there; Dispatch lists and A2A
+connected-agent context use the app name plus description so agents know what
+the app does. Use relative workspace links like `/<app-name>` and never
+hardcode `localhost`, `127.0.0.1`, `8080`, `8100`, or any dev port in app
+cards, instructions, redirects, or navigation; the active workspace
+gateway/browser origin owns the port. React Router apps must preserve
+`APP_BASE_PATH` / `VITE_APP_BASE_PATH` in
 `app/entry.client.tsx` via `appBasePath()` so the app hydrates correctly when
 mounted at `/<app-name>`. Use the framework/template UI stack for standard UI:
 shadcn/ui components and `@tabler/icons-react`. Do not add `lucide-react` or
@@ -80,3 +83,9 @@ workspace root. In production, Dispatch posts new-app requests to Builder
 branch creation; Builder should still scaffold the separate workspace app. The
 workspace dev gateway (`pnpm dev`) detects new `apps/<app-name>` directories
 automatically.
+
+When using the starter template, treat it as scaffolding only. The finished app
+must be branded as the requested app, with its own home screen, navigation,
+package metadata, manifest, and domain workflow. Do not leave visible
+`Starter`, `Blank app`, `Start building`, or `New app` UI in a starter-derived
+app.

package/src/templates/workspace-root/AGENTS.md

@@ -108,6 +108,11 @@ coding agents can discover the same workspace-wide guidance from the root.
   should still create the separate workspace app, not patch starter. The local
   workspace gateway detects new app directories automatically and starts each
   app server lazily on first visit.
+- When using the starter template, treat it as scaffolding only. The finished
+  app must be branded as the requested app, with its own home screen,
+  navigation, package metadata, manifest, and domain workflow. Do not leave
+  visible `Starter`, `Blank app`, `Start building`, or `New app` UI in a
+  starter-derived app.
 
 ## Workspace Identity
 

package/src/templates/workspace-root/README.md

@@ -106,6 +106,9 @@ pnpm exec agent-native create crm --template=starter
 The CLI detects the workspace root and scaffolds a minimal app that already
 depends on `@{{APP_NAME}}/shared`. Edit only the routes you care about;
 auth, org switching, skills, and instructions come from the shared package.
+Starter is only the source scaffold: the finished app should use its own name,
+home screen, navigation, package metadata, and manifest rather than leaving
+starter or new-app UI in place.
 If the request starts from Dispatch in production, Dispatch sends it to Builder
 branch creation; that branch should still add a new `apps/<app-id>` workspace
 app rather than adding files to `apps/starter`.