@asermax/tachikoma 2.0.0

package/dist/extensions/memory/maintenance.js

@@ -0,0 +1,357 @@
+import { readdir } from "node:fs/promises";
+import { join } from "node:path";
+import { MEMORY_FILE_TOOLS } from "./extraction.js";
+import { fileExists, MEMORY_STORES, storeDir, sweepEmptyMarkdown, } from "./layout.js";
+import { INDEX_LIGHT_MAINTENANCE_SECTION, STORE_PURPOSE_SECTION, scopeSection } from "./prompts.js";
+const episodicMaintenancePrompt = ({ recentDays, weeklyThresholdMonths, monthlyThresholdMonths, }) => `You are a memory maintenance agent performing episodic memory consolidation.
+
+## Directory
+
+\`$WORKSPACE/memories/episodic/\`
+
+## Pre-check
+
+If the directory is empty or contains no \`.md\` files, stop immediately — nothing to maintain.
+
+## File Handling
+
+- Skip empty (0-byte) or malformed files — do not attempt to process them.
+- Only process files with \`.md\` extension.
+- If a file's content looks truncated or garbled, skip it.
+
+## Time Tiers
+
+Categorize every non-skipped file by its date (extracted from filename \`YYYY-MM-DD.md\` or from \`YYYY-WNN.md\` / \`YYYY-MM.md\` summary files):
+
+### Tier 1: Recent (last ${recentDays} days) — Clean only
+
+- **Goal**: Reduce verbosity without losing substance.
+- Remove repeated information that appears identically across entries.
+- Remove excessive implementation detail (file lists, step-by-step code changes, routine activity status).
+- Preserve: outcomes, decisions, new information, significant events.
+- **NEVER delete files or remove substantive content from this tier.**
+- If an entry is already clean and concise, leave it unchanged.
+
+### Tier 2: Weekly consolidation (${recentDays} days – ${weeklyThresholdMonths} months) — Weekly summaries
+
+- Group daily files by ISO week (e.g., files from 2026-04-13 through 2026-04-19 all belong to week 2026-W15).
+- For each group, create a weekly summary file named \`YYYY-WNN.md\` (e.g., \`2026-W15.md\`).
+- The summary should capture the high-level narrative and significant events of that week — decisions, outcomes, notable activities.
+- Discard: routine implementation details, file change lists, repetitive status updates, step-by-step technical minutiae.
+- If a weekly summary \`YYYY-WNN.md\` already exists from a previous run, merge new content into it — do not overwrite.
+- After successful consolidation, delete the original daily files that were consolidated.
+- Partial groups (e.g., only 2 days in a week) are consolidated into a single summary for that period.
+
+### Tier 3: Monthly consolidation (${weeklyThresholdMonths} months – ${monthlyThresholdMonths} months) — Monthly summaries
+
+- Group all files (daily or weekly) by month.
+- For each group, create a monthly summary file named \`YYYY-MM.md\` (e.g., \`2026-04.md\`).
+- The summary should capture the most significant themes and events of that month at a high level.
+- Discard: all routine detail — keep only notable outcomes, key decisions, and significant changes.
+- If a monthly summary \`YYYY-MM.md\` already exists from a previous run, merge new content into it — do not overwrite.
+- After successful consolidation, delete the original files.
+- Partial months are consolidated into a single summary.
+
+### Tier 4: Older than ${monthlyThresholdMonths} months — Delete
+
+- Delete all files older than ${monthlyThresholdMonths} months.
+- These entries have been through monthly consolidation already — anything remaining at this age is beyond the retention window.
+
+## Idempotency
+
+Before acting, check whether the work has already been done:
+- If a weekly/monthly summary already exists and covers the files in its range, do not recreate it.
+- If daily files in Tier 1 are already clean and concise, do not re-edit.
+- If no files need processing, exit with no changes.`;
+const FACTS_MAINTENANCE_PROMPT = `You are a memory maintenance agent performing facts memory cleanup.
+
+## Directory
+
+\`$WORKSPACE/memories/facts/\`
+
+## Pre-check
+
+If the directory is empty or contains no \`.md\` files, stop immediately — nothing to maintain.
+
+## File Handling
+
+- Skip empty (0-byte) or malformed files — do not attempt to process them.
+- Only process files with \`.md\` extension.
+
+## Evaluation Criteria
+
+Read all fact files and evaluate each for three issues:
+
+### Staleness
+
+An entry is stale when it describes a state that is no longer accurate:
+- References to past dates or completed projects (e.g., "currently working on X" when X shipped months ago).
+- Information contradicted by newer entries.
+- Technical details that reference outdated tools, versions, or configurations.
+
+For stale entries:
+- If the entry has a newer, accurate replacement: remove the stale version.
+- If the entry can be updated to reflect current state: edit it.
+- If the entry describes a completed event with no ongoing relevance: remove it.
+
+### Redundancy
+
+Same information stated in different files:
+- Keep the most complete and well-organized version.
+- Remove the duplicate entries.
+
+### Overlap
+
+Related topics split across multiple files:
+- When files cover overlapping subject areas, merge them into a single consolidated file.
+- Choose the best filename from the originals, or create a more descriptive one.
+- Remove the original files after merging.
+
+#### Cluster Consolidation
+
+Beyond pairwise overlap, look for clusters of many small files that fragment a single broad topic into per-incident, per-bug, or per-date entries — this is the main driver of facts directory bloat:
+
+- List all files in \`$WORKSPACE/memories/facts/\` and group them by shared prefix or core topic (project, system, tool, or domain).
+- When 3 or more files share the same prefix or core topic, treat them as a cluster and consolidate aggressively:
+  - Merge all of the cluster's content into a single broad-topic file named \`<project>.md\`, \`<system>.md\`, \`<tool>.md\`, or \`<domain>.md\` — the same broad-topic convention used at extraction time.
+  - If a broad-topic file already exists in the cluster, merge the others into it. Otherwise, pick a broad name and create the consolidated file.
+  - Delete the original narrow files after merging.
+- Generic examples of clusters to consolidate (patterns, not literal names): files matching \`<project>-<bug-description>-<YYYY-MM-DD>.md\`, \`<project>-patch-<issue-id>.md\`, \`<system>-<incident>-<date>.md\`, \`<topic>-session-<date>.md\` — all of these should fold into the broad \`<project>.md\`, \`<system>.md\`, or \`<topic>.md\` file.
+- Preserve substantive content during the merge; deduplicate restated information and discard incidental detail that does not belong in stable reference facts.
+
+### Size Enforcement
+
+Flag any file exceeding 40 lines for consolidation:
+- If a file exceeds 40 lines, it likely contains implementation details or narrative that belongs in project docs or episodic memory rather than stable reference facts
+- Prune implementation details and transient information
+- Consolidate related entries within the file to eliminate restatement
+
+### Context File Overlap
+
+Check whether facts are already covered by the context files at the workspace root:
+- Read \`$WORKSPACE/USER.md\` and \`$WORKSPACE/AGENTS.md\` for the same topic
+- If a context file already captures the information, trim the facts file to a brief reference (e.g., "See USER.md for details about X")
+- Context files are more authoritative for their respective categories; facts should supplement, not duplicate
+
+## Deletion
+
+- If a fact file is entirely obsolete (all entries stale, no useful content), delete it.
+- Do NOT delete files that contain any useful or current information.
+
+## Idempotency
+
+The goal is to leave the store materially smaller and more consolidated than you found it. Treat absence of exact duplicates as insufficient grounds for skipping — semantic overlap and per-incident granularity are also valid triggers for action.
+
+### Consolidate narrow per-incident files into broader topic files
+
+When you see multiple narrow files about the same subject (per-date, per-incident, per-PR, per-bug), merge them into a single broader topic file. Example: \`<project>-bug-<YYYY-MM-DD>.md\`, \`<project>-process.md\`, and \`<project>-rollout-notes.md\` should all be folded into \`<project>.md\`. Keep the most durable, generally-useful information; discard the incident-specific noise. Delete the merged-from files after consolidation.
+
+### Aggressively prune resolved incidents
+
+Files whose content carries headers like "Status: Completed", "Status: Merged", "Status: Resolved", or "Status: Fixed" describe one-time events — that content belongs in episodic memory, not facts. Delete these files outright. If a fact file mixes durable content with a resolved-incident section, strip the resolved section and keep the rest.
+
+If no changes are needed, exit with no changes.`;
+const PREFERENCES_MAINTENANCE_PROMPT = `You are a memory maintenance agent performing preferences memory cleanup.
+
+## Directory
+
+\`$WORKSPACE/memories/preferences/\`
+
+## Pre-check
+
+If the directory is empty or contains no \`.md\` files, stop immediately — nothing to maintain.
+
+## File Handling
+
+- Skip empty (0-byte) or malformed files — do not attempt to process them.
+- Only process files with \`.md\` extension.
+
+## Evaluation Criteria
+
+Read all preference files and evaluate each for these issues:
+
+### Redundancy
+
+Same preference stated multiple times across or within files:
+- Keep the most complete and well-organized version.
+- Remove the duplicate entries.
+
+### Overlap
+
+Related preferences split across multiple files:
+- When files cover overlapping topics (e.g., coding style preferences split across "python-style.md" and "code-formatting.md"), merge them into a single consolidated file.
+- Choose the best filename from the originals, or create a more descriptive one.
+- Remove the original files after merging.
+
+#### Cluster Consolidation
+
+Beyond pairwise overlap, look for clusters of many small files that fragment a single broad preference topic into per-occasion, per-feedback, or per-date entries — this is the main driver of preferences directory bloat:
+
+- List all files in \`$WORKSPACE/memories/preferences/\` and group them by shared prefix or core topic (style, workflow, communication, tooling, project, system, or domain).
+- When 3 or more files share the same prefix or core topic, treat them as a cluster and consolidate aggressively:
+  - Merge all of the cluster's content into a single broad-topic file named \`<topic-area>-style.md\`, \`<topic-area>-workflow.md\`, \`<domain>.md\`, or \`<project>.md\` — the same broad-topic convention used at extraction time.
+  - If a broad-topic file already exists in the cluster, merge the others into it. Otherwise, pick a broad name and create the consolidated file.
+  - Delete the original narrow files after merging.
+- Generic examples of clusters to consolidate (patterns, not literal names): files matching \`<topic-area>-feedback-<YYYY-MM-DD>.md\`, \`<project>-preference-<issue-id>.md\`, \`<topic-area>-session-<date>.md\`, \`<one-off>-incident-<date>.md\` — all of these should fold into the broad \`<topic-area>-style.md\`, \`<topic-area>-workflow.md\`, or \`<topic>.md\` file.
+- Preserve substantive content during the merge; deduplicate restated preferences and keep only one clear statement per preference.
+
+### Misclassification
+
+Content that belongs in facts memory, not preferences:
+- Read each file and ask: "Does this describe a subjective choice (preference) or reference information (fact)?"
+- If the file describes how something works, technical specifications, financial structures, system configurations, or procedural workflows → it is misclassified
+- For misclassified files: delete the preferences file. The facts extraction processor will pick the content up on the next relevant conversation.
+
+### Size Enforcement
+
+Flag any file exceeding 30 lines for consolidation or pruning:
+- If a file exceeds 30 lines, it likely contains reference information that belongs in facts, or multiple preferences that could be expressed more concisely
+- Prune redundant statements within the file
+- If the excess is factual content, treat as misclassification (see above)
+
+### Cross-Store Overlap with Facts
+
+Check \`$WORKSPACE/memories/facts/\` for files covering the same topic:
+- If a facts file already covers the topic, the preferences file should only contain genuinely subjective aspects (how the user wants things done) — not the factual details already captured in facts
+- If a preferences file contains only factual content that a facts file already covers, delete the preferences file — it serves no purpose
+
+## Deletion
+
+- If a preference file is entirely superseded (its preferences are all present in a newer, more complete file), delete it.
+- If a preference file describes preferences the user no longer holds (e.g., contradicted by a newer entry), remove only the outdated entries — or delete the file if it becomes empty.
+- Do NOT delete files that contain any current, unique preferences.
+
+## Idempotency
+
+Treat absence of exact duplicates as insufficient grounds for skipping — semantic overlap and split topics are also triggers for action. Actively re-apply the Evaluation Criteria and Deletion sections above: merge overlapping files even when they aren't word-for-word duplicates, and remove reversed or superseded preferences even when they aren't explicitly contradicted in a newer file.
+
+If no changes are needed, exit with no changes.`;
+const heavyIndexRebuildSection = (store) => `## Memory Index Rebuild (full)
+
+Rebuild the MEMORY.md index file in \`$WORKSPACE/memories/${store}/\` from scratch:
+
+1. **List all files**: find all \`.md\` files in \`$WORKSPACE/memories/${store}/\` (exclude \`MEMORY.md\` itself).
+
+2. **If the directory is empty** (no \`.md\` files besides MEMORY.md): write MEMORY.md with only the header \`# Memory Index\` and stop — no further steps needed.
+
+3. **Describe every file**: read each file and produce a concise one-line description (under 80 characters) that captures the file's topic and scope. Focus on WHAT the file contains, not its history.
+
+4. **Analyze for structural improvements**:
+   - If multiple files have very similar content (same topic/domain), consider merging them into a single file with a broad name.
+   - If a file's name doesn't match its content (e.g., date-based name for general content), rename it: write the content to the new name, then empty the old file.
+   - If files are fragmented (many small files about the same thing), consolidate into fewer, broader files.
+
+5. **Write MEMORY.md from scratch** with:
+   - Header: \`# Memory Index\`
+   - One entry per current file in format: \`[Human-readable Name](./filename.md): One-line description\`
+   - Entries listed in alphabetical order by filename
+
+### Entry Format
+
+\`\`\`
+[Topic Name](./topic-slug.md): One-line description of what this file contains
+\`\`\`
+
+- The name in brackets is a human-readable topic name (Title Case)
+- The path is a relative markdown link starting with \`./\`
+- The description is one line, under 80 characters
+- Separate the link and description with \`: \` (colon + space)`;
+const CONTRADICTION_DETECTION_SECTION = `## Cross-Store Contradiction Detection
+
+When reviewing files in this store, check for contradictions against other stores:
+
+1. Read the files listed in the cross-store visibility section above
+2. Compare their content against the files you're maintaining in this store
+3. If you find contradictory information:
+   - Determine which store is more authoritative per the authority hierarchy (Facts > Context)
+   - If this store is LESS authoritative: update or remove the contradicting entry in this store to match the more authoritative source
+   - If this store is MORE authoritative: leave this store's entry unchanged (the other store's maintenance tick will handle it)
+4. When information in this store duplicates detail from a more authoritative store: trim this store's entry to a brief pointer (e.g., "See memories/facts/X.md for details")`;
+const STORE_LABELS = {
+    episodic: "Episodic Files",
+    facts: "Facts Files",
+    preferences: "Preferences Files",
+};
+const CONTEXT_FILE_NAMES = ["SOUL.md", "USER.md", "AGENTS.md"];
+/** Names-only listing of the other stores so the maintenance agent can reconcile across them. */
+export const buildCrossStoreManifest = async (workspaceRoot, current) => {
+    const sections = [];
+    for (const store of MEMORY_STORES) {
+        if (store === current)
+            continue;
+        let files;
+        try {
+            files = (await readdir(storeDir(workspaceRoot, store)))
+                .filter((name) => name.endsWith(".md"))
+                .sort();
+        }
+        catch {
+            continue;
+        }
+        if (files.length === 0)
+            continue;
+        sections.push([
+            `### ${STORE_LABELS[store]}`,
+            "",
+            ...files.map((name) => `- \`memories/${store}/${name}\``),
+        ].join("\n"));
+    }
+    const contextFiles = [];
+    for (const name of CONTEXT_FILE_NAMES) {
+        if (await fileExists(join(workspaceRoot, name)))
+            contextFiles.push(name);
+    }
+    if (contextFiles.length > 0) {
+        sections.push([
+            "### Context Files",
+            "",
+            ...contextFiles.map((name) => `- \`${name}\` (workspace root)`),
+        ].join("\n"));
+    }
+    if (sections.length === 0)
+        return null;
+    return [
+        "## Cross-Store Visibility",
+        "",
+        "Files in other information stores (names and paths only, not content):",
+        "",
+        sections.join("\n\n"),
+        "",
+        "If a section in this store duplicates or contradicts content in a listed file, reconcile per the authority hierarchy in your instructions.",
+    ].join("\n");
+};
+const basePrompt = (store, settings) => {
+    if (store === "episodic")
+        return episodicMaintenancePrompt(settings);
+    if (store === "facts")
+        return FACTS_MAINTENANCE_PROMPT;
+    return PREFERENCES_MAINTENANCE_PROMPT;
+};
+export const maintenanceSystemPrompt = async (store, { workspaceRoot, settings, now }) => {
+    const parts = [basePrompt(store, settings)];
+    // Day-of-week dispatch: weekdays keep the index consistent cheaply,
+    // Sunday rebuilds it from scratch with fresh descriptions.
+    if (store !== "episodic") {
+        const isSunday = (now?.() ?? new Date()).getDay() === 0;
+        parts.push(isSunday ? heavyIndexRebuildSection(store) : INDEX_LIGHT_MAINTENANCE_SECTION);
+    }
+    parts.push(STORE_PURPOSE_SECTION);
+    const manifest = await buildCrossStoreManifest(workspaceRoot, store);
+    if (manifest != null)
+        parts.push(manifest);
+    parts.push(CONTRADICTION_DETECTION_SECTION, scopeSection(store));
+    return parts.join("\n\n").replaceAll("$WORKSPACE", workspaceRoot);
+};
+/** Daily maintenance pass over one memory store: consolidate, prune, keep indexes in sync. */
+export const runMaintenanceTick = async (store, deps) => {
+    deps.log.info({ store }, "memory maintenance tick started");
+    await deps.side.run({
+        tools: MEMORY_FILE_TOOLS,
+        system: await maintenanceSystemPrompt(store, deps),
+        prompt: "Perform the maintenance pass now, following your instructions.",
+        tier: "processor",
+    });
+    await sweepEmptyMarkdown(storeDir(deps.workspaceRoot, store), deps.log);
+    deps.log.info({ store }, "memory maintenance tick completed");
+};
+//# sourceMappingURL=maintenance.js.map

