@agent-native/core 0.98.0 → 0.98.2

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

@@ -30,7 +30,7 @@ The agent modifies data in SQL, but the UI runs in the browser. SSE bridges same
    useDbSync({ queryClient });
    ```
 
-   For each non-own event, `useDbSync` bumps a per-source counter (e.g. `dashboards`, `analyses`, `settings`, `action`) and invalidates a small fixed list of framework-internal prefixes (`["action"]`, `["app-state"]`, `["__set_url__"]`, etc.). It does **not** blanket-invalidate templates' own data queries for ordinary domain events — that caused a request storm in production. The exception is `source: "action"`: a successful mutating action is the framework-wide "agent changed app data" signal, so `useDbSync` also refreshes active React Query observers as a compatibility safety net for custom apps that have not yet moved every read to `useActionQuery` or source-versioned query keys.
+   For each non-own event, `useDbSync` bumps a per-source counter (e.g. `dashboards`, `analyses`, `settings`, `action`) and invalidates a small fixed list of framework-internal prefixes (`["action"]`, `["app-state"]`, `["__set_url__"]`, etc.). It does **not** blanket-invalidate templates' own data queries — that caused request storms in production. A successful mutating action refreshes active `useActionQuery` observers under the `["action"]` prefix. Browser actions carry a tab id so their originating tab ignores the sync echo while other tabs refresh. Legacy apps can opt into broader compatibility with `actionInvalidatePredicate`, but first-party apps should use action-backed or source-versioned query keys. Idle fallback polling runs once per minute; active agent work temporarily uses the faster cadence.
 
 3. **Templates fold per-source counters into their query keys.** This is the pattern that makes "agent writes show up without a manual refresh" reliable:
 
@@ -117,7 +117,7 @@ useQuery({
 | UI not updating after agent writes | Is `useDbSync` called with the correct `queryClient`? Does the affected query have an active observer?         |
 | Poll endpoint not responding       | Is `/_agent-native/poll` accessible? Is the server running?                                                    |
 | SSE not connecting                 | Is `/_agent-native/events` accessible and authenticated? Polling should still keep the UI fresh as fallback.   |
-| High CPU / event storms            | The agent is writing rapidly. Add `staleTime` to queries to debounce refetches.                                |
+| High CPU / event storms            | Use targeted source keys, settle bursty list counters, and avoid broad action invalidation.                   |
 
 ## Jitter Prevention
 

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

@@ -30,7 +30,7 @@ The agent modifies data in SQL, but the UI runs in the browser. SSE bridges same
    useDbSync({ queryClient });
    ```
 
-   For each non-own event, `useDbSync` bumps a per-source counter (e.g. `dashboards`, `analyses`, `settings`, `action`) and invalidates a small fixed list of framework-internal prefixes (`["action"]`, `["app-state"]`, `["__set_url__"]`, etc.). It does **not** blanket-invalidate templates' own data queries for ordinary domain events — that caused a request storm in production. The exception is `source: "action"`: a successful mutating action is the framework-wide "agent changed app data" signal, so `useDbSync` also refreshes active React Query observers as a compatibility safety net for custom apps that have not yet moved every read to `useActionQuery` or source-versioned query keys.
+   For each non-own event, `useDbSync` bumps a per-source counter (e.g. `dashboards`, `analyses`, `settings`, `action`) and invalidates a small fixed list of framework-internal prefixes (`["action"]`, `["app-state"]`, `["__set_url__"]`, etc.). It does **not** blanket-invalidate templates' own data queries — that caused request storms in production. A successful mutating action refreshes active `useActionQuery` observers under the `["action"]` prefix. Browser actions carry a tab id so their originating tab ignores the sync echo while other tabs refresh. Legacy apps can opt into broader compatibility with `actionInvalidatePredicate`, but first-party apps should use action-backed or source-versioned query keys. Idle fallback polling runs once per minute; active agent work temporarily uses the faster cadence.
 
 3. **Templates fold per-source counters into their query keys.** This is the pattern that makes "agent writes show up without a manual refresh" reliable:
 
