@agent-native/core-corpus 0.199.0-nightly-20261001153605 → 0.199.0

package/corpus/README.md

@@ -32,4 +32,4 @@ rg -n "defineAction|useActionQuery" node_modules/@agent-native/core-corpus/corpu
 
 ## Generated Counts
 
-- template files: 10915
+- template files: 10942

package/corpus/templates/analytics/.agents/skills/monitoring/SKILL.md

@@ -77,7 +77,9 @@ selection to the `monitoring` application-state key.
 A recording's devtools Console error lines link to the grouped issue at
 `/monitoring?view=errors&issue=<id>`, resolved by `match-error-issues` (exact
 fingerprint match, no heuristics); issues link back to the originating
-recording at `/sessions/<recordingId>`.
+recording at `/sessions/<recordingId>`. The fingerprint includes the app, so
+`match-error-issues` takes the recording's `app` and only matches issues filed
+under it.
 
 ## Related Skills
 

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

@@ -17,6 +17,8 @@ All application data lives in **SQL** (local PGlite, hosted Postgres in producti
 
 Large binary or file-like payloads (images, video/audio, PDFs, ZIPs, screenshots, session replay chunks, thumbnails, generated assets, `data:` URLs, and base64 file bodies) must go through configured file/blob storage such as `uploadFile()` or `putPrivateBlob()`. Persist only the returned URL, asset id, or opaque blob handle in SQL. If storage is unavailable in hosted or persistent-database mode, fail closed with setup guidance instead of falling back to base64 in `application_state`, `settings`, `resources`, or app tables.
 
+**Uploaded files an action opens later** (chat attachments, import controls, chunked commits) are one core `AttachmentRef`: mint with `mintAttachmentRef`, open with `resolveAttachment` and `unwrapAttachment` from `@agent-native/core/private-blob`. Never write a template descriptor, never branch on error text, and never truncate a ref (`ATTACHMENT_REF_MAX_CHARS` is the floor for any prompt or field that carries one). Each failure is typed: `notFound`, `forbiddenScope`, `expired` and `malformed` are definitive and stop the turn; only `storageUnavailable` is retryable, and the same ref works once storage is back, so never ask the user to attach the file again for it.
+
 **Local File Mode exception:** some artifact apps (Content, Plans, Slides, Dashboards, Designs, etc.) can intentionally use repo files as the source of truth for the artifact itself. This must be explicit via `agent-native.json`, `AGENT_NATIVE_MODE=local-files`, or an app-owned local-file action helper. In that mode, the UI and agent still go through app actions, but those actions read/write scoped files through `@agent-native/core/local-artifacts` instead of SQL rows. App state, auth, settings, credentials, collaboration metadata, and hosted database mode remain SQL. File-to-database or file-to-provider synchronization is an explicit sync step, not an implicit side effect of editing.
 
 When you add a data model, a list, or a read path, also follow the `performance` skill: project only the columns a list renders, index the columns hot queries filter/sort on, and avoid query waterfalls — so apps stay fast as data grows.

package/corpus/templates/analytics/CHANGELOG.md

@@ -3,6 +3,13 @@
 All notable user-facing changes to Agent-Native Analytics are documented here. Open it any
 time from the command menu (Cmd+K → "What's new") or from Settings.
 
+## 2026-10-01
+
+### Improved
+
+- Error issues in Monitoring link straight to the chat thread that failed, and one underlying error now stays a single issue instead of splitting after each deploy
+- The observability settings tab is now labeled Observability.
+
 ## 2026-09-30
 
 ### Improved

package/corpus/templates/analytics/actions/match-error-issues.ts

@@ -42,11 +42,20 @@ export default defineAction({
       )
       .max(100)
       .describe("Session console error lines to resolve to issues."),
+    app: z
+      .string()
+      .optional()
+      .describe(
+        "The recording's app. Issues are filed per app, so lines only match issues filed under it.",
+      ),
   }),
   http: { method: "POST" },
   readOnly: true,
   grounding: true,
   run: async (args) => {
-    return matchErrorIssuesBySignatures(resolveScope(), args.signatures);
+    return matchErrorIssuesBySignatures(
+      resolveScope(),
+      args.signatures.map((signature) => ({ ...signature, app: args.app })),
+    );
   },
 });