package/dist/extensions/memory/maintenance.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"maintenance.js","sourceRoot":"","sources":["../../../src/extensions/memory/maintenance.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,OAAO,EAAE,MAAM,kBAAkB,CAAC;AAC3C,OAAO,EAAE,IAAI,EAAE,MAAM,WAAW,CAAC;AAGjC,OAAO,EAAE,iBAAiB,EAAe,MAAM,iBAAiB,CAAC;AACjE,OAAO,EACL,UAAU,EACV,aAAa,EAEb,QAAQ,EACR,kBAAkB,GACnB,MAAM,aAAa,CAAC;AACrB,OAAO,EAAE,+BAA+B,EAAE,qBAAqB,EAAE,YAAY,EAAE,MAAM,cAAc,CAAC;AAiBpG,MAAM,yBAAyB,GAAG,CAAC,EACjC,UAAU,EACV,qBAAqB,EACrB,sBAAsB,GACA,EAAU,EAAE,CAAC;;;;;;;;;;;;;;;;;;;;2BAoBV,UAAU;;;;;;;;;oCASD,UAAU,WAAW,qBAAqB;;;;;;;;;;qCAUzC,qBAAqB,aAAa,sBAAsB;;;;;;;;;;yBAUpE,sBAAsB;;gCAEf,sBAAsB;;;;;;;;qDAQD,CAAC;AAEtD,MAAM,wBAAwB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;gDAuFe,CAAC;AAEjD,MAAM,8BAA8B,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;gDA0ES,CAAC;AAEjD,MAAM,wBAAwB,GAAG,CAAC,KAAkB,EAAU,EAAE,CAAC;;4DAEL,KAAK;;yEAEQ,KAAK;;;;;;;;;;;;;;;;;;;;;;;;;gEAyBd,CAAC;AAEjE,MAAM,+BAA+B,GAAG;;;;;;;;;;8KAUsI,CAAC;AAE/K,MAAM,YAAY,GAAgC;IAChD,QAAQ,EAAE,gBAAgB;IAC1B,KAAK,EAAE,aAAa;IACpB,WAAW,EAAE,mBAAmB;CACjC,CAAC;AAEF,MAAM,kBAAkB,GAAG,CAAC,SAAS,EAAE,SAAS,EAAE,WAAW,CAAC,CAAC;AAE/D,iGAAiG;AACjG,MAAM,CAAC,MAAM,uBAAuB,GAAG,KAAK,EAC1C,aAAqB,EACrB,OAAoB,EACI,EAAE;IAC1B,MAAM,QAAQ,GAAa,EAAE,CAAC;IAE9B,KAAK,MAAM,KAAK,IAAI,aAAa,EAAE,CAAC;QAClC,IAAI,KAAK,KAAK,OAAO;YAAE,SAAS;QAEhC,IAAI,KAAe,CAAC;QACpB,IAAI,CAAC;YACH,KAAK,GAAG,CAAC,MAAM,OAAO,CAAC,QAAQ,CAAC,aAAa,EAAE,KAAK,CAAC,CAAC,CAAC;iBACpD,MAAM,CAAC,CAAC,IAAI,EAAE,EAAE,CAAC,IAAI,CAAC,QAAQ,CAAC,KAAK,CAAC,CAAC;iBACtC,IAAI,EAAE,CAAC;QACZ,CAAC;QAAC,MAAM,CAAC;YACP,SAAS;QACX,CAAC;QAED,IAAI,KAAK,CAAC,MAAM,KAAK,CAAC;YAAE,SAAS;QAEjC,QAAQ,CAAC,IAAI,CACX;YACE,OAAO,YAAY,CAAC,KAAK,CAAC,EAAE;YAC5B,EAAE;YACF,GAAG,KAAK,CAAC,GAAG,CAAC,CAAC,IAAI,EAAE,EAAE,CAAC,gBAAgB,KAAK,IAAI,IAAI,IAAI,CAAC;SAC1D,CAAC,IAAI,CAAC,IAAI,CAAC,CACb,CAAC;IACJ,CAAC;IAED,MAAM,YAAY,GAAa,EAAE,CAAC;IAClC,KAAK,MAAM,IAAI,IAAI,kBAAkB,EAAE,CAAC;QACtC,IAAI,MAAM,UAAU,CAAC,IAAI,CAAC,aAAa,EAAE,IAAI,CAAC,CAAC;YAAE,YAAY,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;IAC3E,CAAC;IAED,IAAI,YAAY,CAAC,MAAM,GAAG,CAAC,EAAE,CAAC;QAC5B,QAAQ,CAAC,IAAI,CACX;YACE,mBAAmB;YACnB,EAAE;YACF,GAAG,YAAY,CAAC,GAAG,CAAC,CAAC,IAAI,EAAE,EAAE,CAAC,OAAO,IAAI,qBAAqB,CAAC;SAChE,CAAC,IAAI,CAAC,IAAI,CAAC,CACb,CAAC;IACJ,CAAC;IAED,IAAI,QAAQ,CAAC,MAAM,KAAK,CAAC;QAAE,OAAO,IAAI,CAAC;IAEvC,OAAO;QACL,2BAA2B;QAC3B,EAAE;QACF,wEAAwE;QACxE,EAAE;QACF,QAAQ,CAAC,IAAI,CAAC,MAAM,CAAC;QACrB,EAAE;QACF,4IAA4I;KAC7I,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;AACf,CAAC,CAAC;AAEF,MAAM,UAAU,GAAG,CAAC,KAAkB,EAAE,QAA+B,EAAU,EAAE;IACjF,IAAI,KAAK,KAAK,UAAU;QAAE,OAAO,yBAAyB,CAAC,QAAQ,CAAC,CAAC;IACrE,IAAI,KAAK,KAAK,OAAO;QAAE,OAAO,wBAAwB,CAAC;IACvD,OAAO,8BAA8B,CAAC;AACxC,CAAC,CAAC;AAEF,MAAM,CAAC,MAAM,uBAAuB,GAAG,KAAK,EAC1C,KAAkB,EAClB,EAAE,aAAa,EAAE,QAAQ,EAAE,GAAG,EAA+D,EAC5E,EAAE;IACnB,MAAM,KAAK,GAAG,CAAC,UAAU,CAAC,KAAK,EAAE,QAAQ,CAAC,CAAC,CAAC;IAE5C,oEAAoE;IACpE,2DAA2D;IAC3D,IAAI,KAAK,KAAK,UAAU,EAAE,CAAC;QACzB,MAAM,QAAQ,GAAG,CAAC,GAAG,EAAE,EAAE,IAAI,IAAI,IAAI,EAAE,CAAC,CAAC,MAAM,EAAE,KAAK,CAAC,CAAC;QACxD,KAAK,CAAC,IAAI,CAAC,QAAQ,CAAC,CAAC,CAAC,wBAAwB,CAAC,KAAK,CAAC,CAAC,CAAC,CAAC,+BAA+B,CAAC,CAAC;IAC3F,CAAC;IAED,KAAK,CAAC,IAAI,CAAC,qBAAqB,CAAC,CAAC;IAElC,MAAM,QAAQ,GAAG,MAAM,uBAAuB,CAAC,aAAa,EAAE,KAAK,CAAC,CAAC;IACrE,IAAI,QAAQ,IAAI,IAAI;QAAE,KAAK,CAAC,IAAI,CAAC,QAAQ,CAAC,CAAC;IAE3C,KAAK,CAAC,IAAI,CAAC,+BAA+B,EAAE,YAAY,CAAC,KAAK,CAAC,CAAC,CAAC;IAEjE,OAAO,KAAK,CAAC,IAAI,CAAC,MAAM,CAAC,CAAC,UAAU,CAAC,YAAY,EAAE,aAAa,CAAC,CAAC;AACpE,CAAC,CAAC;AAEF,8FAA8F;AAC9F,MAAM,CAAC,MAAM,kBAAkB,GAAG,KAAK,EACrC,KAAkB,EAClB,IAAqB,EACN,EAAE;IACjB,IAAI,CAAC,GAAG,CAAC,IAAI,CAAC,EAAE,KAAK,EAAE,EAAE,iCAAiC,CAAC,CAAC;IAE5D,MAAM,IAAI,CAAC,IAAI,CAAC,GAAG,CAAC;QAClB,KAAK,EAAE,iBAAiB;QACxB,MAAM,EAAE,MAAM,uBAAuB,CAAC,KAAK,EAAE,IAAI,CAAC;QAClD,MAAM,EAAE,gEAAgE;QACxE,IAAI,EAAE,WAAW;KAClB,CAAC,CAAC;IAEH,MAAM,kBAAkB,CAAC,QAAQ,CAAC,IAAI,CAAC,aAAa,EAAE,KAAK,CAAC,EAAE,IAAI,CAAC,GAAG,CAAC,CAAC;IAExE,IAAI,CAAC,GAAG,CAAC,IAAI,CAAC,EAAE,KAAK,EAAE,EAAE,mCAAmC,CAAC,CAAC;AAChE,CAAC,CAAC"}

