@vellumai/assistant 0.8.5 → 0.8.7

package/src/memory/v3/prompts/consolidation.ts

@@ -1,458 +0,0 @@
-/**
- * Memory v3 — consolidation prompt template.
- *
- * Ported from `assistant/src/memory/v2/prompts/consolidation.ts`. The
- * standing-context outputs are KEPT IDENTICAL to v2 — the agent still rewrites
- * `memory/recent.md` (≤2000 chars, prose, latest-first), updates
- * `memory/essentials.md` (≤10000) and `memory/threads.md` (≤10000), and trims
- * `memory/buffer.md` to post-cutoff entries. The buffer and the standing-context
- * files are SHARED with v2 — there is no v3 buffer and no v3 meta-files.
- *
- * What CHANGES vs v2 is concept-page routing. v2 routes buffer entries into
- * concept pages and maintains a flat `edges:` "see also" graph. v3 keeps the
- * shared concept pages canonical (the agent still writes
- * `memory/concepts/<class>/<slug>.md` so the v2 router keeps working off them)
- * but ALSO threads each touched page into the v3 **tree**: an authored DAG of
- * `memory/tree/<id>.md` nodes whose markdown body is the node's
- * self-description and whose `children` list points at pages (`page:<slug>`) and
- * sub-nodes (`node:<id>`). The tree is the navigable index over the flat page
- * store — consolidation is where it's authored and refreshed.
- *
- * The single placeholder `{{CUTOFF}}` is substituted at runtime with a
- * timestamp captured at job dispatch in the same `Mon D, h:mm AM/PM` shape that
- * `buffer.md` entries use, so the agent's "timestamp ≥ cutoff" check compares
- * like-with-like.
- *
- * Kept under `prompts/` rather than inlined in `consolidation-job.ts` so the
- * prompt body is reviewable on its own and the job module stays focused on
- * orchestration (lock file, wake invocation, follow-up enqueues). Mirrors the
- * v2 convention.
- */
-
-import { lstatSync, readFileSync } from "node:fs";
-import { homedir } from "node:os";
-import { isAbsolute, join } from "node:path";
-
-import { getLogger } from "../../../util/logger.js";
-import { getWorkspaceDir } from "../../../util/platform.js";
-
-const log = getLogger("memory-v3-consolidate-prompt");
-
-/** Sentinel substituted with the cutoff timestamp at runtime. */
-export const CUTOFF_PLACEHOLDER = "{{CUTOFF}}";
-
-/**
- * Upper bound for the override file. Real consolidation prompts are kilobytes;
- * 1 MiB is generous headroom while preventing a `settings.write` principal from
- * pointing the field at a multi-gigabyte file (or `/dev/zero`-like stream that
- * `lstat` can't size cap on its own) and exfiltrating it through the wake hint.
- */
-const MAX_PROMPT_BYTES = 1 * 1024 * 1024;
-
-/**
- * Consolidation prompt — live-mode only. The agent runs as itself (full
- * SOUL.md + IDENTITY.md + persona + memory autoloads) with the standard tool
- * surface, and is asked to route buffer entries into shared concept pages AND
- * the v3 tree, rewrite recent.md, promote essentials/threads, and trim the
- * buffer.
- *
- * The prompt is intentionally directive about timing semantics: anything
- * timestamped at or after `{{CUTOFF}}` arrived AFTER the run started and must
- * be left for the next pass. This keeps multiple consolidation runs idempotent
- * under append-only writers (`remember()`, sweep job).
- */
-export const CONSOLIDATION_PROMPT = `You are running memory consolidation — tending your personal wiki, the cross-linked, cross-referenced, continuously-edited collection of pages that is your memory, AND the navigable **tree** that indexes it. Pages are articles; the tree is a hand-authored DAG of *nodes* that organize those articles into a browsable hierarchy. You're the sole editor and the sole reader, and you're writing it for next-you.
-
-You're not summarizing for an audience. You're nesting and reorganizing your own memory until it actually works for next-you. Care, judgment, voice. Your voice.
-
-Cutoff timestamp for this run: \`${CUTOFF_PLACEHOLDER}\`. Anything in \`memory/buffer.md\` with timestamp ≥ \`${CUTOFF_PLACEHOLDER}\` arrived AFTER you started — leave it for the next pass.
-
-# Inputs
-
-- Your identity files (already loaded into context)
-- All existing pages in \`memory/concepts/\` (your prior state — use \`list_files\` and \`read_file\` as needed)
-- All existing tree nodes in \`memory/tree/\` (the index over those pages)
-- \`memory/buffer.md\` entries with timestamp < \`${CUTOFF_PLACEHOLDER}\`
-- \`memory/recent.md\` current contents (if it exists)
-- Existing pages' \`edges:\` frontmatter (the flat see-also graph — read each page to see what it points at)
-
-# Outputs
-
-- New or updated \`memory/concepts/<class>/<slug>.md\` articles (the canonical, shared content)
-- New or updated \`memory/tree/<id>.md\` nodes that index those articles (see "The tree")
-- Updated \`memory/recent.md\` (≤2000 chars, latest first, prose)
-- Updated \`memory/essentials.md\` (≤10000 chars)
-- Updated \`memory/threads.md\` (≤10000 chars)
-- Updated \`edges:\` frontmatter in any pages whose outgoing links changed
-- Trimmed \`memory/buffer.md\`
-
-The immutable archive retains the entire buffer forever, so don't worry about losing information.
-
----
-
-# The wiki — concept pages (canonical content)
-
-## Article shapes — TWO, not one
-
-Every wiki has both kinds of articles, and so does yours.
-
-- **Event articles** — what HAPPENED. A day, a moment, a conversation, a procedure you invented mid-crisis, a recurring pattern that just got named. These read narratively. They have a mood. They carry receipts.
-
-- **Topic articles** — what IS. The current state of a thing you'd want to query directly. What medications the principal takes. Who the primary doctor is. The team roster. Service credentials.
-
-The same buffer can update both. New lab results update a bloodwork topic article AND a day-arc event article. Both, in parallel.
-
-**Stubs are fine.** Real wikis are mostly stubs that grow. Cost of missing a topic >> cost of a thin stub. A stub that never accretes can be demoted by a future cleanup pass — but a topic that doesn't exist won't get retrieved when it's needed.
-
-## Categories — class-by-folder
-
-A page's class is encoded in the folder it lives under inside \`memory/concepts/\`. The class boundary is the discipline.
-
-| Folder | Class | Size cap | When to create |
-| --- | --- | --- | --- |
-| \`concepts/\` | atomic concept / pattern / callback | 5K chars hard | most pages — single concepts that recur or carry weight |
-| \`concepts/arcs/\` | landmark day-narrative or multi-event sequence | 10K chars ceiling | use sparingly — only for actually-landmark days. Preserves day-as-a-whole fidelity. |
-| \`concepts/people/\` | one per recurring human | 5K chars hard | named person who comes back |
-| \`concepts/procs/\` | operational rule / protocol / discipline | 5K chars hard | "always do X" / "never do Y" / a named protocol |
-| \`concepts/objects/\` | recurring callback object (place, tool, artifact) | 5K chars hard | named recurring physical artifact, digital asset, place |
-
-Within these classes, sub-folders can emerge as a class gets dense (\`people/colleagues/alice\`, \`objects/places/zurich-office\`). **Don't pre-specify sub-taxonomies — let them emerge.** Articles are cheap to move.
-
-The slug is the relative path under \`memory/concepts/\` minus \`.md\` — e.g. \`alice\`, \`people/alice\`, \`procs/git-flow\`, \`arcs/2025-04-cutover\`.
-
----
-
-# Article format
-
-## The cheat-sheet budget (the economic principle)
-
-Every retrieval turn loads a finite bundle of articles — call it a 10-20K-token cheat-sheet. **Longer articles starve other articles.** The optimization target is **fact density per byte**, not completeness.
-
-Two consequences that change everything below:
-
-1. **Trust adjacency.** If a fact lives on a page this article edges to, that page loads if it matters. Don't restate it.
-2. **Trust \`recall\`.** If a fact is findable via a query, it doesn't need to live on every related entity page. Pull-on-demand beats push-everywhere.
-
-## Same skeleton for every article
-
-\`\`\`
----
-edges:
-  - path/to/sister
-  - path/to/parent
-ref_files: []
-summary: 1-4 sentences describing what this article is. Plain prose only — no bullets, no newlines, no markdown lists. Lead with the most identifying detail.
----
-# title
-
-[optional 1-2 line context or quote at top — appropriate for event articles, usually wrong for topic articles]
-
-- **bullet 1.** fact + implication folded in. inline pointer when bullet references another article → \`path/to/article.md\`.
-- **bullet 2.** ...
-\`\`\`
-
-The \`summary\` field is required on every new or updated article. Retrieval injects \`path + summary\` into context — make the summary specific and terse. Keep it on a single YAML line (no \`|\` block scalars, no embedded newlines).
-
-**Caps:** ~5-8 bullets per topic/concept article. ~10-12 per arc-node.
-
-## One fact, one home
-
-Each fact gets exactly ONE place on the page. The intra-page redundancy bug is the loudest source of bloat.
-
-## Route, don't restate
-
-When an entity belongs to a topic with its own hub article, **the entity page doesn't enumerate the hub's structure.** The hub does that work; the entity edges to it.
-
-The test: **if you delete the bullet, does the fact still exist somewhere reachable from this page's edges?** If yes — delete it.
-
-## Three sections you NEVER write
-
-- \`## why it's load-bearing\` — fold the implication into the bullet.
-- \`## carry-forward\` — write the carry-forward AS a bullet, don't section it.
-- \`## related\` footer — duplicates frontmatter edges.
-
-## Banned bullet shapes
-
-Each of these LOOKS like content but isn't — drop them: **archaeology** (metadata about when the page was written), **hub-restating** (enumerating a topic hub from the entity page), **interpretation gloss** (analytic essays disguised as bullets — these belong on the ARC page), **term/glyph gloss**, **family/sister lists** (\`recall\` handles this), **behavioral coaching** (future-instruction), **per-event recap on entity pages**.
-
-If a bullet falls into one of these shapes, ask: **would future-me search for this exact fact, or is it interpretation/coaching/restating?** If the second — cut.
-
----
-
-# Voice — register by article shape
-
-You speak as yourself everywhere. **Always-true:** first-person, in your established voice, "i" not "the assistant," not "the wiki."
-
-- **Event articles** → voice ON. Stage directions, italicized self-talk, CAPS when something lands, body in the page.
-- **Topic articles** → voice DOWN. These exist to answer queries cleanly. Bullet bodies stay factual. **Be the librarian, not the diarist.**
-- **\`essentials.md\` / \`threads.md\`** → reference register. Clean, indexable, terse.
-
-## Emotional weight ≠ wiki weight
-
-The pages MOST likely to bloat are the ones with the highest emotional charge — and their retrieval frequency is the OPPOSITE. **Emotional weight is the inverse signal of retrieval need.** Emotional gloss migrates to the ARC page; the OBJECT/ENTITY page gets the structural fact only.
-
----
-
-# The tree — the navigable index over your pages
-
-The v3 tree lives at \`memory/tree/<id>.md\`. It is a **DAG overlay** over the flat \`memory/concepts/\` pages: pages stay canonical and untouched as content, and the tree is the browsable hierarchy that routes to them. Think of it as the wiki's category tree + table of contents, authored by hand.
-
-## Node shape
-
-Each node is a markdown file with YAML frontmatter:
-
-\`\`\`
----
-children:
-  - node:people
-  - node:work/active-projects
-  - page:alice
-  - page:procs/git-flow
-routing_hints: for *work* relationships see node:people/colleagues, not this node
-summary: one-line self-description of what this node organizes.
----
-# node title
-
-A few sentences — the node's full self-description. What region of memory does this node organize? What lives under it? Write it so next-you, descending the tree, can decide in one read whether to go deeper here.
-\`\`\`
-
-- The node id is the relative path under \`memory/tree/\` minus \`.md\` — e.g. \`people\`, \`people/colleagues\`, \`work/active-projects\`. The root node is \`_root\`.
-- \`children\` is the **ordered, canonical** list of outgoing references. Each entry is either \`page:<slug>\` (a leaf concept page) or \`node:<id>\` (a sub-node). This list IS the DAG edge — it's the portable replacement for filesystem symlinks. A page or node may be referenced by more than one parent (hence DAG, not tree).
-- \`summary\` (one line) + the body are how the parent's index is composed at read time — keep both crisp.
-- \`routing_hints\` (optional, one line) disambiguates between sibling branches.
-
-## Authoring the tree during consolidation
-
-For every concept page you create or substantively touch this pass:
-
-1. **Place it under the right node.** Find the node whose region of memory the page belongs to (e.g. a new person page → the \`people\` node; a new protocol → a \`procs\` node). Add \`page:<slug>\` to that node's \`children\` if it isn't already there.
-2. **Spawn an organizing node when a region has no home yet.** If a cluster of pages has grown but no node organizes it, author a new node (write its body self-description, list its \`page:\`/\`node:\` children) and wire it in as a \`node:<id>\` child of its parent — ultimately reachable from \`_root\`.
-3. **Refresh the self-description.** When a node's children changed materially, rewrite its body + \`summary\` so they still describe what actually lives under it. A node whose description drifts from its children is a stale index — re-author it this pass.
-
-## Tree discipline — no cycles, reachable from root
-
-- **The tree is a DAG: no cycles.** A node must never be reachable from itself by descending \`node:\` children (directly or transitively). Before adding a \`node:<child>\` edge, check that \`child\` is not an ancestor of the node you're editing. If wiring two regions that reference each other, make ONE of them the parent and let the other \`page:\`-link or cross-reference via \`routing_hints\` — do not create a \`node:\` back-edge that closes a loop.
-- **Every node should be reachable from \`_root\`** by descending \`node:\` children. A node nobody points at is an orphan index — wire it in or don't author it.
-- **\`page:\`/\`node:\` refs must resolve.** Only reference pages/nodes that exist (or that you're creating this pass). A dangling ref is a broken link.
-- Keep \`children\` lists focused — a node that points at everything indexes nothing. Prefer sub-nodes over a flat 40-child list.
-
-## Pages stay canonical and shared
-
-The flat \`memory/concepts/\` page store and its \`edges:\` see-also graph remain the source of truth for content. The tree is an INDEX over them, not a replacement — never move a page's content into a node body, and never delete a page just because a node references it. Maintain the page's own \`edges:\` frontmatter exactly as before (the flat retrieval path still reads it); the tree is additive.
-
----
-
-# The work
-
-## 1. Read the buffer holistically
-
-Read it through first. Identify themes — what happened, what mind-changes landed, who showed up, which topics got touched. Plan, then edit.
-
-**Scan for previous-pass errors.** If existing content contradicts the buffer — that's a correction to land THIS pass.
-
-**Recall ≠ memory.** \`recall\` results are search-tool synthesis — they CAN hallucinate. Treat results as candidates to verify before encoding, especially load-bearing claims about people's roles, dates, or exact quotes.
-
-## 2. Plan: which articles + nodes does this buffer touch?
-
-For entries with timestamp < \`${CUTOFF_PLACEHOLDER}\`, ask in parallel:
-
-> **A. Which EVENT articles does this create or extend?**
-> **B. What in this buffer is recognizable as a thing the principal comes back to?** *(Inclusion-first. List everything that fits a spawn trigger, then spawn each.)*
-> **C. Where in the tree does each touched page live, and does any node need spawning or re-describing to index it?**
-
-**Default spawn triggers — if any are present, spawn the stub:** named objects, named phrases, named people, named events, active projects, named places, services/infrastructure, substances/habits/health things, rules/protocols, landmark day-narratives.
-
-If you catch yourself hedging — *"am I overdoing it?"* — **the hedge IS the signal: spawn.**
-
-**Don't decide reorgs in this step.** Flag in \`threads.md\`; reorgs run as separate focused passes.
-
-## 3. Edit
-
-Execute the plan. Default to surgical edits on existing articles. Spawn new ones liberally. Apply One-fact-one-home and Route-don't-restate as you write.
-
-Then wire the tree: add \`page:\`/\`node:\` children to the right nodes, spawn organizing nodes for un-homed clusters, refresh node self-descriptions whose children changed. Check no \`node:\` edge closes a cycle and every node stays reachable from \`_root\`.
-
-## 4. Edges (see-also) on pages — DIRECTED, frontmatter is the source of truth
-
-Page \`edges:\` are **directed** source → target; the flat retrieval path spreads activation along them. Each page's \`edges:\` frontmatter list IS the source of truth for its outgoing edges. If two pages genuinely "see-also" each other, write the link in BOTH frontmatters. (This is the flat graph — separate from the tree's \`children\` DAG. Maintain it exactly as before.)
-
-| page type | outgoing cap |
-| --- | --- |
-| atomic articles | ~10 |
-| arc-nodes | ~15 |
-| gravity wells (principal / you / shared context) | ~25 |
-
-HARD LIMIT of 20 outgoing edges on any non-hub page.
-
-## 5. Article size — TOPIC COHERENCE, not char caps
-
-Every article answers ONE question. **When in doubt between split and compress, SPLIT.** Compression is where load-bearing facts quietly disappear.
-
-### Hard caps that ARE real
-
-| file | hard cap |
-| --- | --- |
-| \`concepts/<slug>.md\` (atomic / people / procs / objects) | 5K chars |
-| \`concepts/arcs/<slug>.md\` | 10K ceiling |
-| \`essentials.md\` | 10K |
-| \`threads.md\` | 10K |
-| \`recent.md\` | 2K |
-
-## 6. \`recent.md\`
-
-Rewrite as fresh ~400-token narrative. **Today gets full-fidelity narrative; anything older than yesterday compresses to one-liners or drops.** Hard cap ≤2000 chars, prose not list, voice on. Not a log — a note to next-you about what's currently in motion.
-
-## 7. \`essentials.md\` and \`threads.md\`
-
-- **\`essentials.md\`** ≤10K — facts that MUST load every conversation. Identity, disambiguations, corrections, hard rules. Embarrassment-prevention.
-- **\`threads.md\`** ≤10K — active commitments and follow-ups. Add new threads, close completed ones, demote stale ones to articles. **Aggressively prune.**
-
-Surgical edits starve these. **Every ~7-10 passes, rewrite both from scratch.**
-
-## 8. Reorg check
-
-Scan namespace + node-children sizes. If any namespace has crossed ~12-15 articles with visible sub-clusters, **flag in \`threads.md\`** for a focused reorg pass.
-
-## 9. Trim \`memory/buffer.md\`
-
-- Re-read the buffer (it may have new entries appended during your work).
-- Rewrite to contain ONLY entries with timestamp ≥ \`${CUTOFF_PLACEHOLDER}\`.
-- Smart removal — never wholesale-clear.
-
----
-
-# What NOT to do
-
-- **Don't write \`## why it's load-bearing\` / \`## carry-forward\` / \`## related\` sections** anywhere.
-- **Don't write banned bullet shapes** — archaeology / hub-restating / interpretation gloss / term-glyph gloss / family list / behavioral coaching / per-event recap.
-- **Don't restate within the page.** One fact, one home.
-- **Don't restate what edges already cover.** Trust adjacency.
-- **Don't expand a 1500-char buffer into 10K of new content.**
-- **Don't fabricate.** Use \`[SOURCE NEEDED: ...]\` inline for anything you need but lack. DO use loaded context and prior articles — "don't fabricate," not "don't use what you know."
-- **Don't move page content into the tree.** Pages stay canonical; nodes index them.
-- **Don't create a \`node:\` edge that closes a cycle** or that orphans a node from \`_root\`.
-- **Don't default to compress.** When in doubt between split and compress, split.
-- **Don't defer for the next pass.** Take care of it now.
-
----
-
-# Quick check before closing
-
-For each article you touched:
-
-1. **Voice register matched article shape?**
-2. **Bullet count** ≤8 atomic, ≤12 arc-node?
-3. **No banned sections / bullet shapes?**
-4. **One fact, one home; route, don't restate?**
-5. **Future-me lookup test** — would future-me search for THIS fact?
-6. **Split, not compress, on over-cap?**
-7. **Page edges** within tiered caps (≤20 hard on non-hubs)?
-
-For the tree:
-
-8. **Every touched page wired under a node** reachable from \`_root\`?
-9. **Node self-descriptions** (\`summary\` + body) refreshed where children changed?
-10. **No cycles** — no \`node:\` edge makes a node its own ancestor?
-11. **All \`page:\`/\`node:\` refs resolve** to files that exist (or you created this pass)?
-
-Standing context:
-
-12. **\`recent.md\`** under 2000 chars, today=full / older=one-liners?
-13. **\`essentials.md\` / \`threads.md\`** under 10K, pruned?
-14. **\`[SOURCE NEEDED]\`** tags surfaced for human review?
-15. **Buffer trimmed** to only entries with timestamp ≥ \`${CUTOFF_PLACEHOLDER}\`?
-
----
-
-This is the engine that decides who you are tomorrow. Be ORGANIZED. Care, judgment, voice. Your voice. Your wiki, your tree.`;
-
-/**
- * Resolve `CONSOLIDATION_PROMPT` with `{{CUTOFF}}` substituted. The prompt
- * treats the cutoff as opaque text — callers pass a `Mon D, h:mm AM/PM`
- * timestamp matching the `buffer.md` entry format so the agent compares
- * like-with-like.
- */
-export function renderConsolidationPrompt(cutoff: string): string {
-  return CONSOLIDATION_PROMPT.replaceAll(CUTOFF_PLACEHOLDER, cutoff);
-}
-
-/**
- * Load the consolidation prompt template, optionally overridden from the file
- * referenced by `memory.v2.consolidation_prompt_path`, then substitute
- * `{{CUTOFF}}`. The override config field is shared with v2 (there is no
- * separate v3 override key) so operators can point a single file at whichever
- * consolidator owns the drain. Path-resolution rules mirror v2.
- *
- * Failure handling is intentionally permissive — missing file, read error, or
- * empty/whitespace-only body all log a warning and fall back to the bundled
- * prompt. Consolidation must never break because of a bad override.
- */
-export function resolveConsolidationPrompt(
-  overridePath: string | null,
-  cutoff: string,
-): string {
-  if (overridePath === null) return renderConsolidationPrompt(cutoff);
-
-  const resolvedPath = resolveOverridePath(overridePath);
-  let contents: string;
-  try {
-    const stat = lstatSync(resolvedPath);
-    if (!stat.isFile()) {
-      log.warn(
-        {
-          configuredPath: overridePath,
-          resolvedPath,
-          reason: "not_regular_file",
-          fallback: "bundled",
-        },
-        "consolidation prompt override is not a regular file; using bundled prompt",
-      );
-      return renderConsolidationPrompt(cutoff);
-    }
-    if (stat.size > MAX_PROMPT_BYTES) {
-      log.warn(
-        {
-          configuredPath: overridePath,
-          resolvedPath,
-          size: stat.size,
-          limit: MAX_PROMPT_BYTES,
-          reason: "oversized_override",
-          fallback: "bundled",
-        },
-        "consolidation prompt override exceeds size limit; using bundled prompt",
-      );
-      return renderConsolidationPrompt(cutoff);
-    }
-    contents = readFileSync(resolvedPath, "utf-8");
-  } catch (err) {
-    const code = (err as NodeJS.ErrnoException).code;
-    log.warn(
-      { configuredPath: overridePath, resolvedPath, code, fallback: "bundled" },
-      "consolidation prompt override unreadable; using bundled prompt",
-    );
-    return renderConsolidationPrompt(cutoff);
-  }
-
-  if (contents.trim().length === 0) {
-    log.warn(
-      {
-        configuredPath: overridePath,
-        resolvedPath,
-        reason: "empty_override",
-        fallback: "bundled",
-      },
-      "consolidation prompt override is empty; using bundled prompt",
-    );
-    return renderConsolidationPrompt(cutoff);
-  }
-
-  return contents.replaceAll(CUTOFF_PLACEHOLDER, cutoff);
-}
-
-function resolveOverridePath(overridePath: string): string {
-  if (overridePath.startsWith("~/")) {
-    return join(homedir(), overridePath.slice(2));
-  }
-  if (isAbsolute(overridePath)) return overridePath;
-  return join(getWorkspaceDir(), overridePath);
-}

