@agent-native/core 0.141.5 → 0.141.6

package/corpus/README.md

@@ -31,4 +31,4 @@ rg -n "defineAction|useActionQuery" node_modules/@agent-native/core/corpus
 
 ## Generated Counts
 
-- template files: 7678
+- template files: 7684

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

@@ -28,12 +28,19 @@ does not require a customer warehouse connection.
 Before a large or historical first-party query, call
 `get-first-party-analytics-health`. Keep Neon as the default while its status is
 `healthy` or `monitor`; a `recommend_bigquery` result means the app has observed
-1M+ events, repeated slow queries, or a timeout/30-second query. If BigQuery is
-not configured, use the returned setup link or `data-source-status --key
-bigquery` to guide the user through the existing Data Sources walkthrough. Do
-not silently move the collector: `/track` still lands in first-party Analytics,
-and BigQuery is the opt-in backend for high-volume or historical analysis after
-the user connects it.
+1M+ events, repeated slow queries, or a timeout/30-second query. Treat that
+status as a compatibility name for an external-backend recommendation, not as
+a requirement to use BigQuery. The health result lists the supported options:
+
+- BigQuery for warehouse SQL and complete historical analysis.
+- Amplitude for product analytics, funnels, and retention.
+
+If a suitable backend is not configured, use its returned setup link or
+`data-source-status --key <provider>` to guide the user through the existing
+Data Sources walkthrough. Do not silently move the collector: `/track` still
+lands in first-party Analytics, and connecting a query backend does not
+automatically copy existing Neon events. Use the provider's explicit collection
+or export path before querying that backend.
 
 Example pageviews query for a local calendar day:
 

package/corpus/templates/analytics/actions/get-first-party-analytics-health.ts