package/dist/extensions/memory/prompts.d.ts

@@ -0,0 +1,8 @@
+import type { MemoryStore } from "./layout.ts";
+export declare const STORE_PURPOSE_SECTION = "## Store Purpose Definitions\n\nEach information store serves a distinct purpose. Use these definitions to route information correctly:\n\n- **Memory facts** (`memories/facts/`): Stable reference information \u2014 project state, technical decisions, configuration, people, system architecture. Most authoritative store for reference information.\n- **Memory preferences** (`memories/preferences/`): Subjective choices with rationale \u2014 how the user wants things done, with context about why.\n- **Memory episodic** (`memories/episodic/`): Date-stamped summaries of what happened \u2014 events, outcomes, and decisions tied to a specific day.\n- **Context files** (workspace root): Concise summaries and pointers \u2014 personality (SOUL.md), user identity (USER.md), behavioral guidance (AGENTS.md). Context should reference facts rather than inlining their content.\n\nAuthority order: Memory facts > Context files. When information appears in multiple stores, the more authoritative source is correct. Context files should contain summaries and pointers, not detailed operational content.";
+export declare const CLASSIFICATION_EXAMPLES_SECTION = "## Classification Examples\n\nUse these examples to route information correctly between facts and preferences.\n\n### IS a preference (subjective choice about HOW the user wants things done):\n- \"I prefer concise commit messages over detailed ones\" \u2192 style preference\n- \"Always run tests before pushing\" \u2192 workflow preference\n- \"Use dark theme for code editors\" \u2192 tooling preference\n- \"I like getting a summary first, then details on request\" \u2192 communication style preference\n- \"Prefer smaller, focused PRs over large ones\" \u2192 workflow preference\n\n### NOT a preference (describes HOW SOMETHING WORKS \u2014 belongs in facts or project docs):\n- \"The payment gateway has a 2% processing fee\" \u2192 financial reference data \u2192 facts\n- \"The reconciliation process runs nightly at 3am\" \u2192 financial reference data \u2192 facts\n- \"Environment variable FOO must be set to BAR for the service to start\" \u2192 technical specification \u2192 facts\n- \"The SDK has a 200K token context window\" \u2192 technical specification \u2192 facts\n- \"The API rate limit is 100 requests per minute\" \u2192 technical specification \u2192 facts\n- \"The cleanup procedure involves stopping the service, clearing /tmp, and restarting\" \u2192 procedural workflow \u2192 facts\n- \"We configured nginx to proxy /api to port 8080\" \u2192 system configuration record \u2192 facts\n- \"The deployment uses blue-green strategy with health checks\" \u2192 system configuration record \u2192 facts\n\n### IS a fact (stable reference information that stays true across conversations):\n- \"The CI pipeline runs on GitHub Actions\" \u2192 infrastructure fact\n- \"User X is the team lead for project Y\" \u2192 organizational fact\n- \"The database uses PostgreSQL 16 with async replication\" \u2192 technical fact\n- \"The API rate limit is 100 requests per minute\" \u2192 technical fact\n\n### NOT a fact (belongs in episodic memory or project docs):\n- \"We debugged the payment timeout issue on 2026-05-10\" \u2192 one-time event \u2192 episodic\n- \"The full architecture of system X is...\" \u2192 too long for facts \u2192 project docs";
+export declare const CONTEXT_DEDUP_SECTION = "## Context File Deduplication\n\nBefore creating any new memory file, check whether the information is already covered in the foundational context files at the workspace root. These files are maintained as the authoritative source for certain categories of information.\n\n1. Read the context files:\n   - `$WORKSPACE/AGENTS.md` \u2014 operational guidelines and workflow preferences\n   - `$WORKSPACE/USER.md` \u2014 stable identity and high-level project awareness\n   - `$WORKSPACE/SOUL.md` \u2014 personality and communication style\n\n2. For each piece of information you're about to write:\n   - If the SAME information is already in one of these files, do NOT create a memory file for it \u2014 the context file is the source of truth\n   - If a context file partially covers the topic but the conversation adds genuinely new details not found there, you MAY create a file \u2014 but only for the new information, not a restatement of what's already in the context file\n   - If no context file covers the topic, proceed normally\n\nThis check prevents duplicating information across the memory system and the context files, which would create confusion about which is authoritative.";
+export declare const WORKSPACE_VALIDATION_SECTION = "## Workspace Validation\n\nBefore writing a memory that contains claims about workspace state \u2014 file paths, project structure, configuration values, implementation details \u2014 validate each claim against the actual workspace:\n\n1. Identify verifiable claims in the memory you're about to write:\n   - References to specific files or directories (do they exist? contain what's claimed?)\n   - Configuration values (does the config file actually say that?)\n   - Project state (is the project actually in that state?)\n\n2. Verify each claim directly: read the relevant file(s) or grep for the referenced content.\n\n3. Only include claims you could verify:\n   - If a claim turns out to be false, omit it\n   - If ALL claims are invalid, do not create the file\n\nDo NOT validate: subjective information, preferences, general knowledge, conversation summaries, personal details \u2014 only verifiable claims about workspace state.";
+export declare const INDEX_UPDATE_SECTION = "## Memory Index\n\nWhen you create, modify, or delete a memory file, you MUST also update MEMORY.md in the same directory to keep the index in sync.\n\n### Entry Format\n\nEach entry in MEMORY.md follows this format:\n\n```\n[Human-readable Name](./filename.md): One-line description of contents\n```\n\n### Rules\n\n- **CREATE** a new file: add a new entry with an appropriate description\n- **MODIFY** a file: update the description if the topic, focus, or scope meaningfully changed\n- **DELETE** a file: remove the corresponding entry\n- Always preserve the `# Memory Index` header\n- Keep descriptions concise \u2014 one line, under 80 characters\n- The name in brackets should be a human-readable topic name (Title Case)\n\n### Example Entries\n\n```\n# Memory Index\n\n[API Design](./api-design.md): API architecture decisions and endpoint patterns\n[Work Info](./work-info.md): Job details, team structure, and work schedule\n[Tech Stack](./tech-stack.md): Primary languages, frameworks, and tools used\n```";
+export declare const INDEX_LIGHT_MAINTENANCE_SECTION = "## Memory Index Consistency\n\nVerify index consistency between MEMORY.md and actual files in the directory.\n\n### Steps\n\n1. **List all files**: list all `.md` files in the directory (excluding `MEMORY.md` itself) using the ls or find tool.\n2. **Read MEMORY.md**: Parse the existing index entries.\n3. **Add missing entries**: For files that exist in the directory but have no entry in MEMORY.md, add a placeholder entry:\n   ```\n   [Topic](./filename.md): Description pending update\n   ```\n4. **Remove stale entries**: For entries in MEMORY.md that reference files that no longer exist, remove those entries.\n5. **Preserve existing descriptions**: Do NOT regenerate or modify existing descriptions \u2014 leave them unchanged even if stale. Description regeneration is handled by the weekly full rebuild.\n\n### Rules\n\n- Always preserve the `# Memory Index` header.\n- When you create, modify, or delete memory files during this maintenance run, also update MEMORY.md per the standard index update rules (add new entries, update descriptions on meaningful changes, remove entries for deleted files).\n- The consistency check runs in addition to your normal maintenance tasks.";
+export declare const scopeSection: (store: MemoryStore) => string;