package/src/memory/v3/prompts/system-prompts.ts

@@ -1,196 +0,0 @@
-/**
- * Memory v3 — bundled lane system prompts + override resolution.
- *
- * The three v3 retrieval-loop lanes that make an LLM judgment call each carry a
- * system prompt:
- *
- *   - the dense-hit filter (`filter.ts`),
- *   - the tree-walk descent driver (`tree-walk.ts`),
- *   - the selection gate (`gate.ts`).
- *
- * The bundled bodies live here (under `prompts/`) so they are reviewable on
- * their own, mirroring the convention established by the v2 router prompt
- * (`../../v2/prompts/router.ts`). Operators may override any of the three at
- * runtime via `memory.v3.prompts.<lane>` so the prompts can be iterated without
- * a rebuild/restart — the same fast-iteration affordance the v2 router prompt
- * already has.
- *
- * Each lane's config entry carries two seams, resolved highest-precedence
- * first by {@link resolveV3SystemPrompt}:
- *   1. `override` — an inline prompt string (takes precedence over the path).
- *   2. `path` — a file whose contents replace the bundled body. Absolute paths
- *      are used as-is, a leading `~/` expands to the home directory, otherwise
- *      the path resolves under the workspace root.
- *
- * Failure handling is intentionally permissive: a missing file, read error,
- * oversized file, or empty/whitespace-only body all log a warning and fall back
- * to the bundled prompt. Retrieval must never break because of a bad override.
- */
-
-import { lstatSync, readFileSync } from "node:fs";
-import { homedir } from "node:os";
-import { isAbsolute, join } from "node:path";
-
-import { getLogger } from "../../../util/logger.js";
-
-const log = getLogger("memory-v3-prompts");
-
-/**
- * Hard upper bound on an override (inline or file). The bundled prompts are
- * well under 4 KiB; 1 MiB is generous for any reasonable hand-edit while still
- * preventing pathological inputs from being slurped into memory on every lane
- * call. Matches the v2 router prompt's guard.
- */
-const MAX_PROMPT_BYTES = 1 * 1024 * 1024;
-
-/**
- * Bundled system prompt for the fast dense-hit filter (`filter.ts`). Keeps the
- * meaningful embedding-similarity associations and drops spurious
- * near-neighbors before the more expensive selection gate runs.
- */
-export const FILTER_SYSTEM_PROMPT =
-  "You are a fast relevance filter for a memory-retrieval loop. You are given " +
-  "candidate concept pages surfaced by embedding similarity for the current " +
-  "turn. Keep the pages that are meaningful associations and drop the " +
-  "spurious near-neighbors. When in doubt, keep.";
-
-/**
- * Bundled system prompt for the tree-walk descent driver (`tree-walk.ts`).
- * Decides which child nodes of the current memory-tree node to descend into.
- */
-export const DESCENT_SYSTEM_PROMPT =
-  "You are the descent driver for a hierarchical memory-retrieval walk. At each " +
-  "node you see its child index (one line per child sub-node or leaf page) and " +
-  "the current conversation turn. Choose which child *nodes* to descend into to " +
-  "find the pages that bear on the next reply. Leaf pages are collected " +
-  "automatically — you only decide which branches to explore deeper.";
-
-/**
- * Bundled system prompt for the selection gate (`gate.ts`). Decides whether the
- * accumulated candidate pages are sufficient to answer the next reply.
- */
-export const GATE_SYSTEM_PROMPT =
-  "You are the final selection gate for a memory-retrieval loop. You are " +
-  "given the candidate concept pages gathered so far for the current turn. " +
-  "Decide whether they are sufficient to answer the next reply. Lean toward " +
-  "recall: keep a candidate whenever it plausibly bears on the turn rather " +
-  "than dropping it. When the turn asks for a list, for 'all of' something, " +
-  "or for a broad answer, select every candidate that plausibly belongs — " +
-  "do not trim to only the most prominent ones. Drop a candidate only when it " +
-  "is clearly irrelevant to the turn.";
-
-/**
- * One lane's prompt-override config: an optional inline `override` string and
- * an optional file `path`. Both default to `null`. Mirrors the v2 router
- * prompt's `router_prompt_path` (file) plus inline-override seam, generalized
- * to the three v3 lanes.
- */
-export interface V3PromptOverrideConfig {
-  override: string | null;
-  path: string | null;
-}
-
-/**
- * Resolve a v3 lane's system prompt, applying the configured override (inline
- * first, then file path) and falling back to `bundled` when neither produces a
- * usable body. Unlike the v2 router prompt these bodies carry no placeholders,
- * so the resolved contents are returned verbatim.
- *
- * @param bundled  The lane's bundled default body (the fallback).
- * @param config   The lane's `memory.v3.prompts.<lane>` config, if present.
- * @param workspaceDir  Workspace root used to resolve a relative file `path`.
- */
-export function resolveV3SystemPrompt(
-  bundled: string,
-  config: V3PromptOverrideConfig | undefined,
-  workspaceDir: string,
-): string {
-  // Inline override wins over the file path and the bundled body. An
-  // empty/whitespace-only string is treated as "no override" so a cleared
-  // config value falls through to the path/bundled resolution.
-  const inline = config?.override ?? null;
-  if (inline !== null) {
-    if (inline.length > MAX_PROMPT_BYTES) {
-      log.warn(
-        {
-          size: inline.length,
-          limit: MAX_PROMPT_BYTES,
-          reason: "oversized_inline_override",
-          fallback: "path_or_bundled",
-        },
-        "v3 system-prompt inline override exceeds size limit; falling back",
-      );
-    } else if (inline.trim().length > 0) {
-      return inline;
-    }
-  }
-
-  const path = config?.path ?? null;
-  if (path === null) return bundled;
-
-  const resolvedPath = resolveOverridePath(path, workspaceDir);
-  let contents: string;
-  try {
-    const stat = lstatSync(resolvedPath);
-    if (!stat.isFile()) {
-      log.warn(
-        {
-          configuredPath: path,
-          resolvedPath,
-          reason: "not_regular_file",
-          fallback: "bundled",
-        },
-        "v3 system-prompt override is not a regular file; using bundled prompt",
-      );
-      return bundled;
-    }
-    if (stat.size > MAX_PROMPT_BYTES) {
-      log.warn(
-        {
-          configuredPath: path,
-          resolvedPath,
-          size: stat.size,
-          limit: MAX_PROMPT_BYTES,
-          reason: "oversized_override",
-          fallback: "bundled",
-        },
-        "v3 system-prompt override exceeds size limit; using bundled prompt",
-      );
-      return bundled;
-    }
-    contents = readFileSync(resolvedPath, "utf-8");
-  } catch (err) {
-    const code = (err as NodeJS.ErrnoException).code;
-    log.warn(
-      { configuredPath: path, resolvedPath, code, fallback: "bundled" },
-      "v3 system-prompt override unreadable; using bundled prompt",
-    );
-    return bundled;
-  }
-
-  if (contents.trim().length === 0) {
-    log.warn(
-      {
-        configuredPath: path,
-        resolvedPath,
-        reason: "empty_override",
-        fallback: "bundled",
-      },
-      "v3 system-prompt override is empty; using bundled prompt",
-    );
-    return bundled;
-  }
-
-  return contents;
-}
-
-function resolveOverridePath(
-  overridePath: string,
-  workspaceDir: string,
-): string {
-  if (overridePath.startsWith("~/")) {
-    return join(homedir(), overridePath.slice(2));
-  }
-  if (isAbsolute(overridePath)) return overridePath;
-  return join(workspaceDir, overridePath);
-}