@agent-native/core 0.85.7 → 0.86.1

package/corpus/core/src/templates/default/app/root.tsx

@@ -1,6 +1,7 @@
 import { useDbSync } from "@agent-native/core/client";
 import {
   AppProviders,
+  ErrorReportActions,
   appPath,
   getLocaleInitScript,
   getThemeInitScript,
@@ -66,6 +67,9 @@ const ERROR_COPY = {
       "This page doesn't exist. It may have been moved or deleted.",
     statusTitle: (status: number) => `${status} Error`,
     goHome: "Go home",
+    sendFeedback: "Send feedback",
+    feedbackPlaceholder: "Describe what happened before this error appeared.",
+    openGitHubIssue: "Open GitHub issue",
   },
   "zh-CN": {
     genericTitle: "出了点问题",
@@ -74,6 +78,9 @@ const ERROR_COPY = {
     notFoundDetails: "此页面不存在。它可能已被移动或删除。",
     statusTitle: (status: number) => `${status} 错误`,
     goHome: "返回首页",
+    sendFeedback: "发送反馈",
+    feedbackPlaceholder: "描述此错误出现前发生了什么。",
+    openGitHubIssue: "打开 GitHub issue",
   },
   "zh-TW": {
     genericTitle: "發生錯誤",
@@ -82,6 +89,9 @@ const ERROR_COPY = {
     notFoundDetails: "此頁面不存在，可能已被移動或刪除。",
     statusTitle: (status: number) => `${status} 錯誤`,
     goHome: "返回首頁",
+    sendFeedback: "傳送意見回饋",
+    feedbackPlaceholder: "描述此錯誤出現前發生了什麼。",
+    openGitHubIssue: "開啟 GitHub issue",
   },
   "es-ES": {
     genericTitle: "Algo salió mal",
@@ -91,6 +101,10 @@ const ERROR_COPY = {
       "Esta página no existe. Puede que se haya movido o eliminado.",
     statusTitle: (status: number) => `Error ${status}`,
     goHome: "Ir al inicio",
+    sendFeedback: "Enviar comentarios",
+    feedbackPlaceholder:
+      "Describe qué pasó antes de que apareciera este error.",
+    openGitHubIssue: "Abrir issue en GitHub",
   },
   "fr-FR": {
     genericTitle: "Une erreur est survenue",
@@ -100,6 +114,9 @@ const ERROR_COPY = {
       "Cette page n'existe pas. Elle a peut-être été déplacée ou supprimée.",
     statusTitle: (status: number) => `Erreur ${status}`,
     goHome: "Retour à l'accueil",
+    sendFeedback: "Envoyer un retour",
+    feedbackPlaceholder: "Décrivez ce qui s'est passé avant cette erreur.",
+    openGitHubIssue: "Ouvrir une issue GitHub",
   },
   "de-DE": {
     genericTitle: "Etwas ist schiefgelaufen",
@@ -109,6 +126,9 @@ const ERROR_COPY = {
       "Diese Seite existiert nicht. Sie wurde möglicherweise verschoben oder gelöscht.",
     statusTitle: (status: number) => `${status} Fehler`,
     goHome: "Zur Startseite",
+    sendFeedback: "Feedback senden",
+    feedbackPlaceholder: "Beschreiben Sie, was vor diesem Fehler passiert ist.",
+    openGitHubIssue: "GitHub-Issue öffnen",
   },
   "ja-JP": {
     genericTitle: "問題が発生しました",
@@ -118,6 +138,9 @@ const ERROR_COPY = {
       "このページは存在しません。移動または削除された可能性があります。",
     statusTitle: (status: number) => `${status} エラー`,
     goHome: "ホームへ",
+    sendFeedback: "フィードバックを送信",
+    feedbackPlaceholder: "このエラーの直前に起きたことを説明してください。",
+    openGitHubIssue: "GitHub issue を開く",
   },
   "ko-KR": {
     genericTitle: "문제가 발생했습니다",
@@ -127,6 +150,10 @@ const ERROR_COPY = {
       "이 페이지는 존재하지 않습니다. 이동되었거나 삭제되었을 수 있습니다.",
     statusTitle: (status: number) => `${status} 오류`,
     goHome: "홈으로 이동",
+    sendFeedback: "피드백 보내기",
+    feedbackPlaceholder:
+      "이 오류가 나타나기 전에 무슨 일이 있었는지 적어 주세요.",
+    openGitHubIssue: "GitHub issue 열기",
   },
   "pt-BR": {
     genericTitle: "Algo deu errado",
@@ -136,6 +163,9 @@ const ERROR_COPY = {
       "Esta página não existe. Ela pode ter sido movida ou excluída.",
     statusTitle: (status: number) => `Erro ${status}`,
     goHome: "Ir para o início",
+    sendFeedback: "Enviar feedback",
+    feedbackPlaceholder: "Descreva o que aconteceu antes deste erro aparecer.",
+    openGitHubIssue: "Abrir issue no GitHub",
   },
   "hi-IN": {
     genericTitle: "कुछ गलत हुआ",
@@ -144,6 +174,9 @@ const ERROR_COPY = {
     notFoundDetails: "यह पेज मौजूद नहीं है। इसे स्थानांतरित या हटाया गया हो सकता है।",
     statusTitle: (status: number) => `${status} त्रुटि`,
     goHome: "होम जाएं",
+    sendFeedback: "फ़ीडबैक भेजें",
+    feedbackPlaceholder: "इस त्रुटि से पहले क्या हुआ, उसका वर्णन करें।",
+    openGitHubIssue: "GitHub issue खोलें",
   },
   "ar-SA": {
     genericTitle: "حدث خطأ",
@@ -152,6 +185,9 @@ const ERROR_COPY = {
     notFoundDetails: "هذه الصفحة غير موجودة. ربما تم نقلها أو حذفها.",
     statusTitle: (status: number) => `خطأ ${status}`,
     goHome: "الذهاب إلى الرئيسية",
+    sendFeedback: "إرسال الملاحظات",
+    feedbackPlaceholder: "صف ما حدث قبل ظهور هذا الخطأ.",
+    openGitHubIssue: "فتح مشكلة في GitHub",
   },
 };
 
@@ -285,6 +321,17 @@ export function ErrorBoundary() {
         >
           {copy.goHome}
         </Link>
+        <ErrorReportActions
+          appName="Agent Native"
+          title={title}
+          details={details}
+          status={status}
+          issueTitle={`Error screen: ${title}`}
+          feedbackLabel={copy.sendFeedback}
+          feedbackPlaceholder={copy.feedbackPlaceholder}
+          githubLabel={copy.openGitHubIssue}
+          className="mt-4"
+        />
         {stack && (
           <pre className="mt-6 w-full text-left text-xs overflow-auto p-4 bg-muted rounded">
             <code>{stack}</code>

package/corpus/core/src/templates/default/package.json

@@ -23,8 +23,8 @@
     "zod": "^4.4.3"
   },
   "devDependencies": {
-    "@react-router/dev": "^8.0.1",
-    "@react-router/fs-routes": "^8.0.1",
+    "@react-router/dev": "^8.1.0",
+    "@react-router/fs-routes": "^8.1.0",
     "@tailwindcss/typography": "^0.5.20",
     "@tailwindcss/vite": "^4.1.18",
     "@tanstack/react-query": "^5.99.2",
@@ -38,7 +38,7 @@
     "oxfmt": "catalog:",
     "react": "catalog:",
     "react-dom": "catalog:",
-    "react-router": "^8.0.1",
+    "react-router": "^8.1.0",
     "sonner": "^2.0.7",
     "tailwind-merge": "^3.5.0",
     "tailwindcss": "^4.1.18",

package/corpus/core/src/templates/workspace-core/.agents/skills/client-methods/SKILL.md

@@ -36,8 +36,16 @@ method gives the UI, docs, and future agents one stable contract.
    | Agent chat context | Agent chat client helpers from `@agent-native/core/client` |
    | Ask the user a multiple-choice question from app code | `askUserQuestion` from `@agent-native/core/client` (renders inline in the agent panel; answer goes to the agent — do not build a custom modal) |
    | Live sync | `useDbSync`, `useChangeVersion`, `useChangeVersions` |
+   | Listen to the shared SSE/poll change stream | `subscribeSyncEvents` from `@agent-native/core/client` — never open a second `EventSource` to `/_agent-native/events` |
    | Extension iframe calls | `appAction`, `appFetch`, `extensionFetch` from the extension runtime |
 
+   Action fetch behavior: every `useActionQuery` / `useActionMutation` /
+   `callAction` request is bounded by a 60s timeout, and timeouts surface as
+   errors instead of retrying silently. `useActionQuery` cancels superseded
+   requests automatically via React Query's abort signal. For imperative
+   calls, `callAction(name, params, { method, signal, timeoutMs })` accepts an
+   `AbortSignal` and a `timeoutMs` override for legitimately long operations.
+
 2. If no client API exists, add the narrowest helper at the boundary.
 
    - Put shared framework helpers in `packages/core/src/client/*`.

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

@@ -232,3 +232,25 @@ This layer is optional and **no-op by default**:
 - Even with the api package installed, it ships a default no-op tracer. Spans become real only once the **host registers a `TracerProvider`** (via `@opentelemetry/sdk-node` or similar). The framework deliberately does not depend on the heavy SDK/exporter packages and never registers a provider itself — instrumentation is opt-in by the embedding app.
 
 The loop emits `agent.run` (with `agent.run_id`, `agent.thread_id`, `agent.user_id`, `agent.model`), `tool.call` (`tool.name` + status), and `llm.call` spans, each finished with OK/ERROR status. This is purely additive to the in-house `agent_trace_spans` / `agent_trace_summaries` tables. Source: `packages/core/src/observability/tracing.ts` + `traces.ts`. See the Observability doc for the full table.
+
+## Tracking Bridge
+
+Instrumented agent loops also emit one server-side tracking event per completed
+LLM generation:
+
+- Event name: `$ai_generation`
+- Provider path: `track()` from `@agent-native/core/tracking`, so configured
+  PostHog, Agent Native Analytics, Mixpanel, Amplitude, and webhook providers
+  receive it through the same best-effort fan-out as other tracking events.
+- PostHog shape: uses AI Observability properties such as `$ai_trace_id`,
+  `$ai_session_id`, `$ai_model`, `$ai_provider`, `$ai_input_tokens`,
+  `$ai_output_tokens`, `$ai_latency`, `$ai_total_cost_usd`, and `$ai_is_error`.
+- Agent Native Analytics shape: the same event lands in `analytics_events` with
+  mirrored query-friendly properties such as `run_id`, `thread_id`,
+  `cost_cents_x100`, `duration_ms`, `tool_calls`, `successful_tools`,
+  `failed_tools`, and `status`.
+
+Do not build a separate LLM-observability ingestion API unless there is a clear
+reason the tracking provider registry cannot express the use case. Keep prompt,
+tool input, and model output content out of tracking by default; use the existing
+observability config flags for local trace content capture.

package/corpus/core/src/templates/workspace-core/.agents/skills/real-time-collab/SKILL.md

@@ -249,34 +249,97 @@ type PatchDeckOp =
 Concurrent edits to different slides both succeed at the action level; there
 is no whole-deck LWW. Forms use the same shape with field-level ops.
 
-## Collaborative Undo Scoping (Y.UndoManager)
+## Agent Presence & Lingering Edit Highlights
+
+The agent is a *visible* collaborator, not a silent content-swapper. Core
+handles most of this automatically:
+
+- **Auto-presence on agent writes** — any `applyText` / `searchAndReplace` /
+  `applyJson` / `applyPatchOps` call with `requestSource: "agent"` publishes
+  an agent awareness entry plus a `recentEdits` attribution describing what
+  changed. Actions that route writes through the collab layer get full
+  presence UX with zero extra wiring.
+- **Linger** — `agentLeaveDocument` (and the auto-presence path) keeps the
+  agent's awareness entry alive for ~6s (`AGENT_PRESENCE_LINGER_MS`) after the
+  last edit so viewers see who just changed what. Pass `{ lingerMs: 0 }` to
+  clear immediately. On serverless the linger degrades to the 30s awareness
+  expiry.
+- **`agentTouchDocument(docId, { edit, metadata })`** — refcount-neutral
+  presence + attribution for actions that write SQL directly (no collab doc).
+  `edit.descriptor` is one of `{kind:"text",quote}`, `{kind:"selector",selector}`,
+  `{kind:"paths",paths}`, `{kind:"doc"}`.
+- **Durable across instances** — awareness is mirrored to the additive
+  `_collab_awareness` table, so presence written by an action in one
+  serverless invocation is visible to clients polling any other instance.
+
+Client rendering:
+
+```tsx
+import {
+  usePresence, useRecentEdits, RecentEditHighlights,
+  PresenceBar, LiveCursorOverlay, RemoteSelectionRings,
+} from "@agent-native/core/client";
+
+const { others, setPresence } = usePresence(awareness, ydoc?.clientID);
+const recentEdits = useRecentEdits(others); // non-expired, ~6s TTL
+
+<RecentEditHighlights
+  edits={recentEdits}
+  containerRef={containerRef}
+  resolveRect={(edit) => /* map descriptor → DOMRect, or null */ null}
+/>
+```
+
+Humans get the same treatment: call `publishRecentEdit(awareness, { descriptor })`
+from local mutation paths so peers see lingering highlights for human edits
+too. `CollabUser.avatarUrl` puts faces on avatars, cursors, and edit tags.
+
+## Per-User Undo (never revert someone else's work)
 
-Scope undo/redo to the local user's own edits so peer and agent changes are
-never accidentally reversed:
+Undo must only reverse the local user's edits — and must never restore a
+whole-document snapshot (that clobbers concurrent edits by peers/the agent).
+Core ships two primitives:
+
+**Yjs surfaces — `useCollabUndo`** (wraps `Y.UndoManager` lifecycle):
 
 ```ts
-import * as Y from "yjs";
+import { useCollabUndo } from "@agent-native/core/client";
+
+const { undo, redo, canUndo, canRedo, transactLocal, localOrigin } =
+  useCollabUndo({
+    ydoc,
+    scope: (doc) => doc.getText("content"),
+    captureTimeout: 500,
+    enableKeyboardShortcuts: true, // Mod+Z / Shift+Mod+Z / Mod+Y
+  });
 
-const LOCAL_EDIT_ORIGIN = "local";
+// Tag every local mutation so it is captured:
+transactLocal(() => { /* mutate shared types */ });
+```
 
-const undoManager = new Y.UndoManager(ydoc.getText("content"), {
-  trackedOrigins: new Set([LOCAL_EDIT_ORIGIN]),
-  captureTimeout: 800, // coalesces rapid slider drags into one undo step
-});
+Remote (`"remote"`) and agent (`"agent"`/`"server"`) origins are never
+captured. The manager is recreated/destroyed automatically when `ydoc`
+changes. (TipTap's Collaboration extension already provides this behavior
+for its own editor content.)
 
-// Mark local edits with the tracked origin
-ydoc.transact(() => {
-  // apply local change
-}, LOCAL_EDIT_ORIGIN);
+**Op-based surfaces (slides/forms) — `useLocalOpUndo`**: record inverse
+granular ops for each local mutation; undo replays the inverse ops through
+your normal granular mutation path:
 
-undoManager.undo(); // only reverses LOCAL_EDIT_ORIGIN transactions
-undoManager.redo();
+```ts
+const { push, undo, redo, canUndo, canRedo } = useLocalOpUndo({
+  apply: (ops) => applyGranularOps(ops), // your patch path
+});
+
+push({
+  undo: [{ type: "patch", slideId, fields: prevFields }],
+  redo: [{ type: "patch", slideId, fields: nextFields }],
+  coalesceKey: `${slideId}:content`, // merge rapid bursts into one step
+});
 ```
 
-Rules:
-- Pass a `Set` to `trackedOrigins` — not an array.
-- Remote (`"remote"`) and agent (`"agent"`) origins are never captured.
-- Recreate and destroy the manager when the active document changes.
+Entries whose target no longer exists should fail soft (skip), never reset
+the whole history — external/agent edits must not wipe the user's undo stack.
 
 ## Common Pitfalls
 

package/corpus/core/src/templates/workspace-core/.agents/skills/real-time-sync/SKILL.md

@@ -58,6 +58,21 @@ The agent modifies data in SQL, but the UI runs in the browser. SSE bridges same
 
 - Don't create manual polling loops — `useDbSync()` handles SSE plus fallback polling
 - Don't create your own fetch-based polling alongside `useDbSync` — use the `onEvent` callback for custom handling
+- Don't open your own `EventSource` to `/_agent-native/events`. A tab must hold exactly ONE SSE connection no matter how many features listen — extra streams eat the browser's per-origin connection budget and can starve ordinary data fetches (worst on HTTP/1.1 dev servers). Subscribe to the shared transport instead:
+
+  ```ts
+  import { subscribeSyncEvents } from "@agent-native/core/client";
+
+  const unsubscribe = subscribeSyncEvents({
+    onEvents: (events) => {
+      // filter by event.source and handle push-style updates
+    },
+    // Optional: relax your own fallback cadence while push is healthy.
+    onSseStateChange: (connected) => {},
+  });
+  ```
+
+  `useDbSync` and every `subscribeSyncEvents` subscriber share one `EventSource` and one fallback poll loop per tab — this is how collaborative documents receive doc updates and cursor/awareness events.
 
 ## Which sources to depend on
 

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

@@ -25,6 +25,14 @@ Agent-native apps use Drizzle ORM over the configured SQL backend. Local develop
 
 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.
 
+### Naming migrations
+
+When you add an entry to a `runMigrations([...])` list (`@agent-native/core/db`), always give it a unique `name:` slug (e.g. `name: "analytics-alert-rules-table"`) alongside its `version`. Never renumber or reuse version numbers on existing entries.
+
+Why: version numbers alone are not a safe identity. Two branches that each independently extend the same migration list can ship different DDL under the same version numbers — whichever branch deploys first "claims" those version numbers in the bookkeeping table, and the other branch's DDL is silently treated as already applied even though it never ran. This exact collision took down analytics: parallel branches both extended their migration list through v75-v83 with different DDL, so `analytics_alert_rules`, `analytics_alert_incidents`, and `session_recordings.network_error_count` never made it to production despite the bookkeeping table showing every version as applied. A `name:` slug is tracked independently of version numbers, so it applies exactly once per database regardless of what any other branch already recorded.
+
+Existing unnamed migrations don't need to be renamed retroactively (the two gating strategies coexist), but any new entry should always carry a name.
+
 ### Core SQL Stores (auto-created, available in all templates)
 
 | Store               | Purpose                                              | Access                                     |

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

@@ -141,6 +141,7 @@ Other framework-level baseline events:
 - `signup` from Better Auth user creation, with `auth_provider`, `auth_user_id`, and first-touch referral attribution (`referral_source`, `referrer_user`, `referral_medium`, `referral_campaign`, `utm_*`, `first_touch_path`, `landing_referrer` — see "Referral / viral attribution" above)
 - `builder connect clicked` and `builder connect popup blocked` from browser Connect Builder CTAs
 - `builder connect started`, `builder connect succeeded`, `builder connect failed`, `builder disconnect succeeded`, and `builder disconnect failed` from the Builder connection routes, with LLM connection context when resolvable
+- `$ai_generation` from instrumented agent loops, with PostHog AI Observability fields such as `$ai_trace_id`, `$ai_session_id`, `$ai_model`, `$ai_provider`, `$ai_input_tokens`, `$ai_output_tokens`, `$ai_latency`, `$ai_total_cost_usd`, and mirrored Agent Native query fields such as `run_id`, `thread_id`, `cost_cents_x100`, `duration_ms`, `tool_calls`, and `status`. Prompt, tool argument, and output content is not included by default.
 
 For new lifecycle events, call `track()` server-side when the server is the source of truth, and `trackEvent()` client-side only for browser interactions.
 

package/corpus/core/src/tracking/providers.ts

@@ -134,16 +134,37 @@ function shouldSkipAgentNativeAnalyticsForLocalhost(): boolean {
 
 // ─── PostHog ───────────────────────────────────────────────────────────────
 
+function isPostHogAiObservabilityEvent(eventName: string): boolean {
+  return eventName.startsWith("$ai_");
+}
+
 function createPostHogProvider(apiKey: string, host: string): TrackingProvider {
   return {
     name: "posthog",
     track(event: TrackingEvent) {
+      const distinctId = event.userId || "anonymous";
+      if (isPostHogAiObservabilityEvent(event.name)) {
+        enqueue(
+          `${host}/i/v0/e/`,
+          JSON.stringify({
+            api_key: apiKey,
+            event: event.name,
+            properties: {
+              distinct_id: distinctId,
+              ...event.properties,
+              timestamp: event.timestamp,
+            },
+          }),
+        );
+        return;
+      }
+
       enqueue(
         `${host}/capture/`,
         JSON.stringify({
           api_key: apiKey,
           event: event.name,
-          distinct_id: event.userId || "anonymous",
+          distinct_id: distinctId,
           properties: {
             ...event.properties,
             timestamp: event.timestamp,

package/corpus/templates/analytics/.agents/skills/real-time-sync/SKILL.md

@@ -58,6 +58,21 @@ The agent modifies data in SQL, but the UI runs in the browser. SSE bridges same
 
 - Don't create manual polling loops — `useDbSync()` handles SSE plus fallback polling
 - Don't create your own fetch-based polling alongside `useDbSync` — use the `onEvent` callback for custom handling
+- Don't open your own `EventSource` to `/_agent-native/events`. A tab must hold exactly ONE SSE connection no matter how many features listen — extra streams eat the browser's per-origin connection budget and can starve ordinary data fetches (worst on HTTP/1.1 dev servers). Subscribe to the shared transport instead:
+
+  ```ts
+  import { subscribeSyncEvents } from "@agent-native/core/client";
+
+  const unsubscribe = subscribeSyncEvents({
+    onEvents: (events) => {
+      // filter by event.source and handle push-style updates
+    },
+    // Optional: relax your own fallback cadence while push is healthy.
+    onSseStateChange: (connected) => {},
+  });
+  ```
+
+  `useDbSync` and every `subscribeSyncEvents` subscriber share one `EventSource` and one fallback poll loop per tab — this is how collaborative documents receive doc updates and cursor/awareness events.
 
 ## Which sources to depend on
 

package/corpus/templates/analytics/.agents/skills/session-replay/SKILL.md

@@ -46,10 +46,15 @@ agent answers about browser recordings in the Analytics template.
   custom events tagged `agent-native.console` and `agent-native.network`.
 - Capture is on by default whenever session replay is enabled. Tune or disable
   it with the `console` / `network` options on the session replay config; each
-  accepts a boolean or an options object (`{ maxEvents?: number }`).
-- Privacy bounds: request/response bodies and headers are never captured, URLs
-  are scrubbed, messages are truncated, and recorder self-traffic (the replay
-  ingest and tracking endpoints) is excluded.
+  accepts a boolean or an options object (`{ maxEvents?: number }`); `network`
+  also accepts `captureErrorBodies` (default true) and `maxErrorBodyLength`
+  (default 2048) to control the bounded 5xx response-body snippet.
+- Privacy bounds: request bodies and headers are never captured. Response
+  bodies are captured only as a bounded, redacted snippet for 5xx (server
+  error) responses, capped at `maxErrorBodyLength` chars; non-5xx and
+  network-failure (status 0) responses never carry a body. URLs are scrubbed,
+  messages are truncated, and recorder self-traffic (the replay ingest and
+  tracking endpoints) is excluded.
 - Per-session budgets: 1000 console events and 2000 network events, with a
   truncation notice event once a budget is hit.
 - On ingest, `deriveReplaySignals` computes the real `errorCount` from tagged
@@ -65,9 +70,19 @@ agent answers about browser recordings in the Analytics template.
 - The agent timeline includes `console-error` / `network-error` markers; error
   markers are kept preferentially under the 200-marker cap.
 - `apis.diagnostics` advertises the fuller bounded list:
-  `GET /api/session-replay/agent-diagnostics.json?id=<recordingId>&agent_access=<token>&kind=console|network|all&level=<level>&limit=<n>`
+  `GET /api/session-replay/agent-diagnostics.json?id=<recordingId>&agent_access=<token>&kind=console|network|all&level=<level>&limit=<n>&offset=<n>&fromMs=<n>&toMs=<n>`
   (limit defaults to 200, max 500). It uses the same recording-scoped
   `agent_access` token as the other agent JSON APIs.
+- `offset` and `fromMs`/`toMs` (inclusive offsetMs window) enable full
+  enumeration of a session's captured entries: page with `offset`, or window
+  with `fromMs`/`toMs` around a timeline marker's `offsetMs`. Providing any of
+  these switches ordering to strictly chronological (no errors-first
+  reshuffle) so pages are stable and disjoint. `total`/`errorCount`/
+  `warnCount`/`failedCount` reflect the filtered (windowed/level/kind)
+  population, not just the returned page, and each kind's response includes
+  `hasMore` alongside `truncated` so an agent can tell whether more entries
+  remain. Route validation rejects negative/non-numeric `offset`/`fromMs`/
+  `toMs` and `fromMs > toMs` with 400.
 
 ## Dev Tools Panel
 

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

@@ -25,6 +25,14 @@ Agent-native apps use Drizzle ORM over the configured SQL backend. Local develop
 
 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.
 
+### Naming migrations
+
+When you add an entry to a `runMigrations([...])` list (`@agent-native/core/db`), always give it a unique `name:` slug (e.g. `name: "analytics-alert-rules-table"`) alongside its `version`. Never renumber or reuse version numbers on existing entries.
+
+Why: version numbers alone are not a safe identity. Two branches that each independently extend the same migration list can ship different DDL under the same version numbers — whichever branch deploys first "claims" those version numbers in the bookkeeping table, and the other branch's DDL is silently treated as already applied even though it never ran. This exact collision took down analytics: parallel branches both extended their migration list through v75-v83 with different DDL, so `analytics_alert_rules`, `analytics_alert_incidents`, and `session_recordings.network_error_count` never made it to production despite the bookkeeping table showing every version as applied. A `name:` slug is tracked independently of version numbers, so it applies exactly once per database regardless of what any other branch already recorded.
+
+Existing unnamed migrations don't need to be renamed retroactively (the two gating strategies coexist), but any new entry should always carry a name.
+
 ### Core SQL Stores (auto-created, available in all templates)
 
 | Store               | Purpose                                              | Access                                     |

package/corpus/templates/analytics/AGENTS.md

@@ -71,6 +71,27 @@ details live in `.agents/skills/`.
 - For shipped dashboard templates, call `list-dashboard-templates` first, then
   `install-dashboard-template` with the selected `templateId`. Do not recreate a
   catalog template by hand unless the user asks for a custom variant.
+- Agent LLM observability is collected through the same first-party tracking
+  API as product analytics. Core emits PostHog-compatible `$ai_generation`
+  events when emitting apps are configured with `AGENT_NATIVE_ANALYTICS_PUBLIC_KEY`
+  and `AGENT_NATIVE_ANALYTICS_ENDPOINT` (or the default hosted endpoint). Query
+  these with `query-agent-native-analytics` using `event_name = '$ai_generation'`;
+  useful JSON properties include `$ai_trace_id` / `run_id`, `$ai_session_id` /
+  `thread_id`, `$ai_model` / `model`, `$ai_provider` / `provider`,
+  `$ai_input_tokens`, `$ai_output_tokens`, `cache_read_tokens`,
+  `cache_write_tokens`, `cost_cents_x100`, `$ai_total_cost_usd`, `duration_ms`
+  / `$ai_latency`, `status`, `tool_calls`, `successful_tools`, `failed_tools`,
+  and `$ai_error` / `error_message`. Do not expect prompts, tool args, or model
+  responses in these tracked events by default.
+- `/agents` is the Analytics home for core agent-admin surfaces. The default
+  Monitoring view embeds the shared observability dashboard for traces,
+  conversations, evals, experiments, and feedback. The Advanced menu opens
+  `/agents?view=database`, where organization owners/admins can connect other
+  agent-native app databases and use the shared database admin tool for table
+  browsing, row editing, and SQL inspection. This surface is for connected
+  target app databases, not broad access to all Analytics data. Keep future
+  agent-admin additions inside this route instead of adding many top-level
+  sidebar tabs.
 - For dashboard edits, default to `mutate-dashboard` with its typed
   `dashboard.*` script API. It supports id-based panel moves, title/SQL/config
   edits, inserts, duplication, removal, and dashboard field patches in one
@@ -136,8 +157,9 @@ details live in `.agents/skills/`.
 - `navigation` exposes current dashboard, analysis, source, chart, and selected
   context.
 - `navigate` moves the user to the relevant analytics view, including
-  `view="catalog"` for the template catalog and `view="sessions"` for session
-  replay.
+  `view="catalog"` for the template catalog, `view="sessions"` for session
+  replay, and `view="agents"` / `agentsView="database"` with optional
+  `dbAdminConnectionId` for agent monitoring or connected app database admin.
 - Use `view-screen` when the active dashboard/chart context is unclear.
 
 ## Session Replay
@@ -155,14 +177,18 @@ details live in `.agents/skills/`.
   scoped to one recording for two hours; SSR embeds an agent discovery payload
   and the JSON APIs expose only summary/timeline metadata plus bounded event
   reads.
-- Recordings also capture console logs and network request metadata (no
-  bodies/headers, scrubbed URLs, truncated messages, per-session budgets);
-  ingest derives `errorCount`/`networkErrorCount` and adds
+- Recordings also capture console logs and network request metadata (request
+  bodies/headers never captured; response bodies captured only as bounded,
+  redacted 5xx snippets; scrubbed URLs, truncated messages, per-session
+  budgets); ingest derives `errorCount`/`networkErrorCount` and adds
   `console-error`/`network-error` timeline markers.
 - The agent context includes a bounded `diagnostics` section (errors first) and
   advertises `GET /api/session-replay/agent-diagnostics.json` with
   `kind`/`level`/`limit` params (limit max 500) under the same `agent_access`
-  token — the primary signal when debugging a user-reported issue.
+  token — the primary signal when debugging a user-reported issue. `offset` and
+  `fromMs`/`toMs` page/window the same endpoint in strictly chronological order
+  (with `hasMore`/`truncated` per kind) so an agent can enumerate every
+  captured entry in a large session.
 - The replay player has a Dev Tools panel with Console and Network tabs
   (filters, search, jump-to-seek, error badge); extend it rather than adding a
   separate replay debugging surface. See the `session-replay` skill.
@@ -185,6 +211,9 @@ details live in `.agents/skills/`.
 - `install-dashboard-template` installs a catalog template into normal
   SQL-backed dashboards. Required: `templateId`. Optional: `dashboardId`,
   `name`, `overwrite`, `forceNew`, and `mergePanels`.
+- The LLM observability dashboard template is `agent-observability-llm`. Install
+  it when the user wants model cost, token volume, latency, error rate, or top
+  expensive agent-run visibility from first-party `$ai_generation` events.
 - To add a template's panels to an existing dashboard, call
   `install-dashboard-template` with `mergePanels: true` and the existing
   `dashboardId`. It appends only the template panels whose id is not already

package/corpus/templates/analytics/actions/delete-db-admin-connection.ts

@@ -0,0 +1,19 @@
+import { defineAction } from "@agent-native/core/action";
+import { z } from "zod";
+
+import {
+  deleteDbAdminConnection,
+  requireDbAdminContextFromRequest,
+} from "../server/lib/db-admin-connections";
+
+export default defineAction({
+  description:
+    "Remove a connected agent-native app database from the Analytics DB admin surface and delete its encrypted connection secrets. Requires active organization owner/admin role.",
+  schema: z.object({
+    id: z.string().min(1).describe("Connection id to remove."),
+  }),
+  run: async ({ id }, ctx) => {
+    const admin = await requireDbAdminContextFromRequest(ctx);
+    return deleteDbAdminConnection(admin, id);
+  },
+});

package/corpus/templates/analytics/actions/list-db-admin-connections.ts

@@ -0,0 +1,18 @@
+import { defineAction } from "@agent-native/core/action";
+import { z } from "zod";
+
+import {
+  listDbAdminConnections,
+  requireDbAdminContextFromRequest,
+} from "../server/lib/db-admin-connections";
+
+export default defineAction({
+  description:
+    "List admin-only connected agent-native app databases available in Analytics DB admin. Requires the caller to be an owner or admin of the active organization.",
+  schema: z.object({}),
+  http: { method: "GET" },
+  run: async (_args, ctx) => {
+    const admin = await requireDbAdminContextFromRequest(ctx);
+    return listDbAdminConnections(admin);
+  },
+});