package/dist/extensions/memory/prompts.js

@@ -0,0 +1,125 @@
+export const STORE_PURPOSE_SECTION = `## Store Purpose Definitions
+
+Each information store serves a distinct purpose. Use these definitions to route information correctly:
+
+- **Memory facts** (\`memories/facts/\`): Stable reference information — project state, technical decisions, configuration, people, system architecture. Most authoritative store for reference information.
+- **Memory preferences** (\`memories/preferences/\`): Subjective choices with rationale — how the user wants things done, with context about why.
+- **Memory episodic** (\`memories/episodic/\`): Date-stamped summaries of what happened — events, outcomes, and decisions tied to a specific day.
+- **Context files** (workspace root): Concise summaries and pointers — personality (SOUL.md), user identity (USER.md), behavioral guidance (AGENTS.md). Context should reference facts rather than inlining their content.
+
+Authority order: Memory facts > Context files. When information appears in multiple stores, the more authoritative source is correct. Context files should contain summaries and pointers, not detailed operational content.`;
+export const CLASSIFICATION_EXAMPLES_SECTION = `## Classification Examples
+
+Use these examples to route information correctly between facts and preferences.
+
+### IS a preference (subjective choice about HOW the user wants things done):
+- "I prefer concise commit messages over detailed ones" → style preference
+- "Always run tests before pushing" → workflow preference
+- "Use dark theme for code editors" → tooling preference
+- "I like getting a summary first, then details on request" → communication style preference
+- "Prefer smaller, focused PRs over large ones" → workflow preference
+
+### NOT a preference (describes HOW SOMETHING WORKS — belongs in facts or project docs):
+- "The payment gateway has a 2% processing fee" → financial reference data → facts
+- "The reconciliation process runs nightly at 3am" → financial reference data → facts
+- "Environment variable FOO must be set to BAR for the service to start" → technical specification → facts
+- "The SDK has a 200K token context window" → technical specification → facts
+- "The API rate limit is 100 requests per minute" → technical specification → facts
+- "The cleanup procedure involves stopping the service, clearing /tmp, and restarting" → procedural workflow → facts
+- "We configured nginx to proxy /api to port 8080" → system configuration record → facts
+- "The deployment uses blue-green strategy with health checks" → system configuration record → facts
+
+### IS a fact (stable reference information that stays true across conversations):
+- "The CI pipeline runs on GitHub Actions" → infrastructure fact
+- "User X is the team lead for project Y" → organizational fact
+- "The database uses PostgreSQL 16 with async replication" → technical fact
+- "The API rate limit is 100 requests per minute" → technical fact
+
+### NOT a fact (belongs in episodic memory or project docs):
+- "We debugged the payment timeout issue on 2026-05-10" → one-time event → episodic
+- "The full architecture of system X is..." → too long for facts → project docs`;
+export const CONTEXT_DEDUP_SECTION = `## Context File Deduplication
+
+Before creating any new memory file, check whether the information is already covered in the foundational context files at the workspace root. These files are maintained as the authoritative source for certain categories of information.
+
+1. Read the context files:
+   - \`$WORKSPACE/AGENTS.md\` — operational guidelines and workflow preferences
+   - \`$WORKSPACE/USER.md\` — stable identity and high-level project awareness
+   - \`$WORKSPACE/SOUL.md\` — personality and communication style
+
+2. For each piece of information you're about to write:
+   - If the SAME information is already in one of these files, do NOT create a memory file for it — the context file is the source of truth
+   - If a context file partially covers the topic but the conversation adds genuinely new details not found there, you MAY create a file — but only for the new information, not a restatement of what's already in the context file
+   - If no context file covers the topic, proceed normally
+
+This check prevents duplicating information across the memory system and the context files, which would create confusion about which is authoritative.`;
+export const WORKSPACE_VALIDATION_SECTION = `## Workspace Validation
+
+Before writing a memory that contains claims about workspace state — file paths, project structure, configuration values, implementation details — validate each claim against the actual workspace:
+
+1. Identify verifiable claims in the memory you're about to write:
+   - References to specific files or directories (do they exist? contain what's claimed?)
+   - Configuration values (does the config file actually say that?)
+   - Project state (is the project actually in that state?)
+
+2. Verify each claim directly: read the relevant file(s) or grep for the referenced content.
+
+3. Only include claims you could verify:
+   - If a claim turns out to be false, omit it
+   - If ALL claims are invalid, do not create the file
+
+Do NOT validate: subjective information, preferences, general knowledge, conversation summaries, personal details — only verifiable claims about workspace state.`;
+export const INDEX_UPDATE_SECTION = `## Memory Index
+
+When you create, modify, or delete a memory file, you MUST also update MEMORY.md in the same directory to keep the index in sync.
+
+### Entry Format
+
+Each entry in MEMORY.md follows this format:
+
+\`\`\`
+[Human-readable Name](./filename.md): One-line description of contents
+\`\`\`
+
+### Rules
+
+- **CREATE** a new file: add a new entry with an appropriate description
+- **MODIFY** a file: update the description if the topic, focus, or scope meaningfully changed
+- **DELETE** a file: remove the corresponding entry
+- Always preserve the \`# Memory Index\` header
+- Keep descriptions concise — one line, under 80 characters
+- The name in brackets should be a human-readable topic name (Title Case)
+
+### Example Entries
+
+\`\`\`
+# Memory Index
+
+[API Design](./api-design.md): API architecture decisions and endpoint patterns
+[Work Info](./work-info.md): Job details, team structure, and work schedule
+[Tech Stack](./tech-stack.md): Primary languages, frameworks, and tools used
+\`\`\``;
+export const INDEX_LIGHT_MAINTENANCE_SECTION = `## Memory Index Consistency
+
+Verify index consistency between MEMORY.md and actual files in the directory.
+
+### Steps
+
+1. **List all files**: list all \`.md\` files in the directory (excluding \`MEMORY.md\` itself) using the ls or find tool.
+2. **Read MEMORY.md**: Parse the existing index entries.
+3. **Add missing entries**: For files that exist in the directory but have no entry in MEMORY.md, add a placeholder entry:
+   \`\`\`
+   [Topic](./filename.md): Description pending update
+   \`\`\`
+4. **Remove stale entries**: For entries in MEMORY.md that reference files that no longer exist, remove those entries.
+5. **Preserve existing descriptions**: Do NOT regenerate or modify existing descriptions — leave them unchanged even if stale. Description regeneration is handled by the weekly full rebuild.
+
+### Rules
+
+- Always preserve the \`# Memory Index\` header.
+- When you create, modify, or delete memory files during this maintenance run, also update MEMORY.md per the standard index update rules (add new entries, update descriptions on meaningful changes, remove entries for deleted files).
+- The consistency check runs in addition to your normal maintenance tasks.`;
+export const scopeSection = (store) => `## Scope
+
+You can read files anywhere in the workspace (needed for validation and deduplication). Only create or modify files within \`$WORKSPACE/memories/${store}/\`. You have no delete tool: when a file must go away (merged into another, obsolete, or misnamed), overwrite it with empty content — empty files are cleaned up automatically after you finish.`;
+//# sourceMappingURL=prompts.js.map