package/corpus/templates/analytics/app/pages/monitoring/errors/IssueDetail.tsx

@@ -13,6 +13,7 @@ import { Card, CardContent } from "@/components/ui/card";
 import { Skeleton } from "@/components/ui/skeleton";
 import { cn } from "@/lib/utils";
 
+import { failureThreadUrl } from "./failure-thread-url";
 import { fmt, useErrorsT } from "./i18n";
 import type {
   ErrorBreadcrumb,
@@ -195,7 +196,8 @@ function JsonBlock({ value }: { value: Record<string, unknown> }) {
 
 function LatestOccurrenceCard({ event }: { event: ErrorEventDetail }) {
   const t = useErrorsT();
-  const details: Array<{ label: string; value: string }> = [
+  const threadUrl = failureThreadUrl(event.extra);
+  const details: Array<{ label: string; value: string; href?: string }> = [
     {
       label: t.occurrenceTime,
       value: formatDateTime(event.occurredAt),
@@ -206,6 +208,9 @@ function LatestOccurrenceCard({ event }: { event: ErrorEventDetail }) {
     },
   ];
   if (event.url) details.push({ label: t.url, value: event.url });
+  if (threadUrl) {
+    details.push({ label: t.chatThread, value: threadUrl, href: threadUrl });
+  }
 
   return (
     <Card>
@@ -228,7 +233,18 @@ function LatestOccurrenceCard({ event }: { event: ErrorEventDetail }) {
                 {item.label}
               </div>
               <div className="mt-0.5 truncate text-sm text-foreground">
-                {item.value}
+                {item.href ? (
+                  <a
+                    href={item.href}
+                    target="_blank"
+                    rel="noreferrer noopener"
+                    className="underline underline-offset-2"
+                  >
+                    {item.value}
+                  </a>
+                ) : (
+                  item.value
+                )}
               </div>
             </div>
           ))}

package/corpus/templates/analytics/app/pages/monitoring/errors/failure-thread-url.ts

@@ -0,0 +1,15 @@
+/**
+ * The chat thread a failure happened in, when its capture named one
+ * (`extra.failureContext.threadUrl`). Events are client-submitted, so only an
+ * http(s) address is returned; the caller shows the address itself as the link
+ * text so a planted one cannot hide where it points.
+ */
+export function failureThreadUrl(
+  extra: Record<string, unknown> | undefined,
+): string | undefined {
+  const failure = extra?.failureContext as { threadUrl?: unknown } | undefined;
+  const url = failure?.threadUrl;
+  if (typeof url !== "string" || !URL.canParse(url)) return undefined;
+  const { protocol } = new URL(url);
+  return protocol === "https:" || protocol === "http:" ? url : undefined;
+}

package/corpus/templates/analytics/app/pages/monitoring/errors/i18n.ts

@@ -53,6 +53,7 @@ const MESSAGES = {
     latestOccurrence: "Latest occurrence",
     message: "Message",
     url: "URL",
+    chatThread: "Chat thread",
     occurrenceTime: "Occurred",
     stackTrace: "Stack trace",
     stackFrameCount: "{count} frames",

package/corpus/templates/analytics/app/pages/sessions/SessionDetailPage.tsx

@@ -566,12 +566,16 @@ function ReplayPlayer({
     [errorSignatures],
   );
   const recordingId = response.recording.id;
+  const recordingApp = response.recording.app;
   const issueMatchQuery = useQuery({
     queryKey: ["match-error-issues", recordingId, errorSignaturesKey],
     queryFn: () =>
       callAction<Record<string, SessionIssueMatch>>(
         "match-error-issues",
-        { signatures: errorSignatures },
+        {
+          signatures: errorSignatures,
+          ...(recordingApp ? { app: recordingApp } : {}),
+        },
         { method: "POST" },
       ),
     enabled: devToolsOpen && errorSignatures.length > 0,

package/corpus/templates/analytics/changelog/2026-10-01-error-issues-in-monitoring-link-straight-to-the-chat-thread-.md

@@ -0,0 +1,6 @@
+---
+type: improved
+date: 2026-10-01
+---
+
+Error issues in Monitoring link straight to the chat thread that failed, and one underlying error now stays a single issue instead of splitting after each deploy