@anuma/sdk 6.11.0 → 6.12.0

package/dist/react/index.cjs

@@ -7148,6 +7148,9 @@ async function decomposeQuery(query, options) {
       ...options.baseUrl !== void 0 && { baseUrl: options.baseUrl },
       model: options.model ?? DEFAULT_MODEL2,
       systemPrompt: SYSTEM_PROMPT2,
+      // The query itself rides the user turn below, so SYSTEM_PROMPT is the whole
+      // fixed instruction — which is what lets the portal own it outright.
+      taskType: "memory_decompose",
       // Wrap the bare query in a task framing so the model treats it as
       // input to classify, not as a question to answer conversationally.
       // Bare-query inputs caused Anthropic models to respond with prose
@@ -7491,24 +7494,19 @@ function createLlmNeighborRefiner(options) {
     async refine(query, candidates, limit) {
       if (candidates.length === 0) return [];
       const numbered = candidates.map((name, i) => `[${i + 1}] ${name}`).join("\n");
-      const systemPrompt = `You help a memory-retrieval system decide which related topics to explore.
-
-Given a user's question and a numbered list of candidate topics/entities linked to memories found so far, pick the ones most likely to lead to memories that help ANSWER the question. Choose at most ${limit}. Prefer topics semantically related to the question; ignore incidental ones.
-
-Output strict JSON, no prose: { "expand": [<entity names to expand, verbatim from the list>] }`;
       const parsed = await callPortalJsonCompletion({
         ...options.apiKey !== void 0 && { apiKey: options.apiKey },
         ...options.getToken !== void 0 && { getToken: options.getToken },
         ...options.baseUrl !== void 0 && { baseUrl: options.baseUrl },
         taskType: "memory_graph",
         model: options.model ?? DEFAULT_REFINER_MODEL,
-        systemPrompt,
+        systemPrompt: REFINER_SYSTEM_PROMPT,
         userMessage: `Question: ${query}
 
 Candidate topics:
 ${numbered}
 
-Which should be expanded?`,
+Which should be expanded? Choose at most ${limit}.`,
         tag: "memory/graph-refine",
         maxAttempts: options.maxAttempts ?? DEFAULT_REFINER_ATTEMPTS,
         totalTimeoutMs: options.totalTimeoutMs ?? DEFAULT_REFINER_TOTAL_TIMEOUT_MS,
@@ -7529,7 +7527,7 @@ Which should be expanded?`,
     }
   };
 }
-var MAX_HOPS, ENTITY_FANOUT, MIN_REFINER_CANDIDATES, MAX_REFINER_CANDIDATES, NODE_BUDGET, VAULT_SIZE_HOP_CAP, DEFAULT_REFINER_MODEL, DEFAULT_REFINER_ATTEMPTS, DEFAULT_REFINER_TOTAL_TIMEOUT_MS;
+var MAX_HOPS, ENTITY_FANOUT, MIN_REFINER_CANDIDATES, MAX_REFINER_CANDIDATES, NODE_BUDGET, VAULT_SIZE_HOP_CAP, DEFAULT_REFINER_MODEL, DEFAULT_REFINER_ATTEMPTS, DEFAULT_REFINER_TOTAL_TIMEOUT_MS, REFINER_SYSTEM_PROMPT;
 var init_graphTraversal = __esm({
   "src/lib/memory/graphTraversal.ts"() {
     "use strict";
@@ -7548,6 +7546,11 @@ var init_graphTraversal = __esm({
     DEFAULT_REFINER_MODEL = "inclusionai/ling-2.6-flash";
     DEFAULT_REFINER_ATTEMPTS = 1;
     DEFAULT_REFINER_TOTAL_TIMEOUT_MS = 8e3;
+    REFINER_SYSTEM_PROMPT = `You help a memory-retrieval system decide which related topics to explore.
+
+Given a user's question and a numbered list of candidate topics/entities linked to memories found so far, pick the ones most likely to lead to memories that help ANSWER the question. Never return more than the maximum the user turn asks for. Prefer topics semantically related to the question; ignore incidental ones.
+
+Output strict JSON, no prose: { "expand": [<entity names to expand, verbatim from the list>] }`;
   }
 });
 
@@ -19038,6 +19041,7 @@ ${TRUNCATION_NOTICE}` : formatted;
 // src/lib/memory/reflect.ts
 init_clientConfig();
 init_logger();
+init_taskType();
 init_portalLlm();
 init_recall();
 var DEFAULT_BASE_URL2 = BASE_URL;
@@ -19083,11 +19087,13 @@ Respond with ONLY a single JSON object conforming to this JSON Schema, with no p
 ${JSON.stringify(
     options.responseSchema
   )}` : basePrompt;
-  const userMessage = `Question:
-${trimmed}
-
-Memories (use only these as evidence):
-${evidence}`;
+  const userMessage = [
+    `Question:
+${trimmed}`,
+    ...options.userInstructions ? [options.userInstructions] : [],
+    `Memories (use only these as evidence):
+${evidence}`
+  ].join("\n\n");
   const maxTokens = options.maxTokens ?? DEFAULT_MAX_TOKENS;
   const fetchImpl = options.fetchFn ?? fetch;
   const log = getLogger();
@@ -19101,7 +19107,13 @@ ${evidence}`;
   try {
     response = await fetchImpl(`${baseUrl}/api/v1/chat/completions`, {
       method: "POST",
-      headers: { ...authHeaders, "Content-Type": "application/json" },
+      // No task type unless the caller named one — an undeclared task adds no
+      // header at all, which is what keeps user-facing reflect() unlabelled.
+      headers: {
+        ...authHeaders,
+        ...taskTypeHeader(options.taskType),
+        "Content-Type": "application/json"
+      },
       body: JSON.stringify({
         model,
         // Modern OpenAI field; the portal reads only `max_completion_tokens`
@@ -19553,10 +19565,15 @@ async function synthesizeFacet(facet, ctx, options, prior) {
     limit,
     types: ["fact"],
     maxTokens: DEFAULT_FACET_MAX_TOKENS,
-    // Profile-facet synthesis is a background op, so it marks its own prompt.
-    // reflect() itself must NOT mark — it also serves the user's own questions,
-    // and that traffic is chat, not an internal flow. See ../internalFlowMarker.
-    systemPrompt: withInternalFlowMarker(buildFacetSystemPrompt(facet)),
+    // Profile-facet synthesis is a background op, so it marks its own prompt AND
+    // names its own task. reflect() itself must do neither — it also serves the
+    // user's own questions, and that traffic is chat, not an internal flow. See
+    // ../internalFlowMarker and ReflectOptions.taskType.
+    taskType: "memory_profile_synth",
+    systemPrompt: withInternalFlowMarker(FACET_SYSTEM_PROMPT),
+    // The facet's label/guidance/response-fields, on the user turn — what keeps
+    // the system half fixed and therefore server-ownable.
+    userInstructions: buildFacetUserInstructions(facet),
     responseSchema: facetResponseSchema(facet.key),
     memories
   });
@@ -19614,19 +19631,22 @@ function fallbackSection(facet, prior) {
     stale: true
   };
 }
-function buildFacetSystemPrompt(facet) {
-  const structuredField = FACET_STRUCTURED_RESPONSE_HINT[facet.key] ?? "";
-  return `You are writing the "${facet.label}" section of a person's shareable profile, using their private memories (supplied as evidence) as the only source of truth.
-
-Task for this section:
-${facet.guidance}
+var FACET_SYSTEM_PROMPT = `You are writing one section of a person's shareable profile, using their private memories (supplied as evidence) as the only source of truth. The user turn names the section, states the task for it, and gives the exact JSON shape to respond in.
 
 Rules:
 - Ground every claim in the supplied memories \u2014 never invent, infer beyond, or embellish what they support.
 - If the memories don't cover this section, return an empty summary with hasEvidence=false. Do not pad or guess.
 - Write in third person about the person, in a natural voice suitable for a public profile (no "I"/"you", no name repetition).
 - Be concise and specific; no preamble, hedging, or meta-commentary.
-- Respond as JSON: { "summary": <the section text, or "">, "hasEvidence": <true|false>${structuredField} }.`;
+- Respond as JSON in exactly the shape the user turn states, with no extra fields.`;
+function buildFacetUserInstructions(facet) {
+  const structuredField = FACET_STRUCTURED_RESPONSE_HINT[facet.key] ?? "";
+  return `Section: "${facet.label}"
+
+Task for this section:
+${facet.guidance}
+
+Respond as JSON: { "summary": <the section text, or "">, "hasEvidence": <true|false>${structuredField} }.`;
 }
 function extractFacetText(structured) {
   if (structured && typeof structured === "object") {

package/dist/react/index.d.mts

@@ -6140,6 +6140,51 @@ declare function getMemoriesByEntityNamesOp(ctx: EntityOperationsContext, entity
  */
 declare function getEntitiesByMemoryIdsOp(ctx: EntityOperationsContext, memoryIds: readonly string[]): Promise<Map<string, Set<string>>>;
 
+/**
+ * Class-B task types — the vocabulary of the `X-Anuma-Task-Type` header.
+ *
+ * A Class-B flow has ONE fixed purpose and no conversation: extract memories
+ * from a snippet, pick a topic, consolidate duplicates, classify a query. Today
+ * each of those builds its own system prompt on the client and sends it as a
+ * `role:system` message, which makes the prompt a suggestion rather than a
+ * contract — a caller can reword it into "you are a general assistant" and get
+ * general chat at internal-endpoint prices.
+ *
+ * The fix is that the SERVER owns the text and the client only names the task.
+ * This header is the name. The portal allowlists it against its own copy of this
+ * enum (ai-portal `internal/systemprompt/tasks.go`) and DROPS anything it does
+ * not recognise, so an unknown value degrades to "no task declared" rather than
+ * failing the request.
+ *
+ * ⚠ These string values are a wire contract with ai-portal. Adding one here
+ * before the portal knows it is harmless (it is dropped); renaming or removing
+ * one silently stops that flow being counted. Keep them in step with
+ * `AllTaskTypes` on the portal side, and see ai-portal
+ * `docs/BACKEND_OWNED_TASK_PROMPTS.md` for the rollout.
+ *
+ * ⚠ RELEASE ORDER. This union is a PUBLIC type, so a split is breaking in both
+ * directions and has to be sequenced:
+ *
+ *   1. merge + publish this package;
+ *   2. bump `@anuma/sdk` in the consumer and switch its call sites to the new
+ *      names in the same commit.
+ *
+ * A consumer on the OLD version cannot compile the new names, and a consumer on
+ * the NEW version cannot compile the retired ones (`app_inspiration` is gone
+ * here, replaced by the three `app_inspiration_*` names). Both halves of that
+ * are type-only — the wire itself always degrades safely, because the portal
+ * drops any value it does not recognise. Concretely: ai-memoryless-client#5782
+ * is blocked on this publish for exactly that reason.
+ *
+ * Deliberately ABSENT: agent personas, `reflect()` when it answers the user, and
+ * the app-idea chat. Those carry an open conversation with the user, so a fixed
+ * server-owned prompt would be wrong rather than merely premature — the same
+ * boundary {@link INTERNAL_FLOW_MARKER} draws.
+ *
+ * @public
+ */
+type TaskType = "title" | "commit_message" | "memory_extract" | "memory_dedup" | "memory_decay" | "memory_injection_check" | "memory_verify_support" | "memory_autosort" | "memory_topic" | "memory_consolidate" | "memory_decompose" | "memory_profile_synth" | "memory_graph" | "folder_context" | "selection_memory" | "summarize" | "style_analysis" | "classify_search" | "app_inspiration_generate" | "app_inspiration_trends" | "app_inspiration_remix" | "spotlight_image" | "slide_image" | "slide_video" | "slide_music" | "slide_sfx" | "media_video" | "media_audio" | "media_bg_removal" | "media_image_preset" | "tool_app_builder" | "tool_document_builder" | "tool_slides" | "tool_slides_image_gen" | "connector_guidance" | "cf_task" | "xbot_intent" | "xbot_council" | "scheduled_task";
+
 /**
  * Shared portal LLM call for the memory pipeline.
  *
@@ -9390,6 +9435,28 @@ interface ReflectOptions extends RecallOptions, PortalLlmAuth {
     maxTokens?: number;
     /** Override the grounding system prompt. */
     systemPrompt?: string;
+    /**
+     * Extra caller instruction to carry on the USER turn, between the question and
+     * the evidence block (see the `userMessage` assembly below). This is the slot a
+     * background caller uses to keep its per-request data OUT of the system message
+     * without colliding with the numbered evidence list — profile-facet synthesis
+     * puts its section label, guidance and response-field hint here so its system
+     * half can stay fixed and server-ownable.
+     */
+    userInstructions?: string;
+    /**
+     * Class-B task name for the `X-Anuma-Task-Type` header, or nothing.
+     *
+     * Deliberately OPTIONAL and unset by default. reflect() also answers the user's
+     * OWN question, and that traffic is chat, not an internal flow — declaring a
+     * task type unconditionally here would put an internal-flow name on real
+     * conversation, which is the same boundary `INTERNAL_FLOW_MARKER` draws
+     * (reflect is deliberately unmarked; its background caller marks its own
+     * prompt — see ../internalFlowMarker.ts). So the name is per call: only a
+     * caller with ONE fixed purpose passes
+     * one, and today that is profile-facet synthesis (`memory_profile_synth`).
+     */
+    taskType?: TaskType;
     /** Endpoint for the answer LLM. */
     baseUrl?: string;
     /** Override fetch (for tests). */

package/dist/react/index.d.ts

@@ -6140,6 +6140,51 @@ declare function getMemoriesByEntityNamesOp(ctx: EntityOperationsContext, entity
  */
 declare function getEntitiesByMemoryIdsOp(ctx: EntityOperationsContext, memoryIds: readonly string[]): Promise<Map<string, Set<string>>>;
 
+/**
+ * Class-B task types — the vocabulary of the `X-Anuma-Task-Type` header.
+ *
+ * A Class-B flow has ONE fixed purpose and no conversation: extract memories
+ * from a snippet, pick a topic, consolidate duplicates, classify a query. Today
+ * each of those builds its own system prompt on the client and sends it as a
+ * `role:system` message, which makes the prompt a suggestion rather than a
+ * contract — a caller can reword it into "you are a general assistant" and get
+ * general chat at internal-endpoint prices.
+ *
+ * The fix is that the SERVER owns the text and the client only names the task.
+ * This header is the name. The portal allowlists it against its own copy of this
+ * enum (ai-portal `internal/systemprompt/tasks.go`) and DROPS anything it does
+ * not recognise, so an unknown value degrades to "no task declared" rather than
+ * failing the request.
+ *
+ * ⚠ These string values are a wire contract with ai-portal. Adding one here
+ * before the portal knows it is harmless (it is dropped); renaming or removing
+ * one silently stops that flow being counted. Keep them in step with
+ * `AllTaskTypes` on the portal side, and see ai-portal
+ * `docs/BACKEND_OWNED_TASK_PROMPTS.md` for the rollout.
+ *
+ * ⚠ RELEASE ORDER. This union is a PUBLIC type, so a split is breaking in both
+ * directions and has to be sequenced:
+ *
+ *   1. merge + publish this package;
+ *   2. bump `@anuma/sdk` in the consumer and switch its call sites to the new
+ *      names in the same commit.
+ *
+ * A consumer on the OLD version cannot compile the new names, and a consumer on
+ * the NEW version cannot compile the retired ones (`app_inspiration` is gone
+ * here, replaced by the three `app_inspiration_*` names). Both halves of that
+ * are type-only — the wire itself always degrades safely, because the portal
+ * drops any value it does not recognise. Concretely: ai-memoryless-client#5782
+ * is blocked on this publish for exactly that reason.
+ *
+ * Deliberately ABSENT: agent personas, `reflect()` when it answers the user, and
+ * the app-idea chat. Those carry an open conversation with the user, so a fixed
+ * server-owned prompt would be wrong rather than merely premature — the same
+ * boundary {@link INTERNAL_FLOW_MARKER} draws.
+ *
+ * @public
+ */
+type TaskType = "title" | "commit_message" | "memory_extract" | "memory_dedup" | "memory_decay" | "memory_injection_check" | "memory_verify_support" | "memory_autosort" | "memory_topic" | "memory_consolidate" | "memory_decompose" | "memory_profile_synth" | "memory_graph" | "folder_context" | "selection_memory" | "summarize" | "style_analysis" | "classify_search" | "app_inspiration_generate" | "app_inspiration_trends" | "app_inspiration_remix" | "spotlight_image" | "slide_image" | "slide_video" | "slide_music" | "slide_sfx" | "media_video" | "media_audio" | "media_bg_removal" | "media_image_preset" | "tool_app_builder" | "tool_document_builder" | "tool_slides" | "tool_slides_image_gen" | "connector_guidance" | "cf_task" | "xbot_intent" | "xbot_council" | "scheduled_task";
+
 /**
  * Shared portal LLM call for the memory pipeline.
  *
@@ -9390,6 +9435,28 @@ interface ReflectOptions extends RecallOptions, PortalLlmAuth {
     maxTokens?: number;
     /** Override the grounding system prompt. */
     systemPrompt?: string;
+    /**
+     * Extra caller instruction to carry on the USER turn, between the question and
+     * the evidence block (see the `userMessage` assembly below). This is the slot a
+     * background caller uses to keep its per-request data OUT of the system message
+     * without colliding with the numbered evidence list — profile-facet synthesis
+     * puts its section label, guidance and response-field hint here so its system
+     * half can stay fixed and server-ownable.
+     */
+    userInstructions?: string;
+    /**
+     * Class-B task name for the `X-Anuma-Task-Type` header, or nothing.
+     *
+     * Deliberately OPTIONAL and unset by default. reflect() also answers the user's
+     * OWN question, and that traffic is chat, not an internal flow — declaring a
+     * task type unconditionally here would put an internal-flow name on real
+     * conversation, which is the same boundary `INTERNAL_FLOW_MARKER` draws
+     * (reflect is deliberately unmarked; its background caller marks its own
+     * prompt — see ../internalFlowMarker.ts). So the name is per call: only a
+     * caller with ONE fixed purpose passes
+     * one, and today that is profile-facet synthesis (`memory_profile_synth`).
+     */
+    taskType?: TaskType;
     /** Endpoint for the answer LLM. */
     baseUrl?: string;
     /** Override fetch (for tests). */

package/dist/react/index.mjs

@@ -178,7 +178,7 @@ import {
   updateVaultMemoryOp,
   useEncryption,
   vaultMemoryToStored
-} from "./chunk-HNQ2ZEFF.mjs";
+} from "./chunk-6IBFFWCE.mjs";
 import {
   PiiRedactor,
   createStreamingDeAnonymizer,
@@ -8949,11 +8949,13 @@ Respond with ONLY a single JSON object conforming to this JSON Schema, with no p
 ${JSON.stringify(
     options.responseSchema
   )}` : basePrompt;
-  const userMessage = `Question:
-${trimmed}
-
-Memories (use only these as evidence):
-${evidence}`;
+  const userMessage = [
+    `Question:
+${trimmed}`,
+    ...options.userInstructions ? [options.userInstructions] : [],
+    `Memories (use only these as evidence):
+${evidence}`
+  ].join("\n\n");
   const maxTokens = options.maxTokens ?? DEFAULT_MAX_TOKENS;
   const fetchImpl = options.fetchFn ?? fetch;
   const log = getLogger();
@@ -8967,7 +8969,13 @@ ${evidence}`;
   try {
     response = await fetchImpl(`${baseUrl}/api/v1/chat/completions`, {
       method: "POST",
-      headers: { ...authHeaders, "Content-Type": "application/json" },
+      // No task type unless the caller named one — an undeclared task adds no
+      // header at all, which is what keeps user-facing reflect() unlabelled.
+      headers: {
+        ...authHeaders,
+        ...taskTypeHeader(options.taskType),
+        "Content-Type": "application/json"
+      },
       body: JSON.stringify({
         model,
         // Modern OpenAI field; the portal reads only `max_completion_tokens`
@@ -9407,10 +9415,15 @@ async function synthesizeFacet(facet, ctx, options, prior) {
     limit,
     types: ["fact"],
     maxTokens: DEFAULT_FACET_MAX_TOKENS,
-    // Profile-facet synthesis is a background op, so it marks its own prompt.
-    // reflect() itself must NOT mark — it also serves the user's own questions,
-    // and that traffic is chat, not an internal flow. See ../internalFlowMarker.
-    systemPrompt: withInternalFlowMarker(buildFacetSystemPrompt(facet)),
+    // Profile-facet synthesis is a background op, so it marks its own prompt AND
+    // names its own task. reflect() itself must do neither — it also serves the
+    // user's own questions, and that traffic is chat, not an internal flow. See
+    // ../internalFlowMarker and ReflectOptions.taskType.
+    taskType: "memory_profile_synth",
+    systemPrompt: withInternalFlowMarker(FACET_SYSTEM_PROMPT),
+    // The facet's label/guidance/response-fields, on the user turn — what keeps
+    // the system half fixed and therefore server-ownable.
+    userInstructions: buildFacetUserInstructions(facet),
     responseSchema: facetResponseSchema(facet.key),
     memories
   });
@@ -9468,19 +9481,22 @@ function fallbackSection(facet, prior) {
     stale: true
   };
 }
-function buildFacetSystemPrompt(facet) {
-  const structuredField = FACET_STRUCTURED_RESPONSE_HINT[facet.key] ?? "";
-  return `You are writing the "${facet.label}" section of a person's shareable profile, using their private memories (supplied as evidence) as the only source of truth.
-
-Task for this section:
-${facet.guidance}
+var FACET_SYSTEM_PROMPT = `You are writing one section of a person's shareable profile, using their private memories (supplied as evidence) as the only source of truth. The user turn names the section, states the task for it, and gives the exact JSON shape to respond in.
 
 Rules:
 - Ground every claim in the supplied memories \u2014 never invent, infer beyond, or embellish what they support.
 - If the memories don't cover this section, return an empty summary with hasEvidence=false. Do not pad or guess.
 - Write in third person about the person, in a natural voice suitable for a public profile (no "I"/"you", no name repetition).
 - Be concise and specific; no preamble, hedging, or meta-commentary.
-- Respond as JSON: { "summary": <the section text, or "">, "hasEvidence": <true|false>${structuredField} }.`;
+- Respond as JSON in exactly the shape the user turn states, with no extra fields.`;
+function buildFacetUserInstructions(facet) {
+  const structuredField = FACET_STRUCTURED_RESPONSE_HINT[facet.key] ?? "";
+  return `Section: "${facet.label}"
+
+Task for this section:
+${facet.guidance}
+
+Respond as JSON: { "summary": <the section text, or "">, "hasEvidence": <true|false>${structuredField} }.`;
 }
 function extractFacetText(structured) {
   if (structured && typeof structured === "object") {

package/dist/react/{recall-F5DBVCU2.mjs → recall-QUWN7DJ7.mjs}

@@ -1,6 +1,6 @@
 import {
   recall
-} from "./chunk-HNQ2ZEFF.mjs";
+} from "./chunk-6IBFFWCE.mjs";
 import "./chunk-CJ32HO6Q.mjs";
 import "./chunk-GYKJOWEO.mjs";
 export {

package/dist/server/{chunk-BKB6AT7Z.mjs → chunk-7YTEE6JT.mjs}

@@ -19193,6 +19193,9 @@ async function decomposeQuery(query, options) {
       ...options.baseUrl !== void 0 && { baseUrl: options.baseUrl },
       model: options.model ?? DEFAULT_MODEL,
       systemPrompt: SYSTEM_PROMPT,
+      // The query itself rides the user turn below, so SYSTEM_PROMPT is the whole
+      // fixed instruction — which is what lets the portal own it outright.
+      taskType: "memory_decompose",
       // Wrap the bare query in a task framing so the model treats it as
       // input to classify, not as a question to answer conversationally.
       // Bare-query inputs caused Anthropic models to respond with prose
@@ -20920,7 +20923,7 @@ function createMemoryVaultSearchTool(vaultCtx, embeddingOptions, cache, searchOp
             subQueries = decomp.subQueries;
           }
         }
-        const { recall: recall2 } = await import("./recall-HVIEAH7J.mjs");
+        const { recall: recall2 } = await import("./recall-HOVWMT4Q.mjs");
         let recallDegraded = [];
         const result = await recall2(
           query,
@@ -21173,29 +21176,29 @@ async function traverseGraphLane(query, entityCtx, options = {}) {
 var DEFAULT_REFINER_MODEL = "inclusionai/ling-2.6-flash";
 var DEFAULT_REFINER_ATTEMPTS = 1;
 var DEFAULT_REFINER_TOTAL_TIMEOUT_MS = 8e3;
+var REFINER_SYSTEM_PROMPT = `You help a memory-retrieval system decide which related topics to explore.
+
+Given a user's question and a numbered list of candidate topics/entities linked to memories found so far, pick the ones most likely to lead to memories that help ANSWER the question. Never return more than the maximum the user turn asks for. Prefer topics semantically related to the question; ignore incidental ones.
+
+Output strict JSON, no prose: { "expand": [<entity names to expand, verbatim from the list>] }`;
 function createLlmNeighborRefiner(options) {
   return {
     async refine(query, candidates, limit) {
       if (candidates.length === 0) return [];
       const numbered = candidates.map((name, i) => `[${i + 1}] ${name}`).join("\n");
-      const systemPrompt = `You help a memory-retrieval system decide which related topics to explore.
-
-Given a user's question and a numbered list of candidate topics/entities linked to memories found so far, pick the ones most likely to lead to memories that help ANSWER the question. Choose at most ${limit}. Prefer topics semantically related to the question; ignore incidental ones.
-
-Output strict JSON, no prose: { "expand": [<entity names to expand, verbatim from the list>] }`;
       const parsed = await callPortalJsonCompletion({
         ...options.apiKey !== void 0 && { apiKey: options.apiKey },
         ...options.getToken !== void 0 && { getToken: options.getToken },
         ...options.baseUrl !== void 0 && { baseUrl: options.baseUrl },
         taskType: "memory_graph",
         model: options.model ?? DEFAULT_REFINER_MODEL,
-        systemPrompt,
+        systemPrompt: REFINER_SYSTEM_PROMPT,
         userMessage: `Question: ${query}
 
 Candidate topics:
 ${numbered}
 
-Which should be expanded?`,
+Which should be expanded? Choose at most ${limit}.`,
         tag: "memory/graph-refine",
         maxAttempts: options.maxAttempts ?? DEFAULT_REFINER_ATTEMPTS,
         totalTimeoutMs: options.totalTimeoutMs ?? DEFAULT_REFINER_TOTAL_TIMEOUT_MS,

package/dist/server/index.cjs

@@ -20915,6 +20915,9 @@ async function decomposeQuery(query, options) {
       ...options.baseUrl !== void 0 && { baseUrl: options.baseUrl },
       model: options.model ?? DEFAULT_MODEL,
       systemPrompt: SYSTEM_PROMPT,
+      // The query itself rides the user turn below, so SYSTEM_PROMPT is the whole
+      // fixed instruction — which is what lets the portal own it outright.
+      taskType: "memory_decompose",
       // Wrap the bare query in a task framing so the model treats it as
       // input to classify, not as a question to answer conversationally.
       // Bare-query inputs caused Anthropic models to respond with prose
@@ -21220,24 +21223,19 @@ function createLlmNeighborRefiner(options) {
     async refine(query, candidates, limit) {
       if (candidates.length === 0) return [];
       const numbered = candidates.map((name, i) => `[${i + 1}] ${name}`).join("\n");
-      const systemPrompt = `You help a memory-retrieval system decide which related topics to explore.
-
-Given a user's question and a numbered list of candidate topics/entities linked to memories found so far, pick the ones most likely to lead to memories that help ANSWER the question. Choose at most ${limit}. Prefer topics semantically related to the question; ignore incidental ones.
-
-Output strict JSON, no prose: { "expand": [<entity names to expand, verbatim from the list>] }`;
       const parsed = await callPortalJsonCompletion({
         ...options.apiKey !== void 0 && { apiKey: options.apiKey },
         ...options.getToken !== void 0 && { getToken: options.getToken },
         ...options.baseUrl !== void 0 && { baseUrl: options.baseUrl },
         taskType: "memory_graph",
         model: options.model ?? DEFAULT_REFINER_MODEL,
-        systemPrompt,
+        systemPrompt: REFINER_SYSTEM_PROMPT,
         userMessage: `Question: ${query}
 
 Candidate topics:
 ${numbered}
 
-Which should be expanded?`,
+Which should be expanded? Choose at most ${limit}.`,
         tag: "memory/graph-refine",
         maxAttempts: options.maxAttempts ?? DEFAULT_REFINER_ATTEMPTS,
         totalTimeoutMs: options.totalTimeoutMs ?? DEFAULT_REFINER_TOTAL_TIMEOUT_MS,
@@ -21258,7 +21256,7 @@ Which should be expanded?`,
     }
   };
 }
-var MAX_HOPS, ENTITY_FANOUT, MIN_REFINER_CANDIDATES, MAX_REFINER_CANDIDATES, NODE_BUDGET, VAULT_SIZE_HOP_CAP, DEFAULT_REFINER_MODEL, DEFAULT_REFINER_ATTEMPTS, DEFAULT_REFINER_TOTAL_TIMEOUT_MS;
+var MAX_HOPS, ENTITY_FANOUT, MIN_REFINER_CANDIDATES, MAX_REFINER_CANDIDATES, NODE_BUDGET, VAULT_SIZE_HOP_CAP, DEFAULT_REFINER_MODEL, DEFAULT_REFINER_ATTEMPTS, DEFAULT_REFINER_TOTAL_TIMEOUT_MS, REFINER_SYSTEM_PROMPT;
 var init_graphTraversal = __esm({
   "src/lib/memory/graphTraversal.ts"() {
     "use strict";
@@ -21277,6 +21275,11 @@ var init_graphTraversal = __esm({
     DEFAULT_REFINER_MODEL = "inclusionai/ling-2.6-flash";
     DEFAULT_REFINER_ATTEMPTS = 1;
     DEFAULT_REFINER_TOTAL_TIMEOUT_MS = 8e3;
+    REFINER_SYSTEM_PROMPT = `You help a memory-retrieval system decide which related topics to explore.
+
+Given a user's question and a numbered list of candidate topics/entities linked to memories found so far, pick the ones most likely to lead to memories that help ANSWER the question. Never return more than the maximum the user turn asks for. Prefer topics semantically related to the question; ignore incidental ones.
+
+Output strict JSON, no prose: { "expand": [<entity names to expand, verbatim from the list>] }`;
   }
 });
 
@@ -30656,6 +30659,7 @@ ${TRUNCATION_NOTICE}` : formatted;
 // src/lib/memory/reflect.ts
 init_clientConfig();
 init_logger();
+init_taskType();
 init_portalLlm();
 init_recall();
 var DEFAULT_BASE_URL2 = BASE_URL;
@@ -30701,11 +30705,13 @@ Respond with ONLY a single JSON object conforming to this JSON Schema, with no p
 ${JSON.stringify(
     options.responseSchema
   )}` : basePrompt;
-  const userMessage = `Question:
-${trimmed}
-
-Memories (use only these as evidence):
-${evidence}`;
+  const userMessage = [
+    `Question:
+${trimmed}`,
+    ...options.userInstructions ? [options.userInstructions] : [],
+    `Memories (use only these as evidence):
+${evidence}`
+  ].join("\n\n");
   const maxTokens = options.maxTokens ?? DEFAULT_MAX_TOKENS;
   const fetchImpl = options.fetchFn ?? fetch;
   const log = getLogger();
@@ -30719,7 +30725,13 @@ ${evidence}`;
   try {
     response = await fetchImpl(`${baseUrl}/api/v1/chat/completions`, {
       method: "POST",
-      headers: { ...authHeaders, "Content-Type": "application/json" },
+      // No task type unless the caller named one — an undeclared task adds no
+      // header at all, which is what keeps user-facing reflect() unlabelled.
+      headers: {
+        ...authHeaders,
+        ...taskTypeHeader(options.taskType),
+        "Content-Type": "application/json"
+      },
       body: JSON.stringify({
         model,
         // Modern OpenAI field; the portal reads only `max_completion_tokens`
@@ -31171,10 +31183,15 @@ async function synthesizeFacet(facet, ctx, options, prior) {
     limit,
     types: ["fact"],
     maxTokens: DEFAULT_FACET_MAX_TOKENS,
-    // Profile-facet synthesis is a background op, so it marks its own prompt.
-    // reflect() itself must NOT mark — it also serves the user's own questions,
-    // and that traffic is chat, not an internal flow. See ../internalFlowMarker.
-    systemPrompt: withInternalFlowMarker(buildFacetSystemPrompt(facet)),
+    // Profile-facet synthesis is a background op, so it marks its own prompt AND
+    // names its own task. reflect() itself must do neither — it also serves the
+    // user's own questions, and that traffic is chat, not an internal flow. See
+    // ../internalFlowMarker and ReflectOptions.taskType.
+    taskType: "memory_profile_synth",
+    systemPrompt: withInternalFlowMarker(FACET_SYSTEM_PROMPT),
+    // The facet's label/guidance/response-fields, on the user turn — what keeps
+    // the system half fixed and therefore server-ownable.
+    userInstructions: buildFacetUserInstructions(facet),
     responseSchema: facetResponseSchema(facet.key),
     memories
   });
@@ -31232,19 +31249,22 @@ function fallbackSection(facet, prior) {
     stale: true
   };
 }
-function buildFacetSystemPrompt(facet) {
-  const structuredField = FACET_STRUCTURED_RESPONSE_HINT[facet.key] ?? "";
-  return `You are writing the "${facet.label}" section of a person's shareable profile, using their private memories (supplied as evidence) as the only source of truth.
-
-Task for this section:
-${facet.guidance}
+var FACET_SYSTEM_PROMPT = `You are writing one section of a person's shareable profile, using their private memories (supplied as evidence) as the only source of truth. The user turn names the section, states the task for it, and gives the exact JSON shape to respond in.
 
 Rules:
 - Ground every claim in the supplied memories \u2014 never invent, infer beyond, or embellish what they support.
 - If the memories don't cover this section, return an empty summary with hasEvidence=false. Do not pad or guess.
 - Write in third person about the person, in a natural voice suitable for a public profile (no "I"/"you", no name repetition).
 - Be concise and specific; no preamble, hedging, or meta-commentary.
-- Respond as JSON: { "summary": <the section text, or "">, "hasEvidence": <true|false>${structuredField} }.`;
+- Respond as JSON in exactly the shape the user turn states, with no extra fields.`;
+function buildFacetUserInstructions(facet) {
+  const structuredField = FACET_STRUCTURED_RESPONSE_HINT[facet.key] ?? "";
+  return `Section: "${facet.label}"
+
+Task for this section:
+${facet.guidance}
+
+Respond as JSON: { "summary": <the section text, or "">, "hasEvidence": <true|false>${structuredField} }.`;
 }
 function extractFacetText(structured) {
   if (structured && typeof structured === "object") {