@@ -117,7 +117,7 @@ useQuery({
 | UI not updating after agent writes | Is `useDbSync` called with the correct `queryClient`? Does the affected query have an active observer?         |
 | Poll endpoint not responding       | Is `/_agent-native/poll` accessible? Is the server running?                                                    |
 | SSE not connecting                 | Is `/_agent-native/events` accessible and authenticated? Polling should still keep the UI fresh as fallback.   |
-| High CPU / event storms            | The agent is writing rapidly. Add `staleTime` to queries to debounce refetches.                                |
+| High CPU / event storms            | Use targeted source keys, settle bursty list counters, and avoid broad action invalidation.                   |
 
 ## Jitter Prevention
 

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

@@ -170,9 +170,13 @@ Core routes plugin mounts these under `/_agent-native/secrets/` automatically:
 - Values are stored in `app_secrets` (created on-demand; no migration
   needed).
 - Encrypted at rest with AES-256-GCM. Key material is derived from
-  `SECRETS_ENCRYPTION_KEY` (preferred) or `BETTER_AUTH_SECRET` (fallback).
-  If neither is set, the framework uses a machine-local fallback and logs a
-  one-time warning — set `SECRETS_ENCRYPTION_KEY` in production.
+  `<APP_NAME>_SECRETS_ENCRYPTION_KEY` when set (for example,
+  `ANALYTICS_SECRETS_ENCRYPTION_KEY`), then `SECRETS_ENCRYPTION_KEY`, then
+  `BETTER_AUTH_SECRET`. App-scoped keys are useful when a local multi-app
+  workspace connects one app to its production database without replacing the
+  shared local authentication secret. If none is set, the framework uses a
+  machine-local fallback and logs a one-time warning — set stable key material
+  in production and in every runtime that reads the same encrypted data.
 
 ## Ad-hoc Keys
 

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

@@ -52,24 +52,54 @@ action before requesting microphone permission.
 - Starting voice mode collapses the chat into a persistent bottom-end speech
   orb. The orb stays visible above the chat even when the chat opens
   automatically. Clicking it shows or hides chat without ending the session;
-  ending the session is a separate, explicit control.
-- The orb's compact waveform must reflect actual microphone or assistant audio
-  activity. It is an audio-level indicator, not a decorative animation.
+  opening chat slides the orb clear of the sidebar. The progressively disclosed
+  controls contain only settings and the separate end-session action.
+- The orb's compact waveform stays visible for the full session and reflects
+  actual microphone or assistant audio activity. At silence it rests at its
+  baseline instead of turning into a loading spinner. While connecting, show a
+  distinct compact spinner; when the session becomes live, the assistant gives
+  one brief spoken greeting so readiness is unambiguous. Do not apply a
+  text-sized `max_output_tokens` cap to that audio greeting because audio tokens
+  can truncate it mid-sentence.
+- The orb settings cog opens in place without ending voice mode or navigating
+  away. Nested pickers must not dismiss the settings popover. Language and
+  intelligence update the active Realtime session; the microphone picker swaps
+  the live WebRTC input track and remembers the browser-local device choice;
+  an output-voice change updates immediately only before the assistant has
+  emitted audio and otherwise applies to the next conversation, matching the
+  Realtime API's voice immutability rule.
 - Semantic VAD keeps listening, starts responses automatically, and supports
   barge-in while the agent is speaking.
 - Function calls must cross the authenticated realtime tool bridge and enter
   `executeAgentToolCall`. Never call `ActionEntry.run` directly: that bypasses
   schema validation, approvals, audit/journal behavior, timeouts, redaction,
   and mutation refreshes.
-- Preserve the active browser-tab id in request context so `set-url`,
+- Preserve the active browser-tab id in request context so `set-url-path`,
   `set-search-params`, `view-screen`, and tab-scoped application state affect
-  the app the user is actually speaking to.
+  the app the user is actually speaking to. Realtime tool manifests are capped,
+  so prioritize `navigate`, `set-url-path`, `set-search-params`, and
+  `view-screen` before packing large template registries.
+- Keep `tool-search` in the initial Realtime manifest. A successful specific
+  search may expand the live session with matching action schemas, but the
+  server must derive those schemas from its own registry, bind authorization
+  to the authenticated voice session, and continue execution through
+  `executeAgentToolCall`. Treat `session.update.tools` as a full replacement:
+  preserve the pinned navigation/discovery tools, evict lower-priority entries
+  within the manifest cap, and wait for `session.updated` before asking the
+  model to continue with a newly discovered tool.
 - Do not persist audio or interim transcript deltas. Append completed user and
   assistant utterances as ordinary text messages to the exact chat thread
-  captured when the session starts. Ending voice mode opens that chat so the
-  user can continue over text. Store only compact lifecycle and latest context
-  at `application_state["realtime-voice-session"]`; delete it when the session
-  ends.
+  captured when the session starts. Input transcription completes
+  asynchronously from assistant generation, so reserve provider conversation
+  item order and publish only the contiguous completed sequence; never use
+  completion arrival time as chat order. Ending voice mode opens that chat so
+  the user can continue over text. Store only compact lifecycle and latest
+  context at `application_state["realtime-voice-session"]`; delete it when the
+  session ends.
+- Store the user-controlled language, intelligence, and output-voice choices at
+  `application_state["realtime-voice-prefs"]`. Keep this separate from
+  `voice-transcription-prefs`, which configures editable dictation rather than
+  the speech-to-speech session.
 - Missing-key failures should open Settings focused on the user-scoped
   `OPENAI_API_KEY` field. Never send, log, or echo the key to the browser.
 

package/corpus/core/src/vite/client.ts

@@ -2140,7 +2140,15 @@ function readAppChangelogMarkdown(
     .map((file) => {
       const filePath = path.join(pendingDir, file);
       watchFile(filePath);
-      return parsePendingEntry(fs.readFileSync(filePath, "utf-8"));
+      // `agent-native changelog add` prefixes every pending filename with its
+      // date. Preserve that date when a hand-written entry omits `date:` so a
+      // deployed What's new surface never groups an already-merged update
+      // under an inaccurate "Unreleased" heading.
+      const filenameDate = file.match(/^(\d{4}-\d{2}-\d{2})(?:-|\.md$)/)?.[1];
+      return parsePendingEntry(
+        fs.readFileSync(filePath, "utf-8"),
+        filenameDate,
+      );
     });
   return mergePendingChangelog(existing, pending);
 }

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

@@ -30,7 +30,7 @@ The agent modifies data in SQL, but the UI runs in the browser. SSE bridges same
    useDbSync({ queryClient });
    ```
 
-   For each non-own event, `useDbSync` bumps a per-source counter (e.g. `dashboards`, `analyses`, `settings`, `action`) and invalidates a small fixed list of framework-internal prefixes (`["action"]`, `["app-state"]`, `["__set_url__"]`, etc.). It does **not** blanket-invalidate templates' own data queries for ordinary domain events — that caused a request storm in production. The exception is `source: "action"`: a successful mutating action is the framework-wide "agent changed app data" signal, so `useDbSync` also refreshes active React Query observers as a compatibility safety net for custom apps that have not yet moved every read to `useActionQuery` or source-versioned query keys.
+   For each non-own event, `useDbSync` bumps a per-source counter (e.g. `dashboards`, `analyses`, `settings`, `action`) and invalidates a small fixed list of framework-internal prefixes (`["action"]`, `["app-state"]`, `["__set_url__"]`, etc.). It does **not** blanket-invalidate templates' own data queries — that caused request storms in production. A successful mutating action refreshes active `useActionQuery` observers under the `["action"]` prefix. Browser actions carry a tab id so their originating tab ignores the sync echo while other tabs refresh. Legacy apps can opt into broader compatibility with `actionInvalidatePredicate`, but first-party apps should use action-backed or source-versioned query keys. Idle fallback polling runs once per minute; active agent work temporarily uses the faster cadence.
 
 3. **Templates fold per-source counters into their query keys.** This is the pattern that makes "agent writes show up without a manual refresh" reliable:
 
@@ -117,7 +117,7 @@ useQuery({
 | UI not updating after agent writes | Is `useDbSync` called with the correct `queryClient`? Does the affected query have an active observer?         |
 | Poll endpoint not responding       | Is `/_agent-native/poll` accessible? Is the server running?                                                    |
 | SSE not connecting                 | Is `/_agent-native/events` accessible and authenticated? Polling should still keep the UI fresh as fallback.   |
-| High CPU / event storms            | The agent is writing rapidly. Add `staleTime` to queries to debounce refetches.                                |
+| High CPU / event storms            | Use targeted source keys, settle bursty list counters, and avoid broad action invalidation.                   |
 
 ## Jitter Prevention
 

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

@@ -28,6 +28,10 @@ agent answers about browser recordings in the Analytics template.
   `session-recording` access before reading private blob refs.
 - SQL inline chunks are a local/dev fallback only; production should use
   private or encrypted blob storage.
+- A local Analytics app pointed at a production database must also use the key
+  that encrypted those replay blobs. Set `ANALYTICS_SECRETS_ENCRYPTION_KEY` in
+  an untracked local env file; do not replace the workspace-wide
+  `BETTER_AUTH_SECRET` just to read production replay storage.
 - When sharing a replay with an external agent, use
   `create-session-replay-agent-link`. It mints a two-hour `agent_access` URL
   scoped to the recording, embeds a small SSR discovery payload on
@@ -98,11 +102,12 @@ agent answers about browser recordings in the Analytics template.
 - Wait for all replay chunks (`isComplete`) before constructing the rrweb
   `Replayer`. Progressive chunk publishes should only update the loading bar;
   rebuilding the player mid-load desyncs the scrubber and playhead.
-- Pass events to `Replayer` untouched (aside from stylesheet/script sanitization
-  that prevents blank frames from live CSS loads). Let rrweb own iframe sizing
-  via Meta / ViewportResize; use those dimensions only for CSS fit-to-stage of
-  the outer wrapper. Never rewrite Meta widths or force iframe dimensions —
-  that desyncs the FullSnapshot DOM and blanks the stage.
+- Pass events to `Replayer` untouched. rrweb rebuilds them in a sandboxed iframe;
+  pre-processing DOM, stylesheet, resource, or mutation payloads makes playback
+  diverge from the captured page. Let rrweb own iframe sizing via Meta /
+  ViewportResize, and keep the outer wrapper in that same coordinate system for
+  fit-to-stage scaling. Never clamp only one layer, rewrite Meta widths, or force
+  iframe dimensions — that desyncs the FullSnapshot DOM and breaks the stage.
 - The event timeline soft-highlights the active marker, auto-scrolls it into
   view (pausing briefly after manual scroll), and supports search. It appears
   beside the player from ~880px content width upward.

package/corpus/templates/analytics/AGENTS.md

@@ -39,6 +39,14 @@ details live in `.agents/skills/`.
   Prometheus credential slot. Treat it as demo-environment data: do not use it
   for `REAL_DATA_REQUIRED`, saved analyses, or real user analytics answers
   unless the user explicitly asks to inspect the demo dashboard.
+- Framework Demo mode is separate from the built-in `demo` source. While Demo
+  mode is enabled, Analytics line and area charts reshape each returned numeric
+  series into a deterministic, natural-looking upward trend using that series'
+  actual minimum, maximum, and normalized volatility. Smooth source series stay
+  smooth; spiky source series keep larger swings. This is presentation-only:
+  query results, tables, metrics, exports, and non-time-series charts remain
+  unchanged, so do not cite the displayed intermediate line/area points as
+  retrieved source values.
 - Every analytical answer should include enough audit context for the user to
   trust it: source(s), time window, filters, sample size or row count,
   join/match method when relevant, and caveats/gaps.
@@ -298,19 +306,15 @@ 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`.
-- Keep model cost, token volume, latency, error rate, explicit thumbs feedback,
-  optional inferred message sentiment, sentiment by main model, and expensive
-  agent-run panels in the canonical Agent Native dashboard
-  (`agent-native-templates-first-party`). Generation metrics use first-party
-  `$ai_generation` events; feedback panels use content-free `$ai_feedback`
-  events with `sentiment` (`positive` or `negative`) and model in `$ai_model` or
-  `model`. Treat these as explicit user ratings, never as inferred message
-  sentiment. Inferred panels separately use `$ai_sentiment` events with
-  `method = 'llm'`, `sentiment` (`positive`, `neutral`, or `negative`), the
-  attributed main model in `$ai_model` or `model`, and the classifier in
-  `classifier_model`. Never group the by-main-model panel on
-  `classifier_model`, and never split these panels into a separately installable
-  observability template.
+- Keep the canonical Agent Native dashboard
+  (`agent-native-templates-first-party`) focused: it includes one explicit
+  feedback-sentiment-by-model chart and one optional inferred-message-sentiment
+  chart, not the broader LLM cost, token, latency, or error suite. Explicit
+  feedback uses content-free `$ai_feedback` events with `sentiment` (`positive`
+  or `negative`) and model in `$ai_model` or `model`. Inferred sentiment uses
+  `$ai_sentiment` events with `method = 'llm'` and `sentiment` (`positive`,
+  `neutral`, or `negative`). Keep these panels in the canonical dashboard and
+  do not recreate a separately installable observability template.
 - 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/navigate.ts

@@ -1,7 +1,47 @@
 import { defineAction } from "@agent-native/core";
-import { writeAppState } from "@agent-native/core/application-state";
+import { writeAppStateForCurrentTab } from "@agent-native/core/application-state";
+import {
+  getRequestOrgId,
+  getRequestUserEmail,
+} from "@agent-native/core/server";
 import { z } from "zod";
 
+import { listDashboardSummaries } from "../server/lib/dashboards-store";
+
+function normalizeDashboardName(value: string): string {
+  return value.trim().replace(/\s+/g, " ").toLowerCase();
+}
+
+async function resolveDashboardIdByName(name: string): Promise<string> {
+  const email = getRequestUserEmail();
+  if (!email) throw new Error("Dashboard navigation requires authentication.");
+  const orgId = getRequestOrgId() || null;
+  const dashboards = await listDashboardSummaries(
+    { email, orgId },
+    { kind: "sql", archived: "active", hidden: "visible" },
+  );
+  const normalized = normalizeDashboardName(name);
+  const withoutDashboardSuffix = normalized.replace(/\s+dashboard$/, "");
+  const matches = dashboards.filter((dashboard) => {
+    const candidate = normalizeDashboardName(dashboard.name);
+    return candidate === normalized || candidate === withoutDashboardSuffix;
+  });
+  if (matches.length === 0) {
+    throw new Error(
+      `No accessible dashboard named "${name.trim()}" was found.`,
+    );
+  }
+  if (matches.length === 1) return matches[0]!.id;
+
+  const ownedMatches = matches.filter(
+    (dashboard) => dashboard.ownerEmail.toLowerCase() === email.toLowerCase(),
+  );
+  if (ownedMatches.length === 1) return ownedMatches[0]!.id;
+  throw new Error(
+    `More than one accessible dashboard is named "${name.trim()}". Use its dashboard id instead.`,
+  );
+}
+
 export default defineAction({
   description:
     "Navigate the UI to a specific view, dashboard, analysis, extension, Analytics session recording, Monitoring tab (uptime checks, public status pages, or captured errors), or Analytics agent-admin surface. For filter changes (dashboard filter query params like ?f_date=... or session filters like ?range=30d&q=signup), use the framework-level `set-search-params` tool instead of this action.",
@@ -16,6 +56,14 @@ export default defineAction({
       .string()
       .optional()
       .describe("Dashboard ID to open (used with view=adhoc)"),
+    dashboardName: z
+      .string()
+      .trim()
+      .min(1)
+      .optional()
+      .describe(
+        'Accessible SQL dashboard name to open when its id is unknown (for example, "Agent Native" or "Agent Native dashboard").',
+      ),
     analysisId: z
       .string()
       .optional()
@@ -70,6 +118,7 @@ export default defineAction({
     if (
       !args.view &&
       !args.dashboardId &&
+      !args.dashboardName &&
       !args.analysisId &&
       !args.extensionId &&
       !args.recordingId &&
@@ -81,13 +130,18 @@ export default defineAction({
       !args.errorIssueId
     ) {
       throw new Error(
-        "At least --view, --dashboardId, --analysisId, --extensionId, --recordingId, --agentsView, --dbAdminConnectionId, --monitoringView, --monitorId, --statusPageId, or --errorIssueId is required.",
+        "At least --view, --dashboardId, --dashboardName, --analysisId, --extensionId, --recordingId, --agentsView, --dbAdminConnectionId, --monitoringView, --monitorId, --statusPageId, or --errorIssueId is required.",
       );
     }
+    const dashboardId =
+      args.dashboardId ??
+      (args.dashboardName
+        ? await resolveDashboardIdByName(args.dashboardName)
+        : undefined);
     const nav: Record<string, string> = {};
     if (args.view) nav.view = args.view === "overview" ? "ask" : args.view;
-    if (args.dashboardId) {
-      nav.dashboardId = args.dashboardId;
+    if (dashboardId) {
+      nav.dashboardId = dashboardId;
       if (!args.view) nav.view = "adhoc";
     }
     if (args.analysisId) {
@@ -133,7 +187,7 @@ export default defineAction({
       nav.monitoringView = "errors";
       if (!args.view) nav.view = "monitoring";
     }
-    await writeAppState("navigate", nav);
+    await writeAppStateForCurrentTab("navigate", nav);
 
     const parts: string[] = [];
     if (nav.view) parts.push(nav.view);

package/corpus/templates/analytics/actions/view-screen.ts

@@ -1,8 +1,5 @@
 import { defineAction } from "@agent-native/core";
-import {
-  readAppState,
-  readAppStateForCurrentTab,
-} from "@agent-native/core/application-state";
+import { readAppStateForCurrentTab } from "@agent-native/core/application-state";
 import {
   getRequestUserEmail,
   getRequestOrgId,
@@ -37,12 +34,12 @@ export default defineAction({
   readOnly: true,
   run: async () => {
     const navigation = await readAppStateForCurrentTab("navigation");
-    const url = (await readAppState("__url__")) as {
+    const url = (await readAppStateForCurrentTab("__url__")) as {
       pathname?: string;
       search?: string;
       searchParams?: Record<string, string>;
     } | null;
-    const selectedObject = await readAppState("selected-object");
+    const selectedObject = await readAppStateForCurrentTab("selected-object");
 
     const screen: Record<string, unknown> = {};
     if (navigation) screen.navigation = navigation;

package/corpus/templates/analytics/app/components/ProviderCorpusJobNotifier.tsx

@@ -4,6 +4,7 @@ import { useNavigate } from "react-router";
 import { toast } from "sonner";
 
 import { useAuth } from "@/components/auth/AuthProvider";
+import { subscribeProviderCorpusJobSync } from "@/lib/provider-corpus-job-sync";
 
 type ProviderCorpusJobStatus =
   | "running"
@@ -41,23 +42,39 @@ type ProviderCorpusJobsResponse = {
 
 const STORAGE_KEY = "analytics.providerCorpusJobNotifier.seen.v1";
 const RECENT_WINDOW_MS = 24 * 60 * 60 * 1_000;
+const ACTIVE_JOB_POLL_MS = 15_000;
+
+export function providerCorpusJobsRefetchInterval(query: {
+  state: { data?: unknown };
+}): number | false {
+  const jobs = (query.state.data as ProviderCorpusJobsResponse | undefined)
+    ?.jobs;
+  return jobs?.some((entry) => entry.job.status === "running")
+    ? ACTIVE_JOB_POLL_MS
+    : false;
+}
 
 export function ProviderCorpusJobNotifier() {
   const { auth, isLoading } = useAuth();
   const t = useT();
   const navigate = useNavigate();
   const seenRef = useRef<Record<string, string> | null>(null);
-  const { data } = useActionQuery(
+  const { data, refetch } = useActionQuery(
     "provider-corpus-jobs",
     { operation: "list", limit: 20 },
     {
       enabled: Boolean(auth) && !isLoading,
-      refetchInterval: 15_000,
-      refetchIntervalInBackground: true,
+      refetchInterval: providerCorpusJobsRefetchInterval,
+      refetchIntervalInBackground: false,
       retry: false,
     },
   );
 
+  useEffect(() => {
+    if (!auth || isLoading) return;
+    return subscribeProviderCorpusJobSync(() => void refetch());
+  }, [auth, isLoading, refetch]);
+
   useEffect(() => {
     const jobs = (data as ProviderCorpusJobsResponse | undefined)?.jobs ?? [];
     if (!jobs.length) return;

package/corpus/templates/analytics/app/components/dashboard/SqlChart.tsx

@@ -1,4 +1,4 @@
-import { useT } from "@agent-native/core/client";
+import { useDemoModeStatus, useT } from "@agent-native/core/client";
 import { EmbeddedExtension } from "@agent-native/core/client/extensions";
 import {
   IconArrowsSort,
@@ -54,6 +54,7 @@ import {
 import { Skeleton } from "@/components/ui/skeleton";
 
 const PAGE_SIZE_OPTIONS = [10, 25, 50, 100];
+import { createDemoChartTrendRows } from "@/lib/demo-chart-trend";
 import { useSqlQuery } from "@/lib/sql-query";
 import { serializePanelSql } from "@/pages/adhoc/sql-dashboard/panel-sql";
 import { pivotRows } from "@/pages/adhoc/sql-dashboard/pivot";
@@ -994,6 +995,7 @@ export function SqlChart({
   onExportCsvChange,
 }: SqlChartProps) {
   const t = useT();
+  const { enabled: demoModeEnabled } = useDemoModeStatus();
   // Hooks must be called unconditionally before any early return.
   const isSection = panel.chartType === "section";
   const isExtension = panel.chartType === "extension";
@@ -1004,6 +1006,7 @@ export function SqlChart({
   const {
     data: result,
     isLoading,
+    isFetching,
     error: queryError,
   } = useSqlQuery(
     ["sql-chart", panel.id, sql, panel.source],
@@ -1023,7 +1026,7 @@ export function SqlChart({
   const error =
     rawRows.length === 0 ? (result?.error ?? queryErrorMessage) : undefined;
 
-  const { rows, forcedYKeys } = useMemo(() => {
+  const { rows: queryRows, forcedYKeys } = useMemo(() => {
     if (panel.config?.pivot && rawRows.length) {
       const pivoted = pivotRows(rawRows, panel.config.pivot);
       return { rows: pivoted.rows, forcedYKeys: pivoted.seriesKeys };
@@ -1032,8 +1035,20 @@ export function SqlChart({
   }, [rawRows, panel.config?.pivot]);
 
   const { xKey, yKeys } = useMemo(
-    () => detectKeys(rows, panel.config, forcedYKeys),
-    [rows, panel.config, forcedYKeys],
+    () => detectKeys(queryRows, panel.config, forcedYKeys),
+    [queryRows, panel.config, forcedYKeys],
+  );
+  const shouldCreateDemoTrend =
+    demoModeEnabled &&
+    (panel.chartType === "line" ||
+      panel.chartType === "area" ||
+      (panel.chartType as string) === "stacked-area");
+  const rows = useMemo(
+    () =>
+      shouldCreateDemoTrend
+        ? createDemoChartTrendRows(queryRows, yKeys, panel.id)
+        : queryRows,
+    [queryRows, yKeys, panel.id, shouldCreateDemoTrend],
   );
 
   // Section panels are pure layout — no query, no chart. Render a header with
@@ -1079,7 +1094,7 @@ export function SqlChart({
       : "min-h-[250px]";
   const placeholderPadY = isMetric ? "py-2" : "py-8";
 
-  if (!loadData || isLoading) {
+  if (!loadData || isLoading || isFetching) {
     return <SqlChartLoadingSkeleton panel={panel} />;
   }
 

package/corpus/templates/analytics/app/components/layout/Header.tsx

@@ -63,7 +63,7 @@ export function Header() {
       </div>
       <div className="flex items-center gap-2 shrink-0">
         {actions}
-        <RunsTray />
+        <RunsTray pollMs={0} />
         <AgentToggleButton />
       </div>
     </header>

package/corpus/templates/analytics/app/components/layout/Sidebar.tsx

@@ -68,6 +68,20 @@ type SidebarDashboard = {
   /** Id of the dashboard this one nests under in the sidebar, if any. */
   parentId?: string;
 };
+
+const SIDEBAR_SYNC_SETTLE_MS = 500;
+
+function useSettledSyncVersion(version: number): number {
+  const [settledVersion, setSettledVersion] = useState(version);
+  useEffect(() => {
+    const timeout = window.setTimeout(
+      () => setSettledVersion(version),
+      SIDEBAR_SYNC_SETTLE_MS,
+    );
+    return () => window.clearTimeout(timeout);
+  }, [version]);
+  return settledVersion;
+}
 import {
   DevDatabaseLink,
   FeedbackButton,
@@ -1751,12 +1765,13 @@ export function Sidebar({ mobile }: { mobile?: boolean } = {}) {
 
   // Fold per-source counters into sidebar list query keys so agent-driven
   // create/rename/archive/delete shows up without a manual refresh. We
-  // depend on `action` too because the agent runner emits an `action`
-  // event for every successful tool call — even when the matching
-  // resource-table emit (`dashboards` / `analyses`) is missed (e.g. event
-  // batching). See `use-change-version.ts` in @agent-native/core.
-  const dashboardsSync = useChangeVersions(["dashboards", "action"]);
-  const analysesSync = useChangeVersions(["analyses", "action"]);
+  // Domain counters keep these lists targeted. Folding the generic `action`
+  // counter into the keys makes unrelated background work cancel and restart
+  // both sidebar reads.
+  const dashboardsSync = useSettledSyncVersion(
+    useChangeVersions(["dashboards"]),
+  );
+  const analysesSync = useSettledSyncVersion(useChangeVersions(["analyses"]));
   const dashboardsSyncRef = useRef(dashboardsSync);
   const analysesSyncRef = useRef(analysesSync);
   dashboardsSyncRef.current = dashboardsSync;

package/corpus/templates/analytics/app/global.css

@@ -186,7 +186,7 @@
   .analytics-chat-intro {
   display: grid;
   width: 100%;
-  max-width: min(760px, 90%);
+  max-width: min(570px, 90%);
   gap: 0.5rem;
   margin: 0 auto 1rem;
   text-align: center;
@@ -223,12 +223,12 @@
   [data-agent-empty-state="centered"]
   .agent-plan-mode-callout {
   width: 100%;
-  max-width: min(760px, 90%);
+  max-width: min(570px, 90%);
   padding: 0;
 }
 
 .analytics-chat-panel [data-agent-empty-state="centered"] .agent-composer-root {
-  min-height: 10.5rem;
+  min-height: 7.875rem;
   border-color: hsl(var(--border));
   border-radius: 1rem;
   background: hsl(var(--card));
@@ -388,7 +388,7 @@
 .analytics-chat-panel
   [data-agent-empty-state="centered"]
   .agent-composer-prosemirror {
-  min-height: 6.75rem;
+  min-height: 5.0625rem;
   font-size: 1rem;
   line-height: 1.625rem;
 }
@@ -426,7 +426,7 @@
   .analytics-chat-panel
     [data-agent-empty-state="centered"]
     .agent-composer-root {
-    min-height: 9rem;
+    min-height: 6.75rem;
   }
 }
 
@@ -513,6 +513,11 @@
   overflow-wrap: anywhere;
 }
 
+.analytics-sessions-filter-search {
+  flex: 1 1 100%;
+  order: 4;
+}
+
 @container agent-native-main (min-width: 720px) {
   .analytics-sessions-page {
     padding-inline: 1.5rem;
@@ -520,6 +525,15 @@
 }
 
 @container analytics-sessions (min-width: 640px) {
+  .analytics-sessions-filter-bar {
+    flex-wrap: nowrap;
+  }
+
+  .analytics-sessions-filter-search {
+    flex: 1 1 0;
+    order: initial;
+  }
+
   .analytics-session-row {
     grid-template-columns: 104px minmax(0, 0.9fr) minmax(0, 1.15fr);
     align-items: center;
@@ -551,21 +565,6 @@
   .analytics-session-badges {
     justify-content: flex-end;
   }
-
-  .analytics-sessions-filter-extra {
-    grid-template-columns: repeat(2, minmax(0, 1fr));
-  }
-}
-
-@container analytics-sessions (min-width: 920px) {
-  .analytics-sessions-filter-grid {
-    grid-template-columns: 150px minmax(260px, 1fr) 160px auto auto;
-    align-items: center;
-  }
-
-  .analytics-sessions-filter-label {
-    min-width: 0;
-  }
 }
 
 @container analytics-sessions (min-width: 960px) {