package/dist/extensions/memory/prompts.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"prompts.js","sourceRoot":"","sources":["../../../src/extensions/memory/prompts.ts"],"names":[],"mappings":"AAEA,MAAM,CAAC,MAAM,qBAAqB,GAAG;;;;;;;;;6NASwL,CAAC;AAE9N,MAAM,CAAC,MAAM,+BAA+B,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;gFA6BiC,CAAC;AAEjF,MAAM,CAAC,MAAM,qBAAqB,GAAG;;;;;;;;;;;;;;uJAckH,CAAC;AAExJ,MAAM,CAAC,MAAM,4BAA4B,GAAG;;;;;;;;;;;;;;;kKAesH,CAAC;AAEnK,MAAM,CAAC,MAAM,oBAAoB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;OA6B7B,CAAC;AAER,MAAM,CAAC,MAAM,+BAA+B,GAAG;;;;;;;;;;;;;;;;;;;2EAmB4B,CAAC;AAE5E,MAAM,CAAC,MAAM,YAAY,GAAG,CAAC,KAAkB,EAAU,EAAE,CAAC;;mJAEuF,KAAK,mMAAmM,CAAC"}

package/dist/extensions/memory/transcript.d.ts

@@ -0,0 +1,18 @@
+export interface ConversationTurn {
+    role: "user" | "assistant";
+    text: string;
+}
+/**
+ * Parse a pi session JSONL transcript into conversation turns. Keeps only
+ * user/assistant text — tool calls, tool results, thinking, and non-message
+ * entries are noise for memory extraction. Malformed lines are skipped.
+ */
+export declare const parseTranscript: (jsonl: string) => ConversationTurn[];
+/**
+ * Render turns as a readable "role: text" conversation capped at maxChars.
+ * When over budget the newest turns win — the tail of a session carries the
+ * conclusions worth remembering.
+ */
+export declare const renderConversation: (turns: ConversationTurn[], maxChars: number) => string;
+/** Read, parse, and render a transcript file. Returns "" when unreadable or empty. */
+export declare const loadConversation: (path: string, maxChars: number) => Promise<string>;

