@agent-native/core 0.99.0 → 0.99.2

package/corpus/core/src/deploy/workspace-deploy.ts

@@ -416,7 +416,7 @@ function writeCloudflareRoutingManifest(distDir: string, apps: string[]): void {
   const dispatch = apps
     .map(
       (a) =>
-        `  if (pathname === "/${a}" || pathname.startsWith("/${a}/")) return ${moduleIdent(a)}.fetch(requestForMountedApp(request, "/${a}"), env, ctx);`,
+        `  if (pathname === "/${a}" || pathname === "/${a}.data" || pathname.startsWith("/${a}/")) return ${moduleIdent(a)}.fetch(requestForMountedApp(request, "/${a}"), env, ctx);`,
     )
     .join("\n");
   const dispatchRootFrameworkRoutes = apps.includes("dispatch")
@@ -880,7 +880,7 @@ function patchNetlifyFunctionEntry(
   const pathConfig =
     app === "dispatch"
       ? ["/_agent-native/*", "/.well-known/*", `${basePath}/*`]
-      : [basePath, `${basePath}/*`];
+      : [basePath, `${basePath}.data`, `${basePath}/*`];
   const normalizeBasePathHelper =
     app === "dispatch"
       ? ""

package/corpus/core/src/server/action-discovery.ts

@@ -599,7 +599,6 @@ export async function mergeCoreSharingActions(
       "change-appearance",
       () => import("../appearance/actions/change-appearance.js"),
     ],
-    ["toggle-demo-mode", () => import("../demo/actions/toggle-demo-mode.js")],
     // Audit log — read surface (who changed what, when, agent vs human).
     [
       "list-audit-events",

package/corpus/core/src/server/agent-chat/action-filters-a2a.ts

@@ -6,9 +6,11 @@ import {
   type A2AToolResultSummary,
 } from "../../a2a/artifact-response.js";
 import { collectFinalResponseTextFromAgentEvents } from "../../a2a/response-text.js";
+import { resolveMainChatMaxOutputTokens } from "../../agent/engine/output-tokens.js";
 import type { EngineTool } from "../../agent/engine/types.js";
 import {
   filterInitialEngineTools,
+  resolveAgentRequestReasoningEffort,
   type ActionEntry,
 } from "../../agent/production-agent.js";
 import { runAgentLoopDirectWithSoftTimeout } from "../../agent/run-loop-with-resume.js";
@@ -160,6 +162,17 @@ function runDelegatedAgentLoop(
   return runner(
     {
       ...runOptions,
+      // Delegated runs resolve their own model and do not pass through the
+      // interactive request handler's output-token setup. Use the same
+      // model-aware headroom here so reasoning models (notably GPT-5.x) do
+      // not spend the small internal default entirely on reasoning before
+      // emitting a tool call or answer. Preserve explicit test/caller values.
+      maxOutputTokens:
+        runOptions.maxOutputTokens ??
+        resolveMainChatMaxOutputTokens(runOptions.model),
+      reasoningEffort:
+        runOptions.reasoningEffort ??
+        resolveAgentRequestReasoningEffort({ model: runOptions.model }),
       finalResponseGuard: pluginOptions.finalResponseGuard,
     },
     pluginOptions.runSoftTimeoutMs,

package/corpus/core/src/server/agent-teams.ts

@@ -18,6 +18,7 @@
 import { AsyncLocalStorage } from "node:async_hooks";
 
 import { applyAgentTextEventToBuffer } from "../a2a/response-text.js";
+import { resolveMainChatMaxOutputTokens } from "../agent/engine/output-tokens.js";
 import type { AgentEngine, EngineMessage } from "../agent/engine/types.js";
 import type {
   ActionEntry,
@@ -26,6 +27,7 @@ import type {
 import {
   actionsToEngineTools,
   filterInitialEngineTools,
+  resolveAgentRequestReasoningEffort,
 } from "../agent/production-agent.js";
 import {
   runAgentLoop,
@@ -589,6 +591,11 @@ function createTaskMessageFinalGuard(
       retryMessage: formatQueuedTaskMessages(queuedMessages),
       fallbackMessage:
         "I received an orchestrator update while finishing, but could not continue from it. Please check the task status and send the update again if needed.",
+      // A queued update can introduce a request for an action that was
+      // deferred behind tool-search. The retry is already a corrective turn,
+      // so expose the full authorized registry rather than making the
+      // sub-agent spend that turn rediscovering the same tool.
+      expandToolSurface: true,
     };
   };
 }
@@ -1835,6 +1842,16 @@ export async function processAgentTeamRun(
                   chunkUsage = await runAgentLoop({
                     engine: config.engine,
                     model: config.model,
+                    // Agent-team runs are delegated turns too. Keep their
+                    // first attempt on the same model-aware budget as A2A /
+                    // MCP so reasoning models do not spend the old 4K
+                    // default before emitting a tool call or answer.
+                    maxOutputTokens: resolveMainChatMaxOutputTokens(
+                      config.model,
+                    ),
+                    reasoningEffort: resolveAgentRequestReasoningEffort({
+                      model: config.model,
+                    }),
                     systemPrompt,
                     tools,
                     availableTools,

package/corpus/core/src/server/core-routes-plugin.ts

@@ -1205,36 +1205,6 @@ export function createCoreRoutesPlugin(
         }),
       );
 
-      // Demo-mode status — read by the client fetch interceptor and the
-      // Demo mode settings toggle. `forced` reflects the DEMO_MODE env (a
-      // hosted demo deployment); `enabled` ORs that with the per-user
-      // application_state toggle. No request-context dependency: the env case
-      // needs nothing, and the per-user case resolves the session straight
-      // off the request cookie via getSession(event).
-      getH3App(nitroApp).use(
-        `${P}/demo/status`,
-        defineEventHandler(async (event) => {
-          const { isDemoModeForced } = await import("../demo/config.js");
-          const forced = isDemoModeForced();
-          if (forced) return { enabled: true, forced: true };
-          try {
-            const session = await getSession(event);
-            const email = session?.email;
-            if (!email) return { enabled: false, forced: false };
-            const { appStateGet } =
-              await import("../application-state/store.js");
-            const state = await appStateGet(email, "demo-mode");
-            return {
-              enabled:
-                (state as { enabled?: boolean } | null)?.enabled === true,
-              forced: false,
-            };
-          } catch {
-            return { enabled: false, forced: false };
-          }
-        }),
-      );
-
       // Polling
       getH3App(nitroApp).use(`${P}/poll`, createPollHandler());
 

package/corpus/core/src/server/google-oauth.ts

@@ -17,7 +17,7 @@ import {
   type H3Event,
 } from "h3";
 
-import { getConfiguredAppBasePath } from "./app-base-path.js";
+import { getAppBasePathFromViteEnv } from "./app-base-path.js";
 import { getAppName } from "./app-name.js";
 import { signupAttributionFromCookieHeader } from "./attribution.js";
 import {
@@ -281,7 +281,11 @@ export function getOrigin(event: H3Event): string {
 
 /** App mount prefix, if the template is served under APP_BASE_PATH. */
 export function getAppBasePath(): string {
-  return getConfiguredAppBasePath();
+  // Vite statically replaces VITE_* values in the server bundle during the
+  // build, but Netlify/Nitro does not necessarily expose those build vars at
+  // runtime. Keep auth and OAuth path matching aligned with the SSR handler by
+  // falling back to import.meta.env (including BASE_URL).
+  return getAppBasePathFromViteEnv();
 }
 
 /** Build an absolute same-origin URL that preserves APP_BASE_PATH. */

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

@@ -0,0 +1,67 @@
+---
+name: native-navigation
+description: >-
+  Use when adding or reviewing UI navigation so internal routes preserve
+  normal SPA behavior plus Cmd/Ctrl-click and middle-click new-tab semantics.
+scope: dev
+---
+
+# Native Navigation
+
+## Rule
+
+Pure navigation must render a real React Router `<Link>` for same-SPA routes,
+a native `<a href>` for external/public or explicit new-tab destinations, or a
+shadcn `Button asChild` wrapper around one. Do not use a button whose only job
+is to call `navigate()`, `window.open()`, or `window.location`.
+
+## Why
+
+Browser modifier-click, middle-click, keyboard activation, accessibility, and
+normal client-side routing come from real links. Imperative JavaScript
+navigation hides the destination and blocks those browser semantics.
+
+## How
+
+```tsx
+import { Link } from "react-router";
+
+<Link to={`/items/${item.id}`}>...</Link>
+
+<Button asChild>
+  <Link to="/settings">Settings</Link>
+</Button>
+
+<a href={previewUrl} target="_blank" rel="noopener noreferrer">
+  Preview
+</a>
+```
+
+- Use `Link` for same-SPA internal routes.
+- Use `<a>` when the URL is external, crosses an app/public boundary, is an
+  auth or sign-in destination, or intentionally opens in a new tab.
+- Preserve query strings and hashes in `to` or `href`.
+- For cards with nested actions, link only the non-interactive card region or
+  use a transparent Link overlay; never nest links or buttons.
+- If selection mode changes click behavior, prevent default only for an
+  unmodified primary click and preserve modified clicks.
+
+Keep imperative navigation for post-mutation redirects, OAuth and popup flows,
+downloads, media/blob URLs, playback, keyboard shortcuts, and stateful tabs.
+
+## Review
+
+Search for `onClick={() => navigate`, `window.open`, `window.location`,
+`onAuxClick`, and buttons whose only purpose is routing. For each candidate,
+confirm whether it is pure navigation or a stateful workflow before changing
+it.
+
+Verify the rendered DOM exposes an `href`, then test normal click, Cmd/Ctrl-click,
+middle-click, keyboard Enter, and nested controls where applicable. Run oxfmt
+and focused app tests or typechecks for the touched package.
+
+## Related Skills
+
+- `client-side-routing`
+- `frontend-design`
+- `shadcn-ui`

package/corpus/templates/analytics/.agents/skills/dashboard-management/SKILL.md

@@ -58,6 +58,23 @@ once — do not switch to db-patch or raw SQL.
 
 Do not use `app-db` as a dashboard source. For first-party events collected through `/track`, use `source: "first-party"` or the `query-agent-native-analytics` action rather than raw internal `db-query`.
 
+AI-generated first-party panels are dashboard-time-bound by default. Set
+`config.timeScope` to `"dashboard"` and include the matching dashboard time
+filter in the SQL. The allowed values are:
+
+- `dashboard`: use the dashboard-selected time range; the default for ordinary metrics.
+- `fixed-window`: use an explicit bounded window independent of the dashboard filter.
+- `cohort-history`: use the bounded history of an explicitly defined cohort.
+- `all-time`: scan all available history; use only when the user requests it and
+  put `all-time`, `lifetime`, or `historical` in the title or description.
+
+`{{timeRange}}` requires an explicit matching `filters` entry with
+`id: "timeRange"` and `type: "select"`. `{{<id>Start}}` and `{{<id>End}}`
+require a matching `filters` entry with that id and `type: "date-range"`.
+Do not rely on undeclared time variables. Server validation rejects unbound
+first-party SQL, so declare the filter or choose an explicit non-dashboard
+scope before saving.
+
 ## Creating A Dashboard
 
 When the user asks for a dashboard:
@@ -154,7 +171,8 @@ Notes:
       "source": "first-party",
       "chartType": "metric",
       "width": 1,
-      "sql": "SELECT COUNT(*) AS value FROM analytics_events WHERE event_name = 'click'",
+      "config": { "timeScope": "dashboard" },
+      "sql": "SELECT COUNT(*) AS value FROM analytics_events WHERE event_name = 'click' AND event_date >= '{{dateStart}}' AND event_date < '{{dateEnd}}'",
     },
     {
       "id": "kpi-signups",
@@ -162,7 +180,8 @@ Notes:
       "source": "first-party",
       "chartType": "metric",
       "width": 1,
-      "sql": "SELECT COUNT(*) AS value FROM analytics_events WHERE event_name = 'signup'",
+      "config": { "timeScope": "dashboard" },
+      "sql": "SELECT COUNT(*) AS value FROM analytics_events WHERE event_name = 'signup' AND event_date >= '{{dateStart}}' AND event_date < '{{dateEnd}}'",
     },
     {
       "id": "kpi-active",
@@ -170,7 +189,8 @@ Notes:
       "source": "first-party",
       "chartType": "metric",
       "width": 1,
-      "sql": "SELECT COUNT(DISTINCT user_id) AS value FROM analytics_events",
+      "config": { "timeScope": "dashboard" },
+      "sql": "SELECT COUNT(DISTINCT user_id) AS value FROM analytics_events WHERE event_date >= '{{dateStart}}' AND event_date < '{{dateEnd}}'",
     },
     // Section header switches the grid to 2 columns for the panels below it.
     {
@@ -186,7 +206,8 @@ Notes:
       "source": "first-party",
       "chartType": "line",
       "width": 2,
-      "sql": "SELECT DATE(timestamp) AS date, COUNT(*) AS value FROM analytics_events WHERE timestamp >= '{{dateStart}}' AND timestamp < '{{dateEnd}}' GROUP BY 1 ORDER BY 1",
+      "config": { "timeScope": "dashboard" },
+      "sql": "SELECT event_date AS date, COUNT(*) AS value FROM analytics_events WHERE event_date >= '{{dateStart}}' AND event_date < '{{dateEnd}}' GROUP BY 1 ORDER BY 1",
     },
   ],
 }
@@ -196,6 +217,13 @@ Notes:
 
 `filters[]` defines dashboard-wide controls. Filter values are available in panel SQL through `{{var}}` interpolation. Date ranges emit `{{<id>Start}}` and `{{<id>End}}`.
 
+For dashboard-time-bound first-party SQL, use `config.timeScope: "dashboard"`
+and a predicate that consumes the declared filter, such as
+`event_date >= '{{dateStart}}' AND event_date < '{{dateEnd}}'`. A
+`{{timeRange}}` token must have a matching select filter and SQL branches for
+its options; date variables must have a matching date-range filter. The server
+rejects unbound first-party SQL during dashboard validation.
+
 **Filter ids must be unique.** Two filters with the same `id` collide on the same URL param, so changing one visibly updates the other in the UI. The dashboard save endpoint rejects duplicates with a 400.
 
 **Use `type: "date-range"` for paired start/end dates.** Don't add two `type: "date"` filters labeled "Start" and "End" — even with distinct ids, that ships the wrong UX. A single date-range filter renders as the "from … to …" pair and exposes both halves to SQL via `{{<id>Start}}` / `{{<id>End}}`.
@@ -244,6 +272,17 @@ type DashboardPatch = {
   variables?: Record<string, string>;
 };
 
+type PanelTimeScope =
+  | "dashboard"
+  | "fixed-window"
+  | "cohort-history"
+  | "all-time";
+
+type PanelConfig = Record<string, unknown> & {
+  // Use "dashboard" for AI-generated first-party panels by default.
+  timeScope?: PanelTimeScope;
+};
+
 type PanelPatch = {
   title?: string;
   sql?: string;
@@ -268,7 +307,7 @@ type PanelPatch = {
   width?: number;
   columns?: number;
   tab?: string;
-  config?: Record<string, unknown>;
+  config?: PanelConfig;
   description?: string;
 };
 
@@ -346,7 +385,9 @@ dashboard
     source: "first-party",
     chartType: "metric",
     width: 1,
-    sql: "SELECT COUNT(*) AS value FROM analytics_events",
+    config: { timeScope: "dashboard" },
+    // Assumes filters includes { id: "date", type: "date-range", default: "30d" }.
+    sql: "SELECT COUNT(*) AS value FROM analytics_events WHERE event_date >= '{{dateStart}}' AND event_date < '{{dateEnd}}'",
   })
   .atTop();
 ```
@@ -441,7 +482,7 @@ For a **first-party analytics** dashboard, prefer `compose-dashboard` over hand-
 - **Never hand-author large first-party configs panel-by-panel.** Call `compose-dashboard` with the metric keys instead.
 - Unknown metric keys are skipped and reported in `unknownMetrics` (not fatal). Each panel's SQL is validated independently — valid panels save, invalid ones are reported in `invalidMetrics`.
 - By default (no `overwrite`), composing into an existing dashboard APPENDS the new panels and skips ids already present. `overwrite: true` replaces the whole config.
-- Each metric accepts an optional per-metric `window` of `'30d' | '90d' | 'all'` (only affects windowed virality/time metrics) and `title` / `chartType` / `width` overrides.
+- Each metric accepts an optional per-metric `window` of `'30d' | '90d' | 'all'` (only affects windowed virality/time metrics) and `title` / `chartType` / `width` overrides. Request `'all'` only when the user asks for all-time coverage, and describe it as full available history.
 - Returns `{ dashboardId, panelCount, createdMetrics, unknownMetrics, invalidMetrics, skippedExistingIds }` — report `panelCount` as proof-of-done.
 
 Available metric keys: `total-signups`, `signups-over-time`, `signups-by-template`, `sessions-by-app`, `sessions-over-time`, `replay-sessions`, `replay-chunks-over-time`, `recent-replay-sessions`, `signed-in-vs-anon`, `total-template-clicks`, `total-demo-clicks`, `total-cli-copies`, `template-interest-over-time`, `clicks-by-template`, `demo-clicks-by-template`, `cli-copies-by-template`, `cli-copies-over-time`, `pageviews-over-time`, `top-referrer-domains`, `referred-signups-30d`, `viral-signup-share-30d`, `clip-share-signups-30d`, `signups-by-referral-source`, `referred-signups-over-time`, `top-referrers`, `share-funnel-30d`, `viral-participation-rate-90d`, `viral-coefficient-90d`, `activated-referrers-90d`.

package/corpus/templates/analytics/AGENTS.md

@@ -119,11 +119,11 @@ details live in `.agents/skills/`.
   without raw replay events or storage references. Do not add replay blob or
   dashboard mutation actions to this catalog without an explicit security
   review.
-- While Demo mode is enabled, session and error identities display anonymized
-  (`anonymous@builder.io`), so incident lookups must filter by the stable
+- Demo mode is a browser-local presentation preference. Analytics backend
+  actions, agent/MCP reads, session replays, and error issues always return real
+  authorized identities, so incident lookups should use the actual
   `userId`/email parameter (e.g. `userId: "user@example.com"`) or recording/
-  issue id — never by matching emails read back from previously displayed
-  output.
+  issue id.
 - Analytics keeps its direct MCP surface explicitly curated, so external
   agents should use `ask_app` for multi-step investigation and changes. The
   six incident reads above are bounded, user/org-scoped fallback tools for

package/corpus/templates/analytics/actions/compose-dashboard.ts

@@ -11,6 +11,7 @@ import {
 } from "@agent-native/core/server";
 import { z } from "zod";
 
+import { validateFirstPartyDashboardTimeScope } from "../server/lib/dashboard-time-scope";
 import {
   getDashboard,
   upsertDashboard,
@@ -138,7 +139,7 @@ export default defineAction({
     "If the dashboard already exists and `overwrite` is false (default), the new panels are APPENDED (panels whose id is already present are skipped); with `overwrite: true` the config is replaced. " +
     "Returns { dashboardId, panelCount, createdMetrics, unknownMetrics, invalidMetrics, urlPath, deepLink, message } — use panelCount as proof-of-done. " +
     `Available metric keys: ${METRIC_KEYS.join(", ")}. ` +
-    "Each metric accepts an optional per-metric `window` of '30d' | '90d' | 'all' (only affects windowed virality/time metrics).",
+    "Each metric accepts an optional per-metric `window` of '30d' | '90d' | 'all' (only affects windowed virality/time metrics). Catalog panels are time-scoped by construction; custom first-party SQL added later must use `{{timeRange}}` or declare `config.timeScope`.",
   schema: z.object({
     dashboardId: z
       .string()
@@ -200,6 +201,7 @@ export default defineAction({
     const unknownMetrics: string[] = [];
     const invalidMetrics: Array<{ metric: string; reason: string }> = [];
     const composedPanels: ComposedPanel[] = [];
+    const catalogDashboard = withFirstPartyDashboardFilters({ filters: [] });
 
     for (const req of requests) {
       const panel = buildPanel(req.metric, {
@@ -220,6 +222,15 @@ export default defineAction({
       // rest of the dashboard still builds. (Catalog SQL is known-good, so this
       // is a defensive net, e.g. if a future window/override produces bad SQL.)
       try {
+        const timeScopeError = validateFirstPartyDashboardTimeScope(
+          panel,
+          catalogDashboard,
+          0,
+        );
+        if (timeScopeError) {
+          invalidMetrics.push({ metric: req.metric, reason: timeScopeError });
+          continue;
+        }
         validateFirstPartyAnalyticsSql(panel.sql);
       } catch (e: any) {
         invalidMetrics.push({

package/corpus/templates/analytics/actions/dashboard-mutation-api.ts

@@ -32,6 +32,17 @@ type DashboardPatch = {
   parentId?: string;
 };
 
+type PanelTimeScope =
+  | "dashboard"
+  | "fixed-window"
+  | "cohort-history"
+  | "all-time";
+
+type PanelConfig = Record<string, unknown> & {
+  /** Use "dashboard" for AI-generated first-party panels by default. */
+  timeScope?: PanelTimeScope;
+};
+
 type PanelPatch = {
   title?: string;
   sql?: string;
@@ -40,7 +51,7 @@ type PanelPatch = {
   width?: number;
   columns?: number;
   tab?: string;
-  config?: Record<string, unknown>;
+  config?: PanelConfig;
   description?: string; // shorthand for config.description
 };
 
@@ -112,9 +123,9 @@ export const DASHBOARD_MUTATION_EXAMPLES = [
   'dashboard.panelsMatching({"source":"first-party"}).setWidth(2);',
   'dashboard.panel("retention").setConfigPath("yAxis.format","percent");',
   'dashboard.section("retention-activity-section").append(["repeat-users","retention-over-time"]);',
-  'dashboard.insertPanel({"id":"new-kpi","title":"New KPI","source":"first-party","chartType":"metric","width":1,"sql":"SELECT COUNT(*) AS value FROM analytics_events"}).atTop();',
-  'dashboard.insertPanel({"id":"new-chart","title":"New Chart","source":"first-party","chartType":"line","width":1,"sql":"SELECT date, COUNT(*) AS value FROM analytics_events GROUP BY date ORDER BY date"}).nextTo("retention-over-time");',
-  'dashboard.insertPanel({"id":"row-chart","title":"Row Chart","source":"first-party","chartType":"bar","width":1,"sql":"SELECT name, COUNT(*) AS value FROM analytics_events GROUP BY name"}).atRow(2);',
+  `dashboard.insertPanel({"id":"new-kpi","title":"New KPI","source":"first-party","chartType":"metric","width":1,"config":{"timeScope":"dashboard"},"sql":"SELECT COUNT(*) AS value FROM analytics_events WHERE event_date >= '{{dateStart}}' AND event_date < '{{dateEnd}}'"}).atTop();`,
+  `dashboard.insertPanel({"id":"new-chart","title":"New Chart","source":"first-party","chartType":"line","width":1,"config":{"timeScope":"dashboard"},"sql":"SELECT event_date AS date, COUNT(*) AS value FROM analytics_events WHERE event_date >= '{{dateStart}}' AND event_date < '{{dateEnd}}' GROUP BY event_date ORDER BY event_date"}).nextTo("retention-over-time");`,
+  `dashboard.insertPanel({"id":"row-chart","title":"Row Chart","source":"first-party","chartType":"bar","width":1,"config":{"timeScope":"dashboard"},"sql":"SELECT event_name AS name, COUNT(*) AS value FROM analytics_events WHERE event_date >= '{{dateStart}}' AND event_date < '{{dateEnd}}' GROUP BY event_name"}).atRow(2);`,
   'dashboard.insertPanel({"id":"pipeline-widget","title":"Pipeline Widget","chartType":"extension","width":3,"config":{"extensionId":"<existing-extension-id>"}}).atBottom();',
 ] as const;
 

package/corpus/templates/analytics/actions/mutate-dashboard.ts

@@ -122,6 +122,7 @@ const apiHelp =
   "Subjects: dashboard.set, dashboard.panel, dashboard.panels, dashboard.panelsMatching, dashboard.section, dashboard.insertPanel. " +
   "Selection methods: moveToTop, moveToBottom, moveBefore, moveAfter, moveToIndex, moveNextTo, moveToRow, remove, set, setTitle, setSql, setWidth, setConfig, setConfigPath, duplicate. " +
   "Inserted panels support atTop, atBottom, before, after, atIndex, nextTo, atRow, atRowStart, and atRowEnd. Use nextTo(panelId) or atRow(rowNumber) for visible row placement. " +
+  "AI-generated first-party panels are dashboard-time-bound by default: set config.timeScope to dashboard and include a matching dashboard time filter in SQL. Allowed values are dashboard, fixed-window, cohort-history, and all-time; use all-time only when the user requests full available history and put all-time, lifetime, or historical in the title or description. A {{timeRange}} token requires the timeRange select filter; {{<id>Start}}/{{<id>End}} require a matching date-range filter. Server validation rejects unbound first-party SQL. " +
   `Examples: ${DASHBOARD_MUTATION_EXAMPLES.slice(0, 5).join(" ")}`;
 
 function resolveScope() {
@@ -198,7 +199,7 @@ export default defineAction({
     "Apply general SQL dashboard edits through a small typed mutation API in ONE atomic save. " +
     "Prefer this for dashboard layout and panel edits: move panels by id, edit titles/SQL/width/config, remove panels, duplicate panels, insert panels, or patch dashboard fields. " +
     "For user placement requests like 'second row' or 'next to return rates', use row-aware placement such as `dashboard.insertPanel(...).nextTo(\"retention-over-time\")` or `.atRow(2)`, then verify rendered rows from `get-sql-dashboard.layout.groups`. " +
-    "This is code-shaped but not arbitrary code execution: the server parses the allowed dashboard methods, validates the resulting config with the same invariants as update-dashboard, saves once, syncs collab, and returns compact proof. " +
+    "This is code-shaped but not arbitrary code execution: the server parses the allowed dashboard methods, validates the resulting config with the same invariants as update-dashboard, saves once, syncs collab, and returns compact proof. First-party SQL must be explicitly time-bound as described in the API help; server validation rejects unbound first-party SQL. " +
     "The main code argument is a string, so it avoids brittle JSON-pointer indexes and native-array serialization issues. " +
     `Common example: ${DASHBOARD_MUTATION_EXAMPLES[0]}`,
   schema: z.object({

package/corpus/templates/analytics/actions/update-dashboard.ts

@@ -13,6 +13,7 @@ import { z } from "zod";
 
 import { interpolate } from "../app/pages/adhoc/sql-dashboard/interpolate";
 import { dryRunQuery } from "../server/lib/bigquery";
+import { validateFirstPartyDashboardTimeScope } from "../server/lib/dashboard-time-scope";
 import {
   upsertDashboard,
   upsertDashboardWithRetry,
@@ -421,8 +422,20 @@ export async function validatePanelSql(
       const raw = typeof p.sql === "string" ? p.sql : "";
       if (raw.trim()) {
         try {
+          const timeScopeError = validateFirstPartyDashboardTimeScope(
+            p,
+            config,
+            i,
+          );
+          if (timeScopeError) return timeScopeError;
           validateFirstPartyAnalyticsSql(interpolate(raw, vars));
         } catch (e: any) {
+          if (
+            typeof e?.message === "string" &&
+            e.message.startsWith("panel[")
+          ) {
+            return e.message;
+          }
           return `panel[${i}] "${p.title || p.id}" first-party analytics SQL is invalid: ${e?.message ?? e}`;
         }
       }
@@ -552,6 +565,7 @@ export default defineAction({
     "Use this action when creating a brand-new dashboard from a complete config, for the UI full-config save path, or for an explicitly requested low-level JSON-pointer compatibility edit. " +
     "Do not use `ops` or `panelOrder` for ordinary agent edits like moving charts, adding panels to an existing dashboard, changing widths, or updating panel config; call `mutate-dashboard` once with the full edit script. " +
     "When this action is appropriate, provide only one of `ops`, `panelOrder`, or `config`; `config` replaces the whole dashboard config. " +
+    "First-party event panels must bind to a declared dashboard time filter with `{{timeRange}}` or date-range variables. Intentional fixed-window, cohort-history, and all-time exceptions must be explicit in `panel.config.timeScope`; unbounded first-party SQL is rejected at save time. " +
     "To add a shipped catalog template's panels to an existing dashboard, prefer `install-dashboard-template` with `mergePanels: true` — it appends the template's panels in one call without you having to author each panel. " +
     "The result is compact by default: `panelCount`, `appliedOps`, `panelOrder`, `firstPanelIds`, and `summary`. Set `returnConfig: true` only when you truly need the full config in the tool result. " +
     "The UI auto-refreshes after this action — do NOT call `refresh-screen`.",

package/corpus/templates/analytics/app/assets/replay-cursor.svg

@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="utf-8"?>
+<svg
+  version="1.1"
+  xmlns="http://www.w3.org/2000/svg"
+  viewBox="-0.8 -0.8 22.8 30.4"
+  shape-rendering="geometricPrecision"
+>
+  <path
+    d="M 2.5 1.8 C 2.2 1.5 1.8 1.7 1.8 2.1 V 21.9 C 1.8 22.5 2.5 22.8 2.9 22.4 L 7.4 17.5 L 11.5 26.2 C 11.7 26.7 12.3 26.9 12.8 26.7 L 15.7 25.3 C 16.2 25.1 16.4 24.5 16.2 24 L 12.4 15.4 H 18.4 C 19.1 15.4 19.4 14.5 18.9 14 Z"
+    fill="#000000"
+    stroke="#FFFFFF"
+    stroke-width="4.35"
+    stroke-linecap="round"
+    stroke-linejoin="round"
+    paint-order="stroke fill"
+  />
+</svg>

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

@@ -24,6 +24,7 @@ import {
   type ReactNode,
 } from "react";
 import { createPortal } from "react-dom";
+import { Link } from "react-router";
 import {
   Area,
   AreaChart,
@@ -1579,12 +1580,12 @@ function TableRenderer({
                       {replayHref ? (
                         <span className="inline-flex flex-col gap-0.5">
                           <span>{content}</span>
-                          <a
-                            href={replayHref}
+                          <Link
+                            to={replayHref}
                             className="text-xs font-medium text-primary hover:underline"
                           >
                             {t("sessions.watchReplay")}
-                          </a>
+                          </Link>
                         </span>
                       ) : (
                         content

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

@@ -14,6 +14,7 @@ import {
   IconReportAnalytics,
   IconSearch,
   IconArchive,
+  IconActivity,
   IconHeartbeat,
   IconPin,
   IconPlus,
@@ -26,7 +27,6 @@ import {
   IconPlayerPlay,
   IconLayoutSidebarLeftCollapse,
   IconLayoutSidebarLeftExpand,
-  IconShieldCheck,
 } from "@tabler/icons-react";
 import {
   useQuery,
@@ -97,7 +97,7 @@ import {
   type ChatThreadSummary,
 } from "@agent-native/core/client";
 import { ExtensionsSidebarSection } from "@agent-native/core/client/extensions";
-import { OrgSwitcher, useOrgRole } from "@agent-native/core/client/org";
+import { OrgSwitcher } from "@agent-native/core/client/org";
 
 import {
   AlertDialog,
@@ -1593,7 +1593,6 @@ export function Sidebar({ mobile }: { mobile?: boolean } = {}) {
   const navigate = useNavigate();
   const t = useT();
   const queryClient = useQueryClient();
-  const { canManageOrg } = useOrgRole();
   const { setTheme } = useTheme();
 
   const isAskRoute = location.pathname === "/ask";
@@ -2428,16 +2427,12 @@ export function Sidebar({ mobile }: { mobile?: boolean } = {}) {
       href: "/monitoring",
       active: location.pathname.startsWith("/monitoring"),
     },
-    ...(canManageOrg
-      ? [
-          {
-            icon: IconShieldCheck,
-            label: t("navigation.admin"),
-            href: "/agents?view=dashboards",
-            active: location.pathname.startsWith("/agents"),
-          },
-        ]
-      : []),
+    {
+      icon: IconActivity,
+      label: t("navigation.agents"),
+      href: "/agents",
+      active: location.pathname.startsWith("/agents"),
+    },
     {
       icon: IconDatabase,
       label: t("navigation.dataSources"),
@@ -2641,20 +2636,19 @@ export function Sidebar({ mobile }: { mobile?: boolean } = {}) {
                 {t("navigation.monitoring")}
               </Link>
 
-              {canManageOrg ? (
-                <Link
-                  to="/agents?view=dashboards"
-                  className={cn(
-                    "order-6 flex items-center gap-3 rounded-lg px-3 py-2 transition-colors hover:text-primary",
-                    location.pathname.startsWith("/agents")
-                      ? "bg-sidebar-accent text-sidebar-accent-foreground"
-                      : "text-muted-foreground hover:bg-sidebar-accent/50",
-                  )}
-                >
-                  <IconShieldCheck className="h-4 w-4" />
-                  {t("navigation.admin")}
-                </Link>
-              ) : null}
+              {/* Agents link */}
+              <Link
+                to="/agents"
+                className={cn(
+                  "order-6 flex items-center gap-3 rounded-lg px-3 py-2 transition-colors hover:text-primary",
+                  location.pathname.startsWith("/agents")
+                    ? "bg-sidebar-accent text-sidebar-accent-foreground"
+                    : "text-muted-foreground hover:bg-sidebar-accent/50",
+                )}
+              >
+                <IconActivity className="h-4 w-4" />
+                {t("navigation.agents")}
+              </Link>
 
               {/* Data Sources link */}
               <Link