@agent-native/core 0.120.1 → 0.120.3

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

@@ -2,6 +2,7 @@ import {
   AgentSidebar,
   GuidedQuestionFlow,
   focusAgentChat,
+  isAgentChatHomeHandoffActive,
   markAgentChatHomeHandoff,
   navigateWithAgentChatViewTransition,
   useAgentChatHomeHandoff,
@@ -19,6 +20,7 @@ import {
   ANALYTICS_CHAT_STORAGE_KEY,
   markAnalyticsChatActivity,
 } from "@/lib/chat-handoff";
+import { isDashboardReportScreenshot } from "@/lib/dashboard-report-capture";
 import { TAB_ID } from "@/lib/tab-id";
 
 import { Header } from "./Header";
@@ -33,12 +35,30 @@ interface LayoutProps {
 const BARE_ROUTES = new Set(["/chart"]);
 
 export function Layout({ children }: LayoutProps) {
+  const location = useLocation();
+
+  if (isDashboardReportScreenshot(location.search)) {
+    return <DashboardReportLayout>{children}</DashboardReportLayout>;
+  }
+
+  return <InteractiveLayout>{children}</InteractiveLayout>;
+}
+
+function DashboardReportLayout({ children }: LayoutProps) {
+  return (
+    <HeaderActionsProvider>
+      <main className="agent-native-app-main min-h-screen bg-background p-6 text-foreground md:p-8">
+        {children}
+      </main>
+    </HeaderActionsProvider>
+  );
+}
+
+function InteractiveLayout({ children }: LayoutProps) {
   useNavigationState();
   const location = useLocation();
   const navigate = useNavigate();
   const t = useT();
-  const reportScreenshot =
-    new URLSearchParams(location.search).get("reportScreenshot") === "1";
 
   // Analytics stages the active primary resource as composer context —
   // dashboards (`/dashboards/:id`, legacy `/adhoc/:id`) and ad-hoc analyses
@@ -102,12 +122,15 @@ export function Layout({ children }: LayoutProps) {
   const chatHomeHandoffActive = useAgentChatHomeHandoff({
     storageKey: ANALYTICS_CHAT_STORAGE_KEY,
     activePath: location.pathname,
-    enabled: !isAskRoute && !reportScreenshot,
+    enabled: !isAskRoute,
   });
+  const chatHomeHandoffPending = isAgentChatHomeHandoffActive(
+    ANALYTICS_CHAT_STORAGE_KEY,
+  );
   useAgentChatHomeHandoffLinks({
     storageKey: ANALYTICS_CHAT_STORAGE_KEY,
     chatPath: "/ask",
-    enabled: !reportScreenshot,
+    enabled: true,
     requireActiveHandoff: true,
   });
   useEffect(() => {
@@ -135,16 +158,6 @@ export function Layout({ children }: LayoutProps) {
     return <>{children}</>;
   }
 
-  if (reportScreenshot) {
-    return (
-      <HeaderActionsProvider>
-        <main className="agent-native-app-main min-h-screen bg-background p-6 text-foreground md:p-8">
-          {children}
-        </main>
-      </HeaderActionsProvider>
-    );
-  }
-
   const contentFrame = (
     <div className="flex h-full flex-1 flex-col overflow-hidden">
       <MobileNav showNewChat={isAskRoute} />
@@ -195,6 +208,7 @@ export function Layout({ children }: LayoutProps) {
             position="right"
             defaultOpen={false}
             chatViewTransition
+            chatViewTransitionHandoff={chatHomeHandoffPending}
             storageKey={ANALYTICS_CHAT_STORAGE_KEY}
             browserTabId={TAB_ID}
             openOnChatRunning={chatHomeHandoffActive}

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

@@ -12,6 +12,7 @@ import {
 
 const DASHBOARD_CONTEXT =
   "The user wants to create a new analytics dashboard. " +
+  'DASHBOARD ARTIFACT RULE — Dashboards are the only user-facing Analytics artifact. For deep dives, saved reports, custom visualizations, or bespoke workflows, always create or update a dashboard. If bespoke UI is needed, create the extension and immediately add it as one or more `chartType: "extension"` panels in that dashboard; never leave the extension standalone or direct the user to an Extensions page. ' +
   "TEMPLATE FIRST — If the user names an existing dashboard as a template to clone/base this on, resolve its id first (use `list-sql-dashboards` if you only have a title), then call `get-sql-dashboard` with `includeConfig: true` immediately and inspect `panels[].chartType`. " +
   'If any panel is `chartType: "extension"`, this is an extension-backed dashboard: call `get-extension` for that panel\'s `config.extensionId`, clone/adapt it with `create-extension` (apply the requested customer/org filters), then save a new dashboard via `update-dashboard` that embeds the new extension panel (`chartType: "extension"`, `config.extensionId`). Do not rebuild an extension template as guessed SQL/BigQuery panels. ' +
   "LARGE EXTENSION CLONE — Extension bodies can be very large (tens of thousands of characters). Call `get-extension` with `forceContent: true` exactly ONCE and reuse that body; a second same-run read intentionally omits `content` (you'll see `contentOmitted`), so don't treat that as the content being gone. Call `create-extension` / `update-extension` as NATIVE tools — they are mutating actions and cannot be invoked from `run-code`/`appAction`. For customer-specific clones, change only the small static config block (e.g. `ACCOUNT_USAGE_STATIC`) and prefer a focused `update-extension` edit over regenerating the whole HTML. Never shovel the full body through `run-code` or chat; if you stage it in a workspace scratch file, read it back with `workspaceRead` (which returns the whole file). " +