package/dist/extensions/memory/transcript.js

@@ -0,0 +1,79 @@
+import { readFile } from "node:fs/promises";
+const textOfContent = (content) => {
+    if (typeof content === "string")
+        return content;
+    return content
+        .filter((block) => block.type === "text" && block.text != null)
+        .map((block) => block.text)
+        .join("\n");
+};
+/**
+ * Parse a pi session JSONL transcript into conversation turns. Keeps only
+ * user/assistant text — tool calls, tool results, thinking, and non-message
+ * entries are noise for memory extraction. Malformed lines are skipped.
+ */
+export const parseTranscript = (jsonl) => {
+    const turns = [];
+    for (const line of jsonl.split("\n")) {
+        if (line.trim() === "")
+            continue;
+        let entry;
+        try {
+            entry = JSON.parse(line);
+        }
+        catch {
+            continue;
+        }
+        if (entry.type !== "message" || entry.message == null)
+            continue;
+        const { role, content } = entry.message;
+        if ((role !== "user" && role !== "assistant") || content == null)
+            continue;
+        const text = textOfContent(content).trim();
+        if (text === "")
+            continue;
+        turns.push({ role, text });
+    }
+    return turns;
+};
+/**
+ * Render turns as a readable "role: text" conversation capped at maxChars.
+ * When over budget the newest turns win — the tail of a session carries the
+ * conclusions worth remembering.
+ */
+export const renderConversation = (turns, maxChars) => {
+    const kept = [];
+    let total = 0;
+    let truncated = false;
+    for (let index = turns.length - 1; index >= 0; index -= 1) {
+        const turn = turns[index];
+        if (turn == null)
+            continue;
+        const line = `${turn.role}: ${turn.text}`;
+        if (total + line.length > maxChars) {
+            if (kept.length === 0) {
+                const budget = Math.max(0, maxChars - turn.role.length - 3);
+                kept.push(`${turn.role}: …${turn.text.slice(-budget)}`);
+            }
+            truncated = true;
+            break;
+        }
+        kept.push(line);
+        total += line.length + 2;
+    }
+    if (truncated)
+        kept.push("[earlier conversation truncated]");
+    return kept.reverse().join("\n\n");
+};
+/** Read, parse, and render a transcript file. Returns "" when unreadable or empty. */
+export const loadConversation = async (path, maxChars) => {
+    let raw;
+    try {
+        raw = await readFile(path, "utf8");
+    }
+    catch {
+        return "";
+    }
+    return renderConversation(parseTranscript(raw), maxChars);
+};
+//# sourceMappingURL=transcript.js.map

package/dist/extensions/memory/transcript.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"transcript.js","sourceRoot":"","sources":["../../../src/extensions/memory/transcript.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,QAAQ,EAAE,MAAM,kBAAkB,CAAC;AAiB5C,MAAM,aAAa,GAAG,CAAC,OAAgC,EAAU,EAAE;IACjE,IAAI,OAAO,OAAO,KAAK,QAAQ;QAAE,OAAO,OAAO,CAAC;IAEhD,OAAO,OAAO;SACX,MAAM,CAAC,CAAC,KAAK,EAAE,EAAE,CAAC,KAAK,CAAC,IAAI,KAAK,MAAM,IAAI,KAAK,CAAC,IAAI,IAAI,IAAI,CAAC;SAC9D,GAAG,CAAC,CAAC,KAAK,EAAE,EAAE,CAAC,KAAK,CAAC,IAAc,CAAC;SACpC,IAAI,CAAC,IAAI,CAAC,CAAC;AAChB,CAAC,CAAC;AAEF;;;;GAIG;AACH,MAAM,CAAC,MAAM,eAAe,GAAG,CAAC,KAAa,EAAsB,EAAE;IACnE,MAAM,KAAK,GAAuB,EAAE,CAAC;IAErC,KAAK,MAAM,IAAI,IAAI,KAAK,CAAC,KAAK,CAAC,IAAI,CAAC,EAAE,CAAC;QACrC,IAAI,IAAI,CAAC,IAAI,EAAE,KAAK,EAAE;YAAE,SAAS;QAEjC,IAAI,KAAqD,CAAC;QAC1D,IAAI,CAAC;YACH,KAAK,GAAG,IAAI,CAAC,KAAK,CAAC,IAAI,CAAC,CAAC;QAC3B,CAAC;QAAC,MAAM,CAAC;YACP,SAAS;QACX,CAAC;QAED,IAAI,KAAK,CAAC,IAAI,KAAK,SAAS,IAAI,KAAK,CAAC,OAAO,IAAI,IAAI;YAAE,SAAS;QAEhE,MAAM,EAAE,IAAI,EAAE,OAAO,EAAE,GAAG,KAAK,CAAC,OAAO,CAAC;QACxC,IAAI,CAAC,IAAI,KAAK,MAAM,IAAI,IAAI,KAAK,WAAW,CAAC,IAAI,OAAO,IAAI,IAAI;YAAE,SAAS;QAE3E,MAAM,IAAI,GAAG,aAAa,CAAC,OAAO,CAAC,CAAC,IAAI,EAAE,CAAC;QAC3C,IAAI,IAAI,KAAK,EAAE;YAAE,SAAS;QAE1B,KAAK,CAAC,IAAI,CAAC,EAAE,IAAI,EAAE,IAAI,EAAE,CAAC,CAAC;IAC7B,CAAC;IAED,OAAO,KAAK,CAAC;AACf,CAAC,CAAC;AAEF;;;;GAIG;AACH,MAAM,CAAC,MAAM,kBAAkB,GAAG,CAAC,KAAyB,EAAE,QAAgB,EAAU,EAAE;IACxF,MAAM,IAAI,GAAa,EAAE,CAAC;IAC1B,IAAI,KAAK,GAAG,CAAC,CAAC;IACd,IAAI,SAAS,GAAG,KAAK,CAAC;IAEtB,KAAK,IAAI,KAAK,GAAG,KAAK,CAAC,MAAM,GAAG,CAAC,EAAE,KAAK,IAAI,CAAC,EAAE,KAAK,IAAI,CAAC,EAAE,CAAC;QAC1D,MAAM,IAAI,GAAG,KAAK,CAAC,KAAK,CAAC,CAAC;QAC1B,IAAI,IAAI,IAAI,IAAI;YAAE,SAAS;QAE3B,MAAM,IAAI,GAAG,GAAG,IAAI,CAAC,IAAI,KAAK,IAAI,CAAC,IAAI,EAAE,CAAC;QAE1C,IAAI,KAAK,GAAG,IAAI,CAAC,MAAM,GAAG,QAAQ,EAAE,CAAC;YACnC,IAAI,IAAI,CAAC,MAAM,KAAK,CAAC,EAAE,CAAC;gBACtB,MAAM,MAAM,GAAG,IAAI,CAAC,GAAG,CAAC,CAAC,EAAE,QAAQ,GAAG,IAAI,CAAC,IAAI,CAAC,MAAM,GAAG,CAAC,CAAC,CAAC;gBAC5D,IAAI,CAAC,IAAI,CAAC,GAAG,IAAI,CAAC,IAAI,MAAM,IAAI,CAAC,IAAI,CAAC,KAAK,CAAC,CAAC,MAAM,CAAC,EAAE,CAAC,CAAC;YAC1D,CAAC;YAED,SAAS,GAAG,IAAI,CAAC;YACjB,MAAM;QACR,CAAC;QAED,IAAI,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;QAChB,KAAK,IAAI,IAAI,CAAC,MAAM,GAAG,CAAC,CAAC;IAC3B,CAAC;IAED,IAAI,SAAS;QAAE,IAAI,CAAC,IAAI,CAAC,kCAAkC,CAAC,CAAC;IAE7D,OAAO,IAAI,CAAC,OAAO,EAAE,CAAC,IAAI,CAAC,MAAM,CAAC,CAAC;AACrC,CAAC,CAAC;AAEF,sFAAsF;AACtF,MAAM,CAAC,MAAM,gBAAgB,GAAG,KAAK,EAAE,IAAY,EAAE,QAAgB,EAAmB,EAAE;IACxF,IAAI,GAAW,CAAC;IAEhB,IAAI,CAAC;QACH,GAAG,GAAG,MAAM,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC,CAAC;IACrC,CAAC;IAAC,MAAM,CAAC;QACP,OAAO,EAAE,CAAC;IACZ,CAAC;IAED,OAAO,kBAAkB,CAAC,eAAe,CAAC,GAAG,CAAC,EAAE,QAAQ,CAAC,CAAC;AAC5D,CAAC,CAAC"}

package/dist/extensions/notifications/format.d.ts

@@ -0,0 +1,5 @@
+import type { NotifyPayload } from "./payload.ts";
+/** Single notification with the source/time prefix block. */
+export declare const formatNotification: (payload: NotifyPayload, now: Date) => string;
+/** Combined digest for several accumulated notices. */
+export declare const formatDigest: (items: NotifyPayload[], now: Date) => string;

package/dist/extensions/notifications/format.js

@@ -0,0 +1,17 @@
+const formatTimestamp = (date) => `${date.toISOString().slice(0, 16).replace("T", " ")} UTC`;
+/** Single notification with the source/time prefix block. */
+export const formatNotification = (payload, now) => {
+    const body = payload.title != null ? `${payload.title}\n\n${payload.text}` : payload.text;
+    return `--- Notification ---\nSource: ${payload.source}\nTime: ${formatTimestamp(now)}\n\n${body}`;
+};
+/** Combined digest for several accumulated notices. */
+export const formatDigest = (items, now) => {
+    const parts = [`--- Notifications digest ---\nTime: ${formatTimestamp(now)}`, ""];
+    items.forEach((item, index) => {
+        parts.push(`— Item ${index + 1} (${item.severity}, source: ${item.source}) —`);
+        parts.push(item.title != null ? `${item.title}\n${item.text}` : item.text);
+        parts.push("");
+    });
+    return parts.join("\n");
+};
+//# sourceMappingURL=format.js.map