@agent-native/core 0.120.1 → 0.120.2

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

@@ -0,0 +1,77 @@
+import { useFormatters, useT } from "@agent-native/core/client/i18n";
+import { IconCalendar, IconClock, IconUser } from "@tabler/icons-react";
+
+interface DashboardMetadataProps {
+  createdAt: string | null;
+  createdBy: string | null;
+  updatedAt: string | null;
+  updatedBy: string | null;
+}
+
+function MetadataRow({
+  icon: Icon,
+  label,
+  value,
+}: {
+  icon: typeof IconCalendar;
+  label: string;
+  value: string;
+}) {
+  return (
+    <div className="flex items-start gap-1.5">
+      <Icon className="mt-0.5 h-3 w-3 shrink-0" />
+      <span className="shrink-0">{label}</span>
+      <span className="min-w-0 truncate text-foreground/80">{value}</span>
+    </div>
+  );
+}
+
+export function DashboardMetadata({
+  createdAt,
+  createdBy,
+  updatedAt,
+  updatedBy,
+}: DashboardMetadataProps) {
+  const t = useT();
+  const { formatDate } = useFormatters();
+
+  function formatMetadataDate(value: string | null): string {
+    if (!value) return t("agents.notTracked");
+    try {
+      return formatDate(value, {
+        year: "numeric",
+        month: "short",
+        day: "numeric",
+        hour: "numeric",
+        minute: "2-digit",
+      });
+    } catch {
+      return value;
+    }
+  }
+
+  return (
+    <div className="flex flex-col gap-1.5 text-xs text-muted-foreground">
+      <MetadataRow
+        icon={IconCalendar}
+        label={t("agents.dashboardMetadataCreated")}
+        value={formatMetadataDate(createdAt)}
+      />
+      <MetadataRow
+        icon={IconUser}
+        label={t("agents.dashboardMetadataCreatedBy")}
+        value={createdBy || t("agents.notTracked")}
+      />
+      <MetadataRow
+        icon={IconClock}
+        label={t("agents.dashboardMetadataUpdated")}
+        value={formatMetadataDate(updatedAt)}
+      />
+      <MetadataRow
+        icon={IconUser}
+        label={t("agents.dashboardMetadataUpdatedBy")}
+        value={updatedBy || t("agents.notTracked")}
+      />
+    </div>
+  );
+}

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

@@ -8,6 +8,12 @@ export function DashboardPanelSkeleton({
   ...props
 }: ComponentProps<typeof Skeleton>) {
   return (
-    <Skeleton {...props} className={cn("bg-muted-foreground/20", className)} />
+    <Skeleton
+      {...props}
+      className={cn(
+        "dashboard-panel-skeleton bg-muted-foreground/25",
+        className,
+      )}
+    />
   );
 }

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). " +