@@ -19,6 +19,17 @@ function resolveScope() {
 const healthSchema = z.object({
   status: z.enum(["healthy", "monitor", "recommend_bigquery", "unavailable"]),
   recommendation: z.enum(["none", "connect_bigquery", "use_bigquery"]),
+  externalBackendRecommendation: z.enum(["none", "connect", "use", "unknown"]),
+  externalBackends: z.array(
+    z.object({
+      id: z.enum(["bigquery", "amplitude"]),
+      label: z.string(),
+      role: z.enum(["warehouse", "product-analytics"]),
+      configured: z.boolean().nullable(),
+      missingRequiredKeys: z.array(z.string()),
+      setupLink: z.string(),
+    }),
+  ),
   reasons: z.array(z.enum(["event_volume", "slow_queries", "query_timeout"])),
   observedAt: z.string(),
   metrics: z.object({
@@ -39,6 +50,9 @@ const healthSchema = z.object({
     recommendMaxQueryMs: z.number(),
   }),
   bigQuery: z.object({
+    id: z.literal("bigquery"),
+    label: z.string(),
+    role: z.literal("warehouse"),
     configured: z.boolean().nullable(),
     missingRequiredKeys: z.array(z.string()),
     setupLink: z.string(),
@@ -47,7 +61,7 @@ const healthSchema = z.object({
 
 export default defineAction({
   description:
-    "Check whether the built-in first-party Analytics source is still a good fit for Neon/Postgres. Use this before recommending BigQuery for tracking data. It reads compact daily rollups and the small slow-query pressure ledger, never the raw event table. `healthy` means Neon is fine, `monitor` means keep Neon but watch growth, and `recommend_bigquery` means connect or use BigQuery for high-volume or historical queries. A recommendation is based on 1M+ observed events, three or more slow queries in 24 hours, or any query timeout/30-second query. The result also includes BigQuery credential status and a safe setup link without revealing credential values.",
+    "Check whether the built-in first-party Analytics source is still a good fit for Neon/Postgres. Use this before a large or historical query. It reads compact daily rollups and the small slow-query pressure ledger, never the raw event table. `healthy` means Neon is fine, `monitor` means keep Neon but watch growth, and `recommend_bigquery` means use a configured external analytics backend for high-volume or historical queries. The result reports the two supported external options with safe setup links: BigQuery for warehouse SQL and history, and Amplitude for product analytics, funnels, and retention. A recommendation is based on 1M+ observed events, three or more slow queries in 24 hours, or any query timeout/30-second query. Connecting a backend does not silently reroute `/track` events or backfill existing Neon events.",
   schema: z.object({}),
   outputSchema: healthSchema,
   http: { method: "GET" },

package/corpus/templates/analytics/actions/query-agent-native-analytics.ts

@@ -15,12 +15,12 @@ function resolveScope() {
 
 export default defineAction({
   description:
-    "Query the built-in first-party Analytics source: events recorded through this app's analytics collector endpoint (/track), compact daily rollups, identifiable user-day rollups, and session replay summaries recorded through /api/analytics/replay. This source does not require an external provider connection. Use it for questions about app/site traffic, product events, template/app usage, conversions, session recordings, LLM/agent observability, model cost, token volume, latency, and other first-party data collected by this analytics app. Use source-specific actions such as BigQuery, GA4, Mixpanel, PostHog, or Amplitude when the user asks for those sources or the relevant data lives there. SQL may read analytics_events, analytics_event_daily_rollups, analytics_user_days, and session_recordings; session_replay_chunks is intentionally unavailable, and reads are automatically scoped to the current user/org. Prefer analytics_event_daily_rollups for event counts and analytics_user_days for active-user or retention questions. The rollups are backfilled from existing analytics_events when this schema is upgraded and are updated transactionally with new ingest. Use analytics_events only for bounded recent drill-downs with an explicit event_date or timestamp range. Aggregate, project only needed columns, and add a LIMIT for raw or high-cardinality reads; do not issue an unbounded raw-event scan or paginate a large cohort. An explicit all-time or lifetime request remains all-time, so do not invent a default lower time bound. Safe scoped results are cached for up to five minutes for this agent action. analytics_events columns include event_name, timestamp, event_date, user_id, anonymous_id, user_key, session_id, app, template, signed_in, url, path, hostname, referrer, properties, and context. analytics_event_daily_rollups columns include tenant_key, owner_email, org_id, event_date, event_name, app, template, and event_count. analytics_user_days columns include tenant_key, owner_email, org_id, event_date, and user_key. LLM observability events use event_name = '$ai_generation'; useful properties include $ai_trace_id/run_id, $ai_session_id/thread_id, $ai_model/model, $ai_provider/provider, $ai_input_tokens/input_tokens, $ai_output_tokens/output_tokens, cache_read_tokens, cache_write_tokens, cost_cents_x100, $ai_total_cost_usd/cost_usd, duration_ms/$ai_latency, status, tool_calls, successful_tools, failed_tools, tools, tools_truncated, delegated, delegation_protocol, caller_app, delegation_task_id, a2a_task_id, parent_run_id, parent_turn_id, and error_message/$ai_error. Agent Teams child runs use delegation_protocol = 'agent-team' and retain their own run_id while linking to the launching run through parent_run_id. The bounded tools array contains names, relative start times, durations, statuses, and coarse error classes only, never args or results; failed runs and interrupted tools remain queryable. session_recordings columns include id, session_id, user_id, anonymous_id, user_key, started_at, ended_at, duration_ms, chunk_count, event_count, page_count, error_count, rage_click_count, app, template, status, first_url, last_url, path, hostname, referrer, and metadata.",
+    "Query the built-in first-party Analytics source: events recorded through this app's analytics collector endpoint (/track), compact daily rollups, identifiable user-day rollups, and session replay summaries recorded through /api/analytics/replay. This source does not require an external provider connection. Use it for questions about app/site traffic, product events, template/app usage, conversions, session recordings, LLM/agent observability, model cost, token volume, latency, and other first-party data collected by this analytics app. Use source-specific actions such as BigQuery, GA4, Mixpanel, PostHog, or Amplitude when the user asks for those sources or the relevant data lives there. SQL may read analytics_events, analytics_event_daily_rollups, analytics_user_days, and session_recordings; session_replay_chunks is intentionally unavailable, and reads are automatically scoped to the current user/org. Prefer analytics_event_daily_rollups for event counts and analytics_user_days for active-user or retention questions. The rollups are updated transactionally with new ingest, and a durable scheduled job backfills existing analytics_events after deployment. Until that job completes, use analytics_events only for bounded recent drill-downs with an explicit event_date or timestamp range. Before a large or historical query, call get-first-party-analytics-health and use a configured external backend when it recommends one: BigQuery supports warehouse SQL and historical analysis, while Amplitude supports product analytics, funnels, and retention. Connecting a backend does not automatically reroute /track events or copy existing Neon events, so use that provider's explicit collection or export path before querying it. Aggregate, project only needed columns, and add a LIMIT for raw or high-cardinality reads; do not issue an unbounded raw-event scan or paginate a large cohort. An explicit all-time or lifetime request remains all-time, so do not invent a default lower time bound. Safe scoped results are cached for up to five minutes for this agent action. analytics_events columns include event_name, timestamp, event_date, user_id, anonymous_id, user_key, session_id, app, template, signed_in, url, path, hostname, referrer, properties, and context. analytics_event_daily_rollups columns include tenant_key, owner_email, org_id, event_date, event_name, app, template, and event_count. analytics_user_days columns include tenant_key, owner_email, org_id, event_date, and user_key. LLM observability events use event_name = '$ai_generation'; useful properties include $ai_trace_id/run_id, $ai_session_id/thread_id, $ai_model/model, $ai_provider/provider, $ai_input_tokens/input_tokens, $ai_output_tokens/output_tokens, cache_read_tokens, cache_write_tokens, cost_cents_x100, $ai_total_cost_usd/cost_usd, duration_ms/$ai_latency, status, tool_calls, successful_tools, failed_tools, tools, tools_truncated, delegated, delegation_protocol, caller_app, delegation_task_id, a2a_task_id, parent_run_id, parent_turn_id, and error_message/$ai_error. Agent Teams child runs use delegation_protocol = 'agent-team' and retain their own run_id while linking to the launching run through parent_run_id. The bounded tools array contains names, relative start times, durations, statuses, and coarse error classes only, never args or results; failed runs and interrupted tools remain queryable. session_recordings columns include id, session_id, user_id, anonymous_id, user_key, started_at, ended_at, duration_ms, chunk_count, event_count, page_count, error_count, rage_click_count, app, template, status, first_url, last_url, path, hostname, referrer, and metadata.",
   schema: z.object({
     sql: z
       .string()
       .describe(
-        "Read-only SQL over analytics_events, analytics_event_daily_rollups, analytics_user_days, and session_recordings. Use literal values, not bind placeholders. Prefer the daily rollups for counts, active-user, and retention questions. For raw analytics_events reads, use an explicit event_date or timestamp range, aggregate or project only needed columns, and add a LIMIT; do not issue an unbounded raw-event scan or paginate a large cohort. An explicit all-time or lifetime request remains all-time, so do not invent a default lower time bound. Example: SELECT event_date, event_name, SUM(event_count) AS events FROM analytics_event_daily_rollups WHERE event_date >= '2026-05-01' AND event_date < '2026-06-01' GROUP BY event_date, event_name ORDER BY event_date, events DESC",
+        "Read-only SQL over analytics_events, analytics_event_daily_rollups, analytics_user_days, and session_recordings. Use literal values, not bind placeholders. Prefer the daily rollups for counts, active-user, and retention questions. A durable scheduled job repairs historical rollups after deployment; until it completes, use an explicit event_date or timestamp range for bounded analytics_events reads. Before a large or historical query, call get-first-party-analytics-health and use a configured external backend when recommended: BigQuery for warehouse SQL and complete history, or Amplitude for product analytics, funnels, and retention. Connecting one does not automatically reroute /track events or backfill existing Neon data. Aggregate or project only needed columns and add a LIMIT for raw or high-cardinality reads; do not issue an unbounded raw-event scan or paginate a large cohort. An explicit all-time or lifetime request remains all-time, so do not invent a default lower time bound. Example: SELECT event_date, event_name, SUM(event_count) AS events FROM analytics_event_daily_rollups WHERE event_date >= '2026-05-01' AND event_date < '2026-06-01' GROUP BY event_date, event_name ORDER BY event_date, events DESC",
       ),
   }),
   outputSchema: z.object({

package/corpus/templates/analytics/app/i18n-data.ts

@@ -964,6 +964,23 @@ const enUS = {
     searchPlaceholder: "Search data sources...",
     noMatch: 'No data sources match "{{search}}"',
   },
+  analyticsBackend: {
+    recommendationTitle: "Use an external analytics backend for heavy history",
+    recommendationDescription:
+      "Neon remains the default for recent operational analytics. Connect BigQuery for warehouse SQL and historical analysis, or Amplitude for product analytics, funnels, and retention. Connecting one does not automatically move /track events or backfill existing Neon data.",
+    connectedTitle: "External analytics backends are ready",
+    connectedDescription:
+      "Use BigQuery for warehouse SQL and historical analysis, or Amplitude for product analytics, funnels, and retention. The built-in /track collector continues to write to first-party Analytics unless you explicitly configure another collection path.",
+    options: "External options",
+    monitorDescription:
+      "Neon is still a good fit. Keep an eye on event volume and query latency; this card will suggest an external backend if pressure grows.",
+    healthyDescription:
+      "Neon is a good fit for this first-party data right now. We will suggest BigQuery or Amplitude if volume or query latency grows.",
+    unavailableDescription:
+      "We could not check first-party Analytics pressure right now. Reload and try again before changing backends.",
+    configured: "Configured",
+    setUp: "Set up",
+  },
   panelEditor: {
     chartTypeLine: "Line",
     chartTypeArea: "Area",
@@ -4238,6 +4255,10 @@ function mergeMessages(overrides: {
     common: { ...enUS.common, ...overrides.common },
     dataDictionary: { ...enUS.dataDictionary, ...overrides.dataDictionary },
     dataSources: { ...enUS.dataSources, ...overrides.dataSources },
+    analyticsBackend: {
+      ...enUS.analyticsBackend,
+      ...overrides.analyticsBackend,
+    },
     panelEditor: { ...enUS.panelEditor, ...overrides.panelEditor },
     legacyFusion: { ...enUS.legacyFusion, ...overrides.legacyFusion },
     dashboard: { ...enUS.dashboard, ...overrides.dashboard },
@@ -6326,6 +6347,21 @@ type AnalyticsPartialMessages = {
 
 const translatedAnalyticsDebtTranslations = {
   "zh-CN": {
+    analyticsBackend: {
+      recommendationTitle: "针对大量历史数据使用外部分析后端",
+      recommendationDescription:
+        "Neon 仍是近期运营分析的默认选择。连接 BigQuery 以使用数据仓库 SQL 和历史分析，或连接 Amplitude 进行产品分析、漏斗和留存分析。连接后不会自动迁移 /track 事件或回填现有 Neon 数据。",
+      connectedTitle: "外部分析后端已就绪",
+      connectedDescription:
+        "使用 BigQuery 进行数据仓库 SQL 和历史分析，或使用 Amplitude 进行产品分析、漏斗和留存分析。内置 /track 收集器仍会写入第一方 Analytics，除非你明确配置其他收集路径。",
+      options: "外部选项",
+      monitorDescription:
+        "Neon 目前仍然适合。请关注事件量和查询延迟；如果压力增加，此卡片会建议外部后端。",
+      healthyDescription:
+        "Neon 目前适合这项第一方数据。如果事件量或查询延迟增加，我们会建议 BigQuery 或 Amplitude。",
+      unavailableDescription:
+        "现在无法检查第一方 Analytics 压力。请重新加载后再尝试更换后端。",
+    },
     analyses: {
       allAnalyses: "所有分析",
       backToAnalyses: "返回分析",
@@ -6541,6 +6577,22 @@ const translatedAnalyticsDebtTranslations = {
     },
   },
   "es-ES": {
+    analyticsBackend: {
+      recommendationTitle:
+        "Usa un backend de analítica externo para historiales grandes",
+      recommendationDescription:
+        "Neon sigue siendo el valor predeterminado para la analítica operativa reciente. Conecta BigQuery para SQL de almacén y análisis histórico, o Amplitude para analítica de producto, embudos y retención. Conectar uno no mueve automáticamente los eventos de /track ni rellena los datos existentes de Neon.",
+      connectedTitle: "Los backends de analítica externos están listos",
+      connectedDescription:
+        "Usa BigQuery para SQL de almacén y análisis histórico, o Amplitude para analítica de producto, embudos y retención. El recopilador /track integrado sigue escribiendo en Analytics de primera parte salvo que configures explícitamente otra ruta de recopilación.",
+      options: "Opciones externas",
+      monitorDescription:
+        "Neon sigue siendo adecuado. Vigila el volumen de eventos y la latencia de las consultas; esta tarjeta recomendará un backend externo si aumenta la presión.",
+      healthyDescription:
+        "Neon es adecuado para estos datos de primera parte. Recomendaremos BigQuery o Amplitude si aumentan el volumen o la latencia.",
+      unavailableDescription:
+        "No pudimos comprobar la presión de Analytics de primera parte. Recarga e inténtalo de nuevo antes de cambiar de backend.",
+    },
     analyses: {
       allAnalyses: "Todos los análisis",
       backToAnalyses: "Volver a los análisis",
@@ -6768,6 +6820,22 @@ const translatedAnalyticsDebtTranslations = {
     },
   },
   "fr-FR": {
+    analyticsBackend: {
+      recommendationTitle:
+        "Utilisez un backend analytique externe pour les historiques volumineux",
+      recommendationDescription:
+        "Neon reste la valeur par défaut pour les analyses opérationnelles récentes. Connectez BigQuery pour le SQL d'entrepôt et l'analyse historique, ou Amplitude pour l'analyse produit, les entonnoirs et la rétention. La connexion ne déplace pas automatiquement les événements /track et ne remplit pas les données Neon existantes.",
+      connectedTitle: "Les backends analytiques externes sont prêts",
+      connectedDescription:
+        "Utilisez BigQuery pour le SQL d'entrepôt et l'analyse historique, ou Amplitude pour l'analyse produit, les entonnoirs et la rétention. Le collecteur /track intégré continue d'écrire dans Analytics propriétaire, sauf si vous configurez explicitement un autre chemin de collecte.",
+      options: "Options externes",
+      monitorDescription:
+        "Neon reste adapté. Surveillez le volume d'événements et la latence des requêtes ; cette carte recommandera un backend externe si la pression augmente.",
+      healthyDescription:
+        "Neon convient actuellement à ces données propriétaires. Nous recommanderons BigQuery ou Amplitude si le volume ou la latence augmente.",
+      unavailableDescription:
+        "Impossible de vérifier la pression d'Analytics propriétaire. Rechargez la page et réessayez avant de changer de backend.",
+    },
     analyses: {
       allAnalyses: "Toutes les analyses",
       backToAnalyses: "Retour aux analyses",
@@ -6999,6 +7067,22 @@ const translatedAnalyticsDebtTranslations = {
     },
   },
   "de-DE": {
+    analyticsBackend: {
+      recommendationTitle:
+        "Verwende ein externes Analyse-Backend für große historische Datenmengen",
+      recommendationDescription:
+        "Neon bleibt die Standardeinstellung für aktuelle operative Analysen. Verbinde BigQuery für Warehouse-SQL und historische Analysen oder Amplitude für Produktanalysen, Funnels und Retention. Durch die Verbindung werden /track-Ereignisse nicht automatisch verschoben und vorhandene Neon-Daten nicht nachgefüllt.",
+      connectedTitle: "Externe Analyse-Backends sind bereit",
+      connectedDescription:
+        "Verwende BigQuery für Warehouse-SQL und historische Analysen oder Amplitude für Produktanalysen, Funnels und Retention. Der integrierte /track-Collector schreibt weiterhin in First-Party Analytics, sofern du nicht ausdrücklich einen anderen Erfassungspfad konfigurierst.",
+      options: "Externe Optionen",
+      monitorDescription:
+        "Neon passt weiterhin gut. Behalte Ereignisvolumen und Abfrage-Latenz im Blick; diese Karte empfiehlt bei wachsender Belastung ein externes Backend.",
+      healthyDescription:
+        "Neon passt derzeit zu diesen First-Party-Daten. Bei wachsendem Volumen oder wachsender Latenz empfehlen wir BigQuery oder Amplitude.",
+      unavailableDescription:
+        "Die First-Party-Analytics-Belastung konnte nicht geprüft werden. Lade neu und versuche es erneut, bevor du das Backend wechselst.",
+    },
     analyses: {
       allAnalyses: "Alle Analysen",
       backToAnalyses: "Zurück zu den Analysen",
@@ -7228,6 +7312,21 @@ const translatedAnalyticsDebtTranslations = {
     },
   },
   "ja-JP": {
+    analyticsBackend: {
+      recommendationTitle: "大量の履歴データには外部分析バックエンドを使用",
+      recommendationDescription:
+        "Neon は最近の運用分析のデフォルトです。BigQuery を接続するとデータウェアハウス SQL と履歴分析を、Amplitude を接続するとプロダクト分析、ファネル、リテンション分析を利用できます。接続しても /track イベントが自動的に移行されたり、既存の Neon データが補完されたりすることはありません。",
+      connectedTitle: "外部分析バックエンドを利用できます",
+      connectedDescription:
+        "BigQuery はデータウェアハウス SQL と履歴分析に、Amplitude はプロダクト分析、ファネル、リテンション分析に使用します。明示的に別の収集経路を設定しない限り、組み込みの /track コレクターは First-party Analytics に書き込み続けます。",
+      options: "外部オプション",
+      monitorDescription:
+        "現在も Neon で問題ありません。イベント量とクエリ遅延を確認してください。負荷が増えると、このカードが外部バックエンドを提案します。",
+      healthyDescription:
+        "現在、この First-party データには Neon が適しています。量やクエリ遅延が増えると BigQuery または Amplitude を提案します。",
+      unavailableDescription:
+        "First-party Analytics の負荷を確認できませんでした。バックエンドを変更する前に再読み込みしてもう一度お試しください。",
+    },
     analyses: {
       allAnalyses: "すべての分析",
       backToAnalyses: "分析に戻る",
@@ -7453,6 +7552,21 @@ const translatedAnalyticsDebtTranslations = {
     },
   },
   "ko-KR": {
+    analyticsBackend: {
+      recommendationTitle: "대규모 기록 데이터에는 외부 분석 백엔드 사용",
+      recommendationDescription:
+        "Neon은 최근 운영 분석의 기본값입니다. 웨어하우스 SQL과 기록 분석에는 BigQuery를, 제품 분석과 퍼널 및 리텐션에는 Amplitude를 연결하세요. 연결해도 /track 이벤트가 자동으로 이동하거나 기존 Neon 데이터가 백필되지는 않습니다.",
+      connectedTitle: "외부 분석 백엔드를 사용할 수 있습니다",
+      connectedDescription:
+        "BigQuery는 웨어하우스 SQL과 기록 분석에, Amplitude는 제품 분석과 퍼널 및 리텐션에 사용하세요. 다른 수집 경로를 명시적으로 설정하지 않는 한 내장 /track 수집기는 계속 First-party Analytics에 기록합니다.",
+      options: "외부 옵션",
+      monitorDescription:
+        "현재도 Neon이 적합합니다. 이벤트 양과 쿼리 지연을 확인하세요. 부하가 커지면 이 카드에서 외부 백엔드를 추천합니다.",
+      healthyDescription:
+        "현재 이 First-party 데이터에는 Neon이 적합합니다. 양이나 쿼리 지연이 늘면 BigQuery 또는 Amplitude를 추천합니다.",
+      unavailableDescription:
+        "현재 First-party Analytics 부하를 확인할 수 없습니다. 백엔드를 변경하기 전에 다시 로드해 보세요.",
+    },
     analyses: {
       allAnalyses: "모든 분석",
       backToAnalyses: "분석으로 돌아가기",
@@ -7676,6 +7790,22 @@ const translatedAnalyticsDebtTranslations = {
     },
   },
   "pt-BR": {
+    analyticsBackend: {
+      recommendationTitle:
+        "Use um backend de análise externo para históricos grandes",
+      recommendationDescription:
+        "Neon continua sendo o padrão para análises operacionais recentes. Conecte o BigQuery para SQL de warehouse e análise histórica, ou o Amplitude para análise de produto, funis e retenção. Conectar um deles não move eventos de /track automaticamente nem preenche dados existentes do Neon.",
+      connectedTitle: "Os backends de análise externos estão prontos",
+      connectedDescription:
+        "Use o BigQuery para SQL de warehouse e análise histórica, ou o Amplitude para análise de produto, funis e retenção. O coletor /track integrado continua gravando no Analytics próprio, a menos que você configure explicitamente outro caminho de coleta.",
+      options: "Opções externas",
+      monitorDescription:
+        "O Neon ainda é adequado. Acompanhe o volume de eventos e a latência das consultas; este cartão recomendará um backend externo se a pressão aumentar.",
+      healthyDescription:
+        "O Neon é adequado para estes dados próprios no momento. Recomendaremos BigQuery ou Amplitude se o volume ou a latência aumentarem.",
+      unavailableDescription:
+        "Não foi possível verificar a pressão do Analytics próprio. Recarregue e tente novamente antes de trocar de backend.",
+    },
     analyses: {
       allAnalyses: "Todas as análises",
       backToAnalyses: "Voltar às análises",
@@ -7904,6 +8034,22 @@ const translatedAnalyticsDebtTranslations = {
     },
   },
   "hi-IN": {
+    analyticsBackend: {
+      recommendationTitle:
+        "बड़े ऐतिहासिक डेटा के लिए बाहरी Analytics backend इस्तेमाल करें",
+      recommendationDescription:
+        "हाल के ऑपरेशनल Analytics के लिए Neon अभी भी डिफ़ॉल्ट है। Warehouse SQL और ऐतिहासिक विश्लेषण के लिए BigQuery, या product analytics, funnels और retention के लिए Amplitude कनेक्ट करें। कनेक्ट करने से /track इवेंट अपने-आप नहीं जाते और Neon का मौजूदा डेटा backfill नहीं होता।",
+      connectedTitle: "बाहरी Analytics backends तैयार हैं",
+      connectedDescription:
+        "Warehouse SQL और ऐतिहासिक विश्लेषण के लिए BigQuery, या product analytics, funnels और retention के लिए Amplitude इस्तेमाल करें। अलग collection path स्पष्ट रूप से कॉन्फ़िगर न करने तक built-in /track collector first-party Analytics में लिखता रहेगा।",
+      options: "बाहरी विकल्प",
+      monitorDescription:
+        "Neon अभी भी उपयुक्त है। Event volume और query latency पर नज़र रखें; दबाव बढ़ने पर यह कार्ड बाहरी backend सुझाएगा।",
+      healthyDescription:
+        "इस first-party डेटा के लिए Neon अभी उपयुक्त है। Volume या query latency बढ़ने पर हम BigQuery या Amplitude सुझाएंगे।",
+      unavailableDescription:
+        "First-party Analytics pressure जाँचा नहीं जा सका। Backend बदलने से पहले reload करके फिर प्रयास करें।",
+    },
     analyses: {
       allAnalyses: "सभी विश्लेषण",
       backToAnalyses: "विश्लेषण पर वापस जाएँ",
@@ -8127,6 +8273,21 @@ const translatedAnalyticsDebtTranslations = {
     },
   },
   "ar-SA": {
+    analyticsBackend: {
+      recommendationTitle: "استخدم واجهة تحليلات خارجية للسجل التاريخي الكبير",
+      recommendationDescription:
+        "يظل Neon الخيار الافتراضي للتحليلات التشغيلية الحديثة. صِل BigQuery لاستخدام SQL المستودع والتحليل التاريخي، أو Amplitude لتحليلات المنتج ومسارات التحويل والاحتفاظ. لا يؤدي الاتصال بأحدهما إلى نقل أحداث /track تلقائياً أو ملء بيانات Neon الحالية.",
+      connectedTitle: "واجهات التحليلات الخارجية جاهزة",
+      connectedDescription:
+        "استخدم BigQuery لـ SQL المستودع والتحليل التاريخي، أو Amplitude لتحليلات المنتج ومسارات التحويل والاحتفاظ. يستمر جامع /track المضمّن في الكتابة إلى Analytics للطرف الأول ما لم تضبط مسار جمع آخر صراحةً.",
+      options: "الخيارات الخارجية",
+      monitorDescription:
+        "لا يزال Neon مناسباً. راقب حجم الأحداث وزمن الاستعلام؛ ستقترح هذه البطاقة واجهة خارجية إذا زاد الضغط.",
+      healthyDescription:
+        "Neon مناسب حالياً لبيانات Analytics للطرف الأول. سنقترح BigQuery أو Amplitude إذا زاد الحجم أو زمن الاستعلام.",
+      unavailableDescription:
+        "تعذّر التحقق من ضغط Analytics للطرف الأول. أعد التحميل وحاول مرة أخرى قبل تغيير الواجهة الخلفية.",
+    },
     analyses: {
       allAnalyses: "جميع التحليلات",
       backToAnalyses: "العودة إلى التحليلات",
@@ -8350,6 +8511,173 @@ const translatedAnalyticsDebtTranslations = {
   },
 } satisfies Partial<Record<LocaleCode, AnalyticsPartialMessages>>;
 
+const analyticsBackendTranslations: Partial<
+  Record<LocaleCode, Partial<Messages["analyticsBackend"]>>
+> = {
+  "zh-TW": {
+    recommendationTitle: "大量歷史資料請使用外部分析後端",
+    recommendationDescription:
+      "Neon 仍是近期營運分析的預設選項。連接 BigQuery 以使用資料倉儲 SQL 和歷史分析，或連接 Amplitude 以進行產品分析、漏斗和留存分析。連接後不會自動移轉 /track 事件或回填現有的 Neon 資料。",
+    connectedTitle: "外部分析後端已就緒",
+    connectedDescription:
+      "使用 BigQuery 進行資料倉儲 SQL 和歷史分析，或使用 Amplitude 進行產品分析、漏斗和留存分析。內建的 /track 收集器仍會寫入第一方 Analytics，除非你明確設定其他收集路徑。",
+    options: "外部選項",
+    monitorDescription:
+      "Neon 目前仍然適用。請留意事件量和查詢延遲；壓力增加時，這張卡片會建議外部後端。",
+    healthyDescription:
+      "Neon 目前很適合這些第一方資料。當資料量或查詢延遲增加時，我們會建議 BigQuery 或 Amplitude。",
+    unavailableDescription:
+      "目前無法檢查第一方 Analytics 壓力。請重新載入後再決定是否更換後端。",
+  },
+  "zh-CN": {
+    recommendationTitle: "大量历史数据请使用外部分析后端",
+    recommendationDescription:
+      "Neon 仍是近期运营分析的默认选项。连接 BigQuery 以使用数据仓库 SQL 和历史分析，或连接 Amplitude 以进行产品分析、漏斗和留存分析。连接后不会自动转移 /track 事件或回填现有 Neon 数据。",
+    connectedTitle: "外部分析后端已就绪",
+    connectedDescription:
+      "使用 BigQuery 进行数据仓库 SQL 和历史分析，或使用 Amplitude 进行产品分析、漏斗和留存分析。内置的 /track 收集器仍会写入第一方 Analytics，除非你明确配置其他收集路径。",
+    options: "外部选项",
+    monitorDescription:
+      "Neon 目前仍然适用。请留意事件量和查询延迟；压力增加时，这张卡片会建议外部后端。",
+    healthyDescription:
+      "Neon 目前很适合这些第一方数据。当数据量或查询延迟增加时，我们会建议 BigQuery 或 Amplitude。",
+    unavailableDescription:
+      "目前无法检查第一方 Analytics 压力。请重新加载后再决定是否更换后端。",
+  },
+  "ar-SA": {
+    recommendationTitle: "استخدم خلفية تحليلات خارجية للتاريخ الكبير",
+    recommendationDescription:
+      "يظل Neon الخيار الافتراضي للتحليلات التشغيلية الحديثة. وصّل BigQuery لبيانات المستودع والتحليل التاريخي، أو Amplitude لتحليلات المنتج والقمع والاحتفاظ. لا يؤدي الاتصال إلى نقل أحداث /track أو ملء بيانات Neon الحالية تلقائيًا.",
+    connectedTitle: "الخلفيات التحليلية الخارجية جاهزة",
+    connectedDescription:
+      "استخدم BigQuery لتحليل SQL التاريخي وبيانات المستودع، أو Amplitude لتحليلات المنتج والقمع والاحتفاظ. يواصل جامع /track المدمج الكتابة إلى Analytics التابعة لنا ما لم تضبط مسار جمع آخر صراحةً.",
+    options: "خيارات خارجية",
+    monitorDescription:
+      "لا يزال Neon مناسبًا. راقب حجم الأحداث وزمن الاستعلام؛ ستقترح هذه البطاقة خلفية خارجية عند زيادة الضغط.",
+    healthyDescription:
+      "Neon مناسب حاليًا لهذه البيانات التابعة لنا. سنقترح BigQuery أو Amplitude إذا زاد الحجم أو زمن الاستعلام.",
+    unavailableDescription:
+      "تعذر فحص ضغط Analytics التابعة لنا الآن. أعد التحميل قبل تغيير الخلفيات.",
+  },
+  "de-DE": {
+    recommendationTitle:
+      "Für umfangreiche historische Daten ein externes Analyse-Backend nutzen",
+    recommendationDescription:
+      "Neon bleibt die Standardeinstellung für aktuelle Betriebsanalysen. Verbinde BigQuery für Warehouse-SQL und historische Analysen oder Amplitude für Produktanalysen, Funnels und Retention. Durch die Verbindung werden /track-Ereignisse nicht automatisch verschoben oder vorhandene Neon-Daten nachgeladen.",
+    connectedTitle: "Externe Analyse-Backends sind bereit",
+    connectedDescription:
+      "Nutze BigQuery für Warehouse-SQL und historische Analysen oder Amplitude für Produktanalysen, Funnels und Retention. Der integrierte /track-Sammler schreibt weiterhin in First-Party-Analytics, sofern du keinen anderen Sammelpfad festlegst.",
+    options: "Externe Optionen",
+    monitorDescription:
+      "Neon passt weiterhin gut. Behalte Ereignismenge und Abfragezeit im Blick; diese Karte schlägt bei wachsender Belastung ein externes Backend vor.",
+    healthyDescription:
+      "Neon eignet sich derzeit gut für diese First-Party-Daten. Bei wachsender Menge oder Abfragezeit schlagen wir BigQuery oder Amplitude vor.",
+    unavailableDescription:
+      "Der Druck auf First-Party-Analytics konnte nicht geprüft werden. Lade neu, bevor du Backends änderst.",
+  },
+  "es-ES": {
+    recommendationTitle:
+      "Usa un backend de analítica externo para historiales grandes",
+    recommendationDescription:
+      "Neon sigue siendo la opción predeterminada para la analítica operativa reciente. Conecta BigQuery para SQL de almacén e históricos, o Amplitude para analítica de producto, embudos y retención. La conexión no mueve automáticamente los eventos de /track ni completa los datos existentes de Neon.",
+    connectedTitle: "Los backends de analítica externos están listos",
+    connectedDescription:
+      "Usa BigQuery para SQL de almacén e históricos, o Amplitude para analítica de producto, embudos y retención. El recolector /track integrado sigue escribiendo en Analytics de primera parte salvo que configures otra ruta de recopilación.",
+    options: "Opciones externas",
+    monitorDescription:
+      "Neon sigue siendo adecuado. Vigila el volumen de eventos y la latencia de las consultas; esta tarjeta sugerirá un backend externo si aumenta la presión.",
+    healthyDescription:
+      "Neon es adecuado para estos datos de primera parte. Sugeriremos BigQuery o Amplitude si crecen el volumen o la latencia.",
+    unavailableDescription:
+      "No se pudo comprobar la presión de Analytics de primera parte. Recarga antes de cambiar de backend.",
+  },
+  "fr-FR": {
+    recommendationTitle:
+      "Utiliser un backend analytique externe pour les historiques volumineux",
+    recommendationDescription:
+      "Neon reste la solution par défaut pour les analyses opérationnelles récentes. Connectez BigQuery pour le SQL d'entrepôt et l'historique, ou Amplitude pour les analyses produit, les tunnels et la rétention. La connexion ne déplace pas automatiquement les événements /track et ne complète pas les données Neon existantes.",
+    connectedTitle: "Les backends analytiques externes sont prêts",
+    connectedDescription:
+      "Utilisez BigQuery pour le SQL d'entrepôt et l'historique, ou Amplitude pour les analyses produit, les tunnels et la rétention. Le collecteur /track intégré continue d'écrire dans Analytics first-party, sauf si vous configurez explicitement un autre chemin de collecte.",
+    options: "Options externes",
+    monitorDescription:
+      "Neon reste adapté. Surveillez le volume d'événements et la latence des requêtes ; cette carte suggérera un backend externe si la pression augmente.",
+    healthyDescription:
+      "Neon convient actuellement à ces données first-party. Nous suggérerons BigQuery ou Amplitude si le volume ou la latence augmente.",
+    unavailableDescription:
+      "Impossible de vérifier la pression Analytics first-party. Rechargez avant de changer de backend.",
+  },
+  "hi-IN": {
+    recommendationTitle:
+      "भारी ऐतिहासिक डेटा के लिए बाहरी Analytics बैकएंड उपयोग करें",
+    recommendationDescription:
+      "हाल के ऑपरेशनल Analytics के लिए Neon अभी भी डिफ़ॉल्ट है। वेयरहाउस SQL और ऐतिहासिक विश्लेषण के लिए BigQuery, या प्रोडक्ट Analytics, फ़नल और रिटेंशन के लिए Amplitude कनेक्ट करें। कनेक्शन /track इवेंट को अपने-आप स्थानांतरित या मौजूदा Neon डेटा को बैकफ़िल नहीं करता।",
+    connectedTitle: "बाहरी Analytics बैकएंड तैयार हैं",
+    connectedDescription:
+      "वेयरहाउस SQL और ऐतिहासिक विश्लेषण के लिए BigQuery, या प्रोडक्ट Analytics, फ़नल और रिटेंशन के लिए Amplitude उपयोग करें। अंतर्निहित /track कलेक्टर First-Party Analytics में लिखता रहेगा, जब तक आप कोई दूसरा कलेक्शन पथ स्पष्ट रूप से कॉन्फ़िगर न करें।",
+    options: "बाहरी विकल्प",
+    monitorDescription:
+      "Neon अभी भी उपयुक्त है। इवेंट वॉल्यूम और क्वेरी लेटेंसी पर नज़र रखें; दबाव बढ़ने पर यह कार्ड बाहरी बैकएंड सुझाएगा।",
+    healthyDescription:
+      "Neon अभी इन First-Party डेटा के लिए अच्छा है। वॉल्यूम या क्वेरी लेटेंसी बढ़ने पर हम BigQuery या Amplitude सुझाएंगे।",
+    unavailableDescription:
+      "अभी First-Party Analytics दबाव की जाँच नहीं हो सकी। बैकएंड बदलने से पहले फिर लोड करें।",
+  },
+  "ja-JP": {
+    recommendationTitle: "大量の履歴データには外部分析バックエンドを使用",
+    recommendationDescription:
+      "Neon は最近の運用分析の既定値です。ウェアハウス SQL と履歴分析には BigQuery、プロダクト分析、ファネル、リテンションには Amplitude を接続してください。接続しても /track イベントが自動的に移行されたり、既存の Neon データがバックフィルされたりすることはありません。",
+    connectedTitle: "外部分析バックエンドを利用できます",
+    connectedDescription:
+      "ウェアハウス SQL と履歴分析には BigQuery、プロダクト分析、ファネル、リテンションには Amplitude を使用できます。別の収集経路を明示的に設定しない限り、組み込みの /track コレクターは First-Party Analytics への書き込みを続けます。",
+    options: "外部オプション",
+    monitorDescription:
+      "Neon は引き続き適しています。イベント量とクエリ遅延を確認してください。負荷が増えると、このカードが外部バックエンドを提案します。",
+    healthyDescription:
+      "Neon は現在この First-Party データに適しています。量やクエリ遅延が増えると BigQuery または Amplitude を提案します。",
+    unavailableDescription:
+      "現在 First-Party Analytics の負荷を確認できませんでした。バックエンドを変更する前に再読み込みしてください。",
+  },
+  "ko-KR": {
+    recommendationTitle: "대규모 기록 데이터에는 외부 분석 백엔드 사용",
+    recommendationDescription:
+      "Neon은 최근 운영 분석의 기본값입니다. 웨어하우스 SQL 및 기록 분석에는 BigQuery를, 제품 분석과 퍼널 및 리텐션에는 Amplitude를 연결하세요. 연결해도 /track 이벤트가 자동으로 이동하거나 기존 Neon 데이터가 백필되지는 않습니다.",
+    connectedTitle: "외부 분석 백엔드를 사용할 수 있습니다",
+    connectedDescription:
+      "웨어하우스 SQL 및 기록 분석에는 BigQuery를, 제품 분석과 퍼널 및 리텐션에는 Amplitude를 사용하세요. 다른 수집 경로를 명시적으로 설정하지 않는 한 기본 /track 수집기는 계속 First-Party Analytics에 기록합니다.",
+    options: "외부 옵션",
+    monitorDescription:
+      "Neon은 아직 적합합니다. 이벤트 규모와 쿼리 지연 시간을 확인하세요. 부하가 커지면 이 카드가 외부 백엔드를 제안합니다.",
+    healthyDescription:
+      "Neon은 현재 이 First-Party 데이터에 적합합니다. 규모나 쿼리 지연이 증가하면 BigQuery 또는 Amplitude를 제안합니다.",
+    unavailableDescription:
+      "지금은 First-Party Analytics 부하를 확인할 수 없습니다. 백엔드를 변경하기 전에 다시 로드하세요.",
+  },
+  "pt-BR": {
+    recommendationTitle:
+      "Use um backend de análise externo para históricos grandes",
+    recommendationDescription:
+      "Neon continua sendo o padrão para análises operacionais recentes. Conecte o BigQuery para SQL de warehouse e análises históricas, ou o Amplitude para análise de produto, funis e retenção. A conexão não move automaticamente eventos de /track nem preenche dados existentes do Neon.",
+    connectedTitle: "Os backends de análise externos estão prontos",
+    connectedDescription:
+      "Use o BigQuery para SQL de warehouse e análises históricas, ou o Amplitude para análise de produto, funis e retenção. O coletor /track integrado continua gravando no Analytics de primeira parte, a menos que você configure explicitamente outro caminho de coleta.",
+    options: "Opções externas",
+    monitorDescription:
+      "Neon continua adequado. Acompanhe o volume de eventos e a latência das consultas; este cartão sugerirá um backend externo se a pressão crescer.",
+    healthyDescription:
+      "Neon é adequado para estes dados de primeira parte agora. Sugeriremos BigQuery ou Amplitude se o volume ou a latência crescer.",
+    unavailableDescription:
+      "Não foi possível verificar a pressão do Analytics de primeira parte. Recarregue antes de trocar de backend.",
+  },
+};
+
+for (const [locale, section] of Object.entries(
+  analyticsBackendTranslations,
+) as Array<[LocaleCode, Partial<Messages["analyticsBackend"]>]>) {
+  const messages = messagesByLocale[locale];
+  if (messages) Object.assign(messages.analyticsBackend, section);
+}
+
 for (const [locale, overrides] of Object.entries(
   translatedAnalyticsDebtTranslations,
 ) as Array<[LocaleCode, AnalyticsPartialMessages]>) {