@anchrd/intel-ui 0.15.0 → 0.16.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@anchrd/intel-ui",
-  "version": "0.15.0",
+  "version": "0.16.0",
   "type": "module",
   "license": "UNLICENSED",
   "repository": {
@@ -60,6 +60,7 @@
     "zod": "^4.4.3"
   },
   "devDependencies": {
+    "@testing-library/dom": "^10.4.1",
     "@testing-library/react": "^16.3.2",
     "@types/node": "^24.13.3",
     "@types/react": "^19.2.17",

package/src/agent/agent-log/agent-log.tsx

@@ -3,7 +3,6 @@ import { useQuery } from "@tanstack/react-query";
 import { ChevronDown, ChevronRight } from "lucide-react";
 import { useState } from "react";
 import {
-  costWindow,
   formatCost,
   formatTokens,
   type RunCost,
@@ -23,9 +22,10 @@ import { useIntelRouterContext } from "@/router/router-context.ts";
  * trimmed there. So this list is short by design and has no paging — the runtime answers at most a
  * hundred runs and keeps no more.
  *
- * ⚠️ A run says what it did and, when it failed, what stopped it. It does not carry the answer it
- * produced: a chat answer belongs to the person it was streamed to and a mail answer to the
- * correspondent, and the runtime deliberately stores neither where this list could reach it.
+ * ⚠️ A run says what it did, when it failed what stopped it, and since #268 what it answered — but
+ * only for the runs nobody was watching (`schedule`, `manual`, `task`). A chat answer belongs to the
+ * person it was streamed to and a mail answer to the correspondent, and the runtime deliberately
+ * stores neither where this list could reach it.
  *
  * ⚠️ Since #251 it also says what each run consumed and what it cost — and the two come from
  * DIFFERENT places on purpose. The tokens are the runtime's own record; the money is Cloudflare's
@@ -223,22 +223,52 @@ function RunRow({
           ) : null}
         </span>
       </button>
-      {open ? <RunDetail agentId={agentId} runId={run.id} /> : null}
+      {open ? <RunDetail agentId={agentId} run={run} /> : null}
     </li>
   );
 }
 
+/**
+ * What an unattended run produced, which is the only place a person can read it (#272).
+ *
+ * ⚠️ Rendered for `schedule`, `manual` and `task`, and for nothing else. A `chat` or `mail` run
+ * carries no answer by construction (#268), so an empty state under one of those would invent a
+ * loss: the answer was streamed into a window or posted to a correspondent and was never meant to
+ * come back here.
+ *
+ * ⚠️ Read from the run the row already holds, not from the detail fetch. `GET /runs` carries the
+ * whole record, and hanging the answer off the second request would hide it whenever the
+ * operational log — the smaller half of what this row is for — happens to be unreadable.
+ */
+function RunAnswer({ run, i18n }: { run: AgentRun; i18n: I18n }) {
+  if (run.trigger === "chat" || run.trigger === "mail") return null;
+  return (
+    <section aria-label={i18n.t("agent.runAnswer")} className="mb-3">
+      <h3 className="text-sm font-semibold">{i18n.t("agent.runAnswer")}</h3>
+      {run.answer ? (
+        // Whitespace preserved: a model answers in paragraphs and lists, and collapsing them turns
+        // a readable report into one block of prose.
+        <p className="mt-1 whitespace-pre-wrap text-sm">{run.answer}</p>
+      ) : (
+        <p className="mt-1 text-sm text-muted-foreground">{i18n.t("agent.runAnswerEmpty")}</p>
+      )}
+    </section>
+  );
+}
+
 // The operational log of one run: what it tried, in order. Fetched only when a row is opened —
 // every run carries its own entries and loading all of them would be the whole log for one screen.
-function RunDetail({ agentId, runId }: { agentId: string; runId: string }) {
+function RunDetail({ agentId, run }: { agentId: string; run: AgentRun }) {
   const { data } = useIntelRouterContext();
   const i18n = useI18n();
+  const runId = run.id;
   const detail = useQuery({
     queryKey: ["agent-run", agentId, runId],
     queryFn: () => data.getAgentRun(agentId, runId),
   });
   return (
     <div className="border-t px-4 py-3">
+      <RunAnswer run={run} i18n={i18n} />
       {detail.isPending ? (
         <p className="text-sm text-muted-foreground">{i18n.t("common.loading")}</p>
       ) : null}

package/src/agent/agent-profile/agent-profile.tsx

@@ -340,8 +340,12 @@ function defaultRoleFor(kind: PickerKind): AgentReferenceRole | null {
  * changes what a document MEANS to an agent must look changeable.
  *
  * ⚠️ Since #255 a row can also be a single document or table, and the role select shows only the
- * roles that kind can carry. `memory` and `semantic-context` stay folders — the agent WRITES into
- * one and SEARCHES the other — so a document simply never offers them.
+ * roles that kind can carry. `memory` and `semantic-context` stay folders — the agent searches both
+ * and writes into one of them — so a document simply never offers them.
+ *
+ * ⚠️ Memory is searched too, since #259, and the hint beside this section says so in words (#269).
+ * The role name alone reads as a write-only notebook, and somebody who believes that files things
+ * there that come back at them out of every later search.
  */
 function KnowledgeSection({
   definition,

package/src/data/agent-runtime/agent-runtime.ts

@@ -43,6 +43,18 @@ export const AgentRun = z.object({
   finishedAt: z.string().nullable(),
   steps: z.number(),
   error: z.string().nullable(),
+  /**
+   * What the run answered, for the runs nobody was watching: `schedule`, `manual` and `task`.
+   *
+   * ⚠️ A `chat` or `mail` run carries none, and that is a runtime invariant rather than an accident
+   * (#268): that answer belongs to the person whose window it was streamed into or to the
+   * correspondent it was posted to. The log screen therefore claims nothing at all on those two
+   * triggers — an empty state there would read as "the answer went missing".
+   *
+   * ⚠️ `.nullish()` for the same reason as `usage` below: a runtime from before #268 sends no such
+   * field, and a required one would blank the whole Log tab over its absence.
+   */
+  answer: z.string().nullish(),
   // ⚠️ `.nullish()` on both, not `.nullable()`. The runtime is a separate deployment and may be a
   // version BEHIND this page: a run list from a runtime without #250/#251 has no such field at all,
   // and a required one would blank the whole Log tab over a missing number.

package/src/i18n/de.json

@@ -322,7 +322,7 @@
   "agent.contactAdd": "Erreichbarkeit hinzufügen",
   "agent.contactAddReason": "Eine Mail-Adresse gehört der Installation, nicht der Definition des Agenten — sie wird dort konfiguriert, wo die Laufzeit betrieben wird.",
   "agent.knows": "Was er weiß",
-  "agent.knowsHint": "Was dieser Agent liest, und wofür jeder Eintrag zählt. Eine Systemnachricht weist ihn an — ein Ordner, ein Dokument oder eine Tabelle. Semantischer Kontext wird durchsucht und in das Gedächtnis wird zurückgeschrieben, deshalb sind beide Ordner.",
+  "agent.knowsHint": "Was dieser Agent liest, und wofür jeder Eintrag zählt. Eine Systemnachricht weist ihn an — ein Ordner, ein Dokument oder eine Tabelle. Semantischer Kontext wird durchsucht, und in das Gedächtnis wird zurückgeschrieben und es wird ebenso durchsucht, deshalb sind beide Ordner. Der Name verspricht weniger als die Rolle: Was der Agent sich im Gedächtnis notiert, kommt ihm bei jeder späteren Suche wieder entgegen.",
   "agent.addReference": "Etwas zum Lesen hinzufügen",
   "agent.removeReferenceOf": "{title} nicht mehr lesen",
   "agent.pickEntry": "Was gelesen wird",
@@ -377,6 +377,8 @@
   "agent.runFailed": "Dieser Lauf konnte nicht gelesen werden.",
   "agent.runLog": "Was dieser Lauf getan hat",
   "agent.runLogEmpty": "Dieser Lauf hat nichts aufgezeichnet.",
+  "agent.runAnswer": "Was dieser Lauf geantwortet hat",
+  "agent.runAnswerEmpty": "Dieser Lauf hat keine Antwort aufgezeichnet.",
   "agent.steps": "{count} Schritte",
   "agent.trigger.chat": "aus dem Chat",
   "agent.trigger.schedule": "nach Zeitplan",

package/src/i18n/en.json

@@ -322,7 +322,7 @@
   "agent.contactAdd": "Add contact",
   "agent.contactAddReason": "A mail address belongs to the installation, not to the agent's definition, so it is configured where the runtime is deployed.",
   "agent.knows": "What it knows",
-  "agent.knowsHint": "What this agent reads, and what each entry counts as. A system message instructs it — a folder, a document or a table. Semantic context is searched and memory is written back to, so both of those are folders.",
+  "agent.knowsHint": "What this agent reads, and what each entry counts as. A system message instructs it — a folder, a document or a table. Semantic context is searched, and memory is written back to and searched as well, so both of those are folders. The name promises less than the role does: what the agent notes down in memory comes back to it in every later search.",
   "agent.addReference": "Add something to read",
   "agent.removeReferenceOf": "Stop reading {title}",
   "agent.pickEntry": "What to read",
@@ -377,6 +377,8 @@
   "agent.runFailed": "This run could not be read.",
   "agent.runLog": "What this run did",
   "agent.runLogEmpty": "This run recorded nothing.",
+  "agent.runAnswer": "What this run answered",
+  "agent.runAnswerEmpty": "This run recorded no answer.",
   "agent.steps": "{count} steps",
   "agent.trigger.chat": "from the chat",
   "agent.trigger.schedule": "on schedule",

package/src/i18n/es.json

@@ -322,7 +322,7 @@
   "agent.contactAdd": "Añadir un contacto",
   "agent.contactAddReason": "Una dirección de correo pertenece a la instalación, no a la definición del agente, así que se configura donde está desplegado el entorno de ejecución.",
   "agent.knows": "Lo que sabe",
-  "agent.knowsHint": "Lo que lee este agente y para qué cuenta cada entrada. Un mensaje de sistema lo instruye — una carpeta, un documento o una tabla. El contexto semántico se busca y en la memoria se escribe de vuelta, por eso ambos son carpetas.",
+  "agent.knowsHint": "Lo que lee este agente y para qué cuenta cada entrada. Un mensaje de sistema lo instruye — una carpeta, un documento o una tabla. El contexto semántico se busca, y en la memoria se escribe de vuelta y también se busca, por eso ambas son carpetas. El nombre promete menos que el papel: lo que el agente anota en la memoria le vuelve en cada búsqueda posterior.",
   "agent.addReference": "Añadir algo para leer",
   "agent.removeReferenceOf": "Dejar de leer {title}",
   "agent.pickEntry": "Qué se lee",
@@ -377,6 +377,8 @@
   "agent.runFailed": "Esta ejecución no se ha podido leer.",
   "agent.runLog": "Lo que ha hecho esta ejecución",
   "agent.runLogEmpty": "Esta ejecución no ha registrado nada.",
+  "agent.runAnswer": "Lo que ha respondido esta ejecución",
+  "agent.runAnswerEmpty": "Esta ejecución no ha registrado ninguna respuesta.",
   "agent.steps": "{count} pasos",
   "agent.trigger.chat": "desde el chat",
   "agent.trigger.schedule": "por horario",