@psiclawops/hypermem 0.9.0 → 0.9.2

package/dist/trigger-registry.js

@@ -13,7 +13,7 @@ import { createHash } from 'node:crypto';
 export const TRIGGER_REGISTRY_VERSION = '1.0.0';
 /**
  * Default trigger registry for standard ACA collections.
- * Covers the core ACA offload use case from carol's spec.
+ * Covers the core ACA offload use case from agent6's spec.
  */
 export const TRIGGER_REGISTRY = [
     {
@@ -69,7 +69,7 @@ export const TRIGGER_REGISTRY = [
         ],
         maxTokens: 800,
         maxChunks: 2,
-        owner: 'alice',
+        owner: 'agent1',
         category: 'operations',
         description: 'Agent operational procedures: boot sequence, heartbeat, work queue, session startup',
     },
@@ -106,7 +106,7 @@ export const TRIGGER_REGISTRY = [
         ],
         maxTokens: 1500,
         maxChunks: 4,
-        owner: 'alice',
+        owner: 'agent1',
         category: 'memory',
         description: 'Decision history: past choices, previously agreed approaches, recalled context',
     },
@@ -132,7 +132,7 @@ export const TRIGGER_REGISTRY = [
         ],
         maxTokens: 1200,
         maxChunks: 3,
-        owner: 'alice',
+        owner: 'agent1',
         category: 'operations',
         description: 'Agent tooling reference: CLI commands, config paths, deployment procedures, quick reference',
     },

package/dist/types.d.ts

@@ -72,7 +72,7 @@ export type FactScope = 'agent' | 'session' | 'user';
 /**
  * Memory visibility levels:
  * - private:  Only the owning agent can read. Identity, SOUL, personal reflections.
- * - org:      Agents in the same org (e.g., alice's directors: Hank, Jack, Irene).
+ * - org:      Agents in the same org (e.g., agent1's directors: Pylon, Vigil, Plane).
  * - council:  All council seats can read.
  * - fleet:    Any agent in the fleet can read.
  */
@@ -646,7 +646,7 @@ export interface ProviderMessage {
  * to identify high-signal unprocessed messages.
  *
  * Stored in Redis (hm:{a}:s:{s}:cursor) with dual-write to SQLite for
- * durability across Redis eviction (bob Gate 2).
+ * durability across Redis eviction (agent2 Gate 2).
  */
 export interface SessionCursor {
     /** StoredMessage.id of the newest message included in the last window */

package/docs/MEMORY_MD_AUTHORING.md

@@ -123,14 +123,14 @@ A simple operating rule works well:
 Bad:
 
 ```md
-- Forge runs copilot-local/claude-sonnet-4.6
+- Agent runs provider/model-X
 ```
 
 Better:
 
 ```md
-- Forge standard model was copilot-local/claude-sonnet-4.6 as of 2026-04-11; recheck after provider routing changes
-  → memory_search("Forge standard model 2026-04-11 provider routing")
+- Agent standard model was provider/model-X as of YYYY-MM-DD; recheck after provider routing changes
+  → memory_search("agent standard model YYYY-MM-DD provider routing")
 ```
 
 ## Relationship to daily memory files

package/docs/ROADMAP.md

@@ -12,7 +12,15 @@ For shipped capabilities, see [CHANGELOG.md](../CHANGELOG.md) and [ARCHITECTURE.
 ## Current state
 
 ### Released
-- Current release: **0.8.6**
+- Current release: **0.9.0** — adaptive context lifecycle. Published 2026-04-25.
+  - Internal `main`: `8f805b8`
+  - Public `main`: `25dd469`
+  - Public tag `v0.9.0`: pushed
+  - Public CI: green (`24942512824`)
+  - GitHub Release: https://github.com/PsiClawOps/hypermem/releases/tag/v0.9.0
+  - npm at 0.9.0: `@psiclawops/hypermem`, `@psiclawops/hypercompositor`, `@psiclawops/hypermem-memory`
+  - New install validator shipped: `hypermem-doctor`
+- Previous release: **0.8.6**
 
 ### Landed on `main` after 0.8.6
 In the order work actually landed:
@@ -84,7 +92,7 @@ Final closeout work now complete:
 Rule going forward: do not reopen warm restore from historical planning notes. New warm-restore work needs a fresh defect, measurement gap, or roadmap item.
 
 ## 2. HyperMem 0.9.0 adaptive context lifecycle
-Status: **OPEN, release-candidate pending tag validation.**
+Status: **CLOSED — shipped 2026-04-25.** Public tag `v0.9.0` (`25dd469`), GitHub Release published, all three npm packages at 0.9.0. `hypermem-doctor` shipped as part of this release.
 
 The core runtime slices have landed: the pure adaptive lifecycle policy kernel, compose diagnostics wiring, afterTurn Redis gradient-cap wiring, adaptive recall breadth, adaptive eviction ordering, lifecycle telemetry, report tooling, forked-context lifecycle integration, and metadata-only topic-signal report classification. The first live telemetry baseline is populated; it shows steady/warmup behavior with zero lifecycle-band divergence, so no threshold tuning is warranted from the current evidence.
 
@@ -168,7 +176,7 @@ Phase 5 stays important, but it is not the next sprint until the higher-priority
 |---|---|---|
 | Runtime diagnostics API allowlist defect | ✅ CLOSED | Verified installed OpenClaw runtime can reach `memory-core/runtime-api.js`; re-open only with a fresh public-surface failure trace. |
 | Topic synthesis bridge defect | ✅ CLOSED | Fixed in `8b9f928`; CI `24917765384` passed. |
-| Adaptive context lifecycle (0.9.0) | 🟡 OPEN | Kernel, compose diagnostics, afterTurn gradient cap, recall breadth, eviction order, lifecycle telemetry, report tooling, forked-context integration, and topic-signal report classification are landed; vector coverage, first live lifecycle baseline, and the 0.9.0 topic-bearing compose evidence gate are closed; threshold tuning remains deferred until future live evidence warrants it. |
+| Adaptive context lifecycle (0.9.0) | ✅ SHIPPED | Released 2026-04-25 as 0.9.0. Threshold tuning remains deferred until future live evidence warrants it. |
 | Vector coverage repair gate | ✅ CLOSED | `embed-existing` now supports knowledge and eligibility-aware coverage reporting; production vectors reached facts 113/113, knowledge 85/85, episodes 30,121/30,121 eligible coverage on 2026-04-24. |
 | Contradiction-aware decay | 🟡 OPEN | Prevents stale-fact poisoning after architectural pivots. |
 | Turn DAG Phase 5 storage/perf | 🟡 OPEN | Important, but later than the items above. |
@@ -189,7 +197,8 @@ Phase 5 stays important, but it is not the next sprint until the higher-priority
 | Strict topic mode legacy NULL backfill | 🟡 DEFERRED | Wait for stable topic coverage before running the migration/backfill. |
 | ACA Step 4 retrieval stubs replace static files | 🔲 PENDING | Still relevant, but downstream of lifecycle/diagnostics stability. Do not start from older ACA notes. |
 | ACA Step 5 governance context assembly | 🔲 PENDING | Still relevant, but depends on Step 4. Do not start until Step 4 has an accepted implementation contract. |
-| Codex harness compatibility for HyperMem hooks | 🔲 TRIAGE | OpenClaw is generalizing the embedded executor (PI stays default; Codex is a registered plugin harness via `agents.defaults.embeddedHarness`). When a turn runs through the Codex harness, OpenClaw owns mirror transcript + tool dispatch but Codex owns the agent loop and native compaction. Investigate before any agent moves off PI: (1) whether HyperMem's `before_prompt_build`, `before_compaction`, `after_compaction`, `before_message_write`, `llm_input`, `llm_output`, `agent_end`, `after_tool_call` hooks fire with the same timing on Codex turns; (2) collision between HyperCompositor compaction and Codex native app-server compaction (need an explicit disable on one side or a coordination contract); (3) whether the locally mirrored transcript loses any content the indexer assumes is present; (4) `subagent` `context: "fork"` behavior when parent runs on Codex (parent JSONL is mirror, not source of truth); (5) keep `openai-codex/*` provider routes (PI under the hood) distinct from `codex/*` runtime selection (Codex harness). Pilot on one non-critical agent with `runtime: "codex"`, `fallback: "pi"` once the parity gap closes; do not adopt fleet-wide before then. Surfaced 2026-04-24 by ragesaq. |
+| Tokenjuice + HyperMem tool-result pipeline integration | 🔲 TRIAGE | OpenClaw 2026.4.24 ships `tokenjuice`, a deterministic rule-based tool-result pre-trim hook (collapses ANSI/build noise/repeated frames). It and HyperMem's size-based `tool_result_trim` both fire on tool results. Three integration concerns before fleet-wide enable: (1) **Hook ordering**: tokenjuice must run before HyperMem trim so HyperMem only collapses what tokenjuice cannot already remove deterministically. Reverse order wastes savings. (2) **Tool-artifact store**: HyperMem's L4 durable artifact store must capture the **untransformed** tool result, not the tokenjuice-trimmed one. The hook chain should pass `{ raw, transformed }` so artifacts get `raw` while message stream gets `transformed`. (3) **Telemetry**: unify `tool_result_trim_event` schema with `source: "tokenjuice" \| "hypermem"` and per-turn rollup so operators see one report. Sequencing: pilot tokenjuice standalone on one heavy-exec agent (HyperBuilder generator candidate) to measure rule-trim savings on our actual workloads before formalizing the contract. Do not write the contract before we have numbers. Surfaced 2026-04-25 during operator review. |
+| Codex harness compatibility for HyperMem hooks | 🔲 TRIAGE | OpenClaw is generalizing the embedded executor (PI stays default; Codex is a registered plugin harness via `agents.defaults.embeddedHarness`). When a turn runs through the Codex harness, OpenClaw owns mirror transcript + tool dispatch but Codex owns the agent loop and native compaction. Investigate before any agent moves off PI: (1) whether HyperMem's `before_prompt_build`, `before_compaction`, `after_compaction`, `before_message_write`, `llm_input`, `llm_output`, `agent_end`, `after_tool_call` hooks fire with the same timing on Codex turns; (2) collision between HyperCompositor compaction and Codex native app-server compaction (need an explicit disable on one side or a coordination contract); (3) whether the locally mirrored transcript loses any content the indexer assumes is present; (4) `subagent` `context: "fork"` behavior when parent runs on Codex (parent JSONL is mirror, not source of truth); (5) keep `openai-codex/*` provider routes (PI under the hood) distinct from `codex/*` runtime selection (Codex harness). Pilot on one non-critical agent with `runtime: "codex"`, `fallback: "pi"` once the parity gap closes; do not adopt fleet-wide before then. Surfaced 2026-04-24 during operator review. |
 
 ---
 

package/install.sh

@@ -18,6 +18,7 @@ CONFIG_FILE="$HOME/.openclaw/hypermem/config.json"
 ASSUME_YES=false
 SKIP_NPM=false
 SKIP_STAGE=false
+DRY_RUN=false
 
 usage() {
   cat <<EOF
@@ -32,6 +33,7 @@ Options:
   --runtime-dir <p>  staged OpenClaw runtime dir, default: ~/.openclaw/plugins/hypermem
   --skip-npm         use existing package in install dir
   --skip-stage       install package only, do not run hypermem-install
+  --dry-run          print planned actions without installing, staging, or writing config
   --help             show this help
 
 Environment overrides:
@@ -49,6 +51,7 @@ while [[ $# -gt 0 ]]; do
     --runtime-dir) RUNTIME_DIR="$2"; shift 2 ;;
     --skip-npm) SKIP_NPM=true; shift ;;
     --skip-stage) SKIP_STAGE=true; shift ;;
+    --dry-run) DRY_RUN=true; shift ;;
     --help|-h) usage; exit 0 ;;
     *) echo -e "${RED}Unknown option:${NC} $1" >&2; usage; exit 1 ;;
   esac
@@ -57,6 +60,7 @@ done
 info() { echo -e "  ${CYAN}→${NC} $*"; }
 success() { echo -e "  ${GREEN}✓${NC} $*"; }
 warn() { echo -e "  ${YELLOW}⚠${NC}  $*"; }
+dryrun() { echo -e "  ${YELLOW}DRY-RUN${NC} $*"; }
 die() { echo -e "  ${RED}✗${NC} $*" >&2; exit 1; }
 
 confirm() {
@@ -86,6 +90,10 @@ preflight() {
   command -v npm >/dev/null 2>&1 || die "npm is required"
   success "npm $(npm --version)"
 
+  if $DRY_RUN; then
+    warn "dry-run mode: no package install, runtime staging, config write, or gateway change will be performed"
+  fi
+
   if command -v openclaw >/dev/null 2>&1; then
     success "openclaw CLI found"
     openclaw gateway status >/dev/null 2>&1 || warn "OpenClaw gateway is not running or not onboarded yet. Complete OpenClaw setup before activation."
@@ -96,6 +104,12 @@ preflight() {
 
 install_package() {
   echo -e "\n${BOLD}  Package install${NC}"
+  if $DRY_RUN; then
+    dryrun "would create/install package directory: $INSTALL_DIR"
+    dryrun "would install package: $PACKAGE"
+    return
+  fi
+
   mkdir -p "$INSTALL_DIR"
   if [[ ! -f "$INSTALL_DIR/package.json" ]]; then
     info "initializing $INSTALL_DIR"
@@ -114,6 +128,11 @@ install_package() {
 }
 
 backup_runtime() {
+  if $DRY_RUN; then
+    dryrun "would check for existing runtime and optionally back up: $RUNTIME_DIR"
+    return 0
+  fi
+
   [[ -e "$RUNTIME_DIR" ]] || return 0
   local backup
   backup="${RUNTIME_DIR}.backup.$(date +%Y%m%d-%H%M%S)"
@@ -132,6 +151,11 @@ stage_runtime() {
     return
   fi
 
+  if $DRY_RUN; then
+    dryrun "would run runtime installer into: $RUNTIME_DIR"
+    return
+  fi
+
   local installer="$INSTALL_DIR/node_modules/@psiclawops/hypermem/scripts/install-runtime.mjs"
   [[ -f "$installer" ]] || die "missing runtime installer: $installer"
   backup_runtime
@@ -141,6 +165,11 @@ stage_runtime() {
 
 write_minimal_config_if_missing() {
   echo -e "\n${BOLD}  Config check${NC}"
+  if $DRY_RUN; then
+    dryrun "would preserve existing config or write lightweight starter config: $CONFIG_FILE"
+    return
+  fi
+
   if [[ -f "$CONFIG_FILE" ]]; then
     success "existing config preserved: $CONFIG_FILE"
     return
@@ -210,6 +239,11 @@ JSON
 
 verify_stage() {
   echo -e "\n${BOLD}  Stage verification${NC}"
+  if $DRY_RUN; then
+    dryrun "would verify runtime payload under: $RUNTIME_DIR"
+    return
+  fi
+
   [[ -d "$RUNTIME_DIR/dist" ]] || die "missing $RUNTIME_DIR/dist"
   [[ -d "$RUNTIME_DIR/plugin/dist" ]] || die "missing $RUNTIME_DIR/plugin/dist"
   [[ -d "$RUNTIME_DIR/memory-plugin/dist" ]] || die "missing $RUNTIME_DIR/memory-plugin/dist"

package/memory-plugin/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@psiclawops/hypermem-memory",
-  "version": "0.9.0",
+  "version": "0.9.2",
   "description": "HyperMem memory plugin for OpenClaw — bridges HyperMem retrieval into the memory slot",
   "type": "module",
   "main": "dist/index.js",
@@ -35,10 +35,12 @@
   },
   "scripts": {
     "build": "tsc",
+    "prepublishOnly": "npm run build",
+    "prepack": "npm run build",
     "typecheck": "tsc --noEmit"
   },
   "dependencies": {
-    "@psiclawops/hypermem": "0.9.0"
+    "@psiclawops/hypermem": "0.9.2"
   },
   "devDependencies": {
     "openclaw": "*",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@psiclawops/hypermem",
-  "version": "0.9.0",
+  "version": "0.9.2",
   "description": "Agent-centric memory and context composition engine for OpenClaw",
   "type": "module",
   "main": "dist/index.js",
@@ -24,6 +24,8 @@
   },
   "scripts": {
     "build": "tsc",
+    "prepublishOnly": "npm run build",
+    "prepack": "npm run build",
     "health": "node bin/hypermem-status.mjs --master",
     "health:master": "node bin/hypermem-status.mjs --master",
     "install:runtime": "node scripts/install-runtime.mjs",
@@ -40,6 +42,7 @@
     "validate:docs": "node scripts/validate-docs.mjs",
     "validate:config": "node scripts/validate-config-surface.mjs",
     "validate:version-parity": "node scripts/validate-version-parity.mjs",
+    "validate:public-surface": "node scripts/validate-public-surface.mjs",
     "bench:memory": "node bench/data-access-bench.mjs --iterations 1000 --warmup 50",
     "validate:doctor": "node test/doctor-cli.mjs"
   },

package/plugin/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@psiclawops/hypercompositor",
-  "version": "0.9.0",
+  "version": "0.9.2",
   "description": "HyperCompositor — context engine plugin for OpenClaw",
   "type": "module",
   "main": "dist/index.js",
@@ -35,10 +35,12 @@
   },
   "scripts": {
     "build": "tsc",
+    "prepublishOnly": "npm run build",
+    "prepack": "npm run build",
     "typecheck": "tsc --noEmit"
   },
   "dependencies": {
-    "@psiclawops/hypermem": "0.9.0",
+    "@psiclawops/hypermem": "0.9.2",
     "zod": "^4.0.0"
   },
   "devDependencies": {

package/dist/compositor-utils.d.ts

@@ -1,31 +0,0 @@
-/**
- * compositor-utils.ts — Utility functions for context window composition.
- *
- * Provides ordering strategies that improve LLM attention over retrieved
- * documents placed into a prompt.
- */
-/**
- * Reorder documents using zigzag placement to mitigate
- * "Lost in the Middle" attention degradation in LLMs.
- *
- * LLMs exhibit a U-shaped attention curve: items at the beginning and end
- * of context receive ~30% more attention than items in the middle.
- * This function places the most relevant items at the edges and the least
- * relevant items near the center, maximising effective attention on the
- * information that matters most.
- *
- * Reference: Liu et al., "Lost in the Middle: How Language Models Use Long
- * Contexts", ICLR 2025. https://arxiv.org/abs/2307.03172
- *
- * Input:  [d1, d2, d3, d4, d5]  (sorted by relevance, descending)
- * Output: [d1, d3, d5, d4, d2]  (most relevant at edges, least in middle)
- *
- * Algorithm:
- *   - Items at even positions in the input (0, 2, 4, …) fill from the front.
- *   - Items at odd positions in the input (1, 3, 5, …) fill from the back.
- *
- * @param docs - Array sorted by relevance (most relevant first).
- * @returns A new array reordered so the most relevant items sit at the edges.
- */
-export declare function zigzagOrder<T>(docs: T[]): T[];
-//# sourceMappingURL=compositor-utils.d.ts.map

package/dist/compositor-utils.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"compositor-utils.d.ts","sourceRoot":"","sources":["../src/compositor-utils.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AAEH;;;;;;;;;;;;;;;;;;;;;;GAsBG;AACH,wBAAgB,WAAW,CAAC,CAAC,EAAE,IAAI,EAAE,CAAC,EAAE,GAAG,CAAC,EAAE,CAkB7C"}

package/dist/compositor-utils.js

@@ -1,47 +0,0 @@
-/**
- * compositor-utils.ts — Utility functions for context window composition.
- *
- * Provides ordering strategies that improve LLM attention over retrieved
- * documents placed into a prompt.
- */
-/**
- * Reorder documents using zigzag placement to mitigate
- * "Lost in the Middle" attention degradation in LLMs.
- *
- * LLMs exhibit a U-shaped attention curve: items at the beginning and end
- * of context receive ~30% more attention than items in the middle.
- * This function places the most relevant items at the edges and the least
- * relevant items near the center, maximising effective attention on the
- * information that matters most.
- *
- * Reference: Liu et al., "Lost in the Middle: How Language Models Use Long
- * Contexts", ICLR 2025. https://arxiv.org/abs/2307.03172
- *
- * Input:  [d1, d2, d3, d4, d5]  (sorted by relevance, descending)
- * Output: [d1, d3, d5, d4, d2]  (most relevant at edges, least in middle)
- *
- * Algorithm:
- *   - Items at even positions in the input (0, 2, 4, …) fill from the front.
- *   - Items at odd positions in the input (1, 3, 5, …) fill from the back.
- *
- * @param docs - Array sorted by relevance (most relevant first).
- * @returns A new array reordered so the most relevant items sit at the edges.
- */
-export function zigzagOrder(docs) {
-    if (docs.length <= 2) {
-        return docs.slice();
-    }
-    const result = new Array(docs.length);
-    let front = 0;
-    let back = docs.length - 1;
-    for (let i = 0; i < docs.length; i++) {
-        if (i % 2 === 0) {
-            result[front++] = docs[i];
-        }
-        else {
-            result[back--] = docs[i];
-        }
-    }
-    return result;
-}
-//# sourceMappingURL=compositor-utils.js.map

package/dist/content-hash.d.ts

@@ -1,43 +0,0 @@
-/**
- * hypermem Content Hash
- *
- * Content-addressed hashing for fact/knowledge deduplication.
- * Uses BLAKE3 (via @noble/hashes) for fast, collision-resistant fingerprints.
- *
- * Dedup semantics are per-agent: the same content stored by two different
- * agents is intentional and should not be merged. Check with:
- *   WHERE content_hash = ? AND agent_id = ?
- */
-import type { DatabaseSync } from 'node:sqlite';
-/**
- * Compute a BLAKE3 content hash for deduplication.
- * Returns a 64-character hex string (32 bytes).
- *
- * Normalization: collapses whitespace, trims, lowercases
- * before hashing. This catches trivial reformatting differences
- * that shouldn't create duplicate facts.
- */
-export declare function contentHash(text: string): string;
-/**
- * SQL migration statements for adding content_hash columns and indexes.
- *
- * Use non-unique indexes — different agents may legitimately store identical
- * facts. Dedup check is always scoped per agent:
- *   WHERE content_hash = ? AND agent_id = ?
- */
-export declare const SCHEMA_MIGRATIONS: {
-    addFactsContentHash: string;
-    addKnowledgeContentHash: string;
-    indexFactsContentHash: string;
-    indexKnowledgeContentHash: string;
-};
-/**
- * Backfill content_hash for existing rows that have NULL hashes.
- * Meant to run once after schema migration.
- * Returns count of rows updated.
- *
- * Defensive: returns 0 if the content_hash column does not exist on the
- * target table (e.g. migration hasn't run yet or table is missing).
- */
-export declare function backfillContentHashes(db: DatabaseSync, table: 'facts' | 'knowledge'): number;
-//# sourceMappingURL=content-hash.d.ts.map

package/dist/content-hash.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"content-hash.d.ts","sourceRoot":"","sources":["../src/content-hash.ts"],"names":[],"mappings":"AAAA;;;;;;;;;GASG;AAGH,OAAO,KAAK,EAAE,YAAY,EAAE,MAAM,aAAa,CAAC;AAEhD;;;;;;;GAOG;AACH,wBAAgB,WAAW,CAAC,IAAI,EAAE,MAAM,GAAG,MAAM,CAIhD;AAED;;;;;;GAMG;AACH,eAAO,MAAM,iBAAiB;;;;;CAK7B,CAAC;AAEF;;;;;;;GAOG;AACH,wBAAgB,qBAAqB,CACnC,EAAE,EAAE,YAAY,EAChB,KAAK,EAAE,OAAO,GAAG,WAAW,GAC3B,MAAM,CAgCR"}

package/dist/content-hash.js

@@ -1,75 +0,0 @@
-/**
- * hypermem Content Hash
- *
- * Content-addressed hashing for fact/knowledge deduplication.
- * Uses BLAKE3 (via @noble/hashes) for fast, collision-resistant fingerprints.
- *
- * Dedup semantics are per-agent: the same content stored by two different
- * agents is intentional and should not be merged. Check with:
- *   WHERE content_hash = ? AND agent_id = ?
- */
-import { blake3 } from '@noble/hashes/blake3.js';
-/**
- * Compute a BLAKE3 content hash for deduplication.
- * Returns a 64-character hex string (32 bytes).
- *
- * Normalization: collapses whitespace, trims, lowercases
- * before hashing. This catches trivial reformatting differences
- * that shouldn't create duplicate facts.
- */
-export function contentHash(text) {
-    const normalized = text.toLowerCase().replace(/\s+/g, ' ').trim();
-    const bytes = new TextEncoder().encode(normalized);
-    return Buffer.from(blake3(bytes)).toString('hex');
-}
-/**
- * SQL migration statements for adding content_hash columns and indexes.
- *
- * Use non-unique indexes — different agents may legitimately store identical
- * facts. Dedup check is always scoped per agent:
- *   WHERE content_hash = ? AND agent_id = ?
- */
-export const SCHEMA_MIGRATIONS = {
-    addFactsContentHash: `ALTER TABLE facts ADD COLUMN content_hash TEXT`,
-    addKnowledgeContentHash: `ALTER TABLE knowledge ADD COLUMN content_hash TEXT`,
-    indexFactsContentHash: `CREATE INDEX IF NOT EXISTS idx_facts_content_hash ON facts(content_hash)`,
-    indexKnowledgeContentHash: `CREATE INDEX IF NOT EXISTS idx_knowledge_content_hash ON knowledge(content_hash)`,
-};
-/**
- * Backfill content_hash for existing rows that have NULL hashes.
- * Meant to run once after schema migration.
- * Returns count of rows updated.
- *
- * Defensive: returns 0 if the content_hash column does not exist on the
- * target table (e.g. migration hasn't run yet or table is missing).
- */
-export function backfillContentHashes(db, table) {
-    // Defensive: verify the column exists before querying it.
-    const pragmaRows = db
-        .prepare(`PRAGMA table_info(${table})`)
-        .all();
-    const hasColumn = pragmaRows.some((r) => r['name'] === 'content_hash');
-    if (!hasColumn)
-        return 0;
-    const rows = db
-        .prepare(`SELECT id, content FROM ${table} WHERE content_hash IS NULL`)
-        .all();
-    if (rows.length === 0)
-        return 0;
-    const update = db.prepare(`UPDATE ${table} SET content_hash = ? WHERE id = ?`);
-    // Single transaction for the entire batch — much faster than autocommit per row.
-    // Node 22 DatabaseSync does not have .transaction(); use manual BEGIN/COMMIT.
-    db.exec('BEGIN');
-    try {
-        for (const row of rows) {
-            update.run(contentHash(row.content), row.id);
-        }
-        db.exec('COMMIT');
-    }
-    catch (err) {
-        db.exec('ROLLBACK');
-        throw err;
-    }
-    return rows.length;
-}
-//# sourceMappingURL=content-hash.js.map

package/memory-plugin/dist/index.d.ts

@@ -1,24 +0,0 @@
-/**
- * HyperMem Memory Plugin
- *
- * Thin adapter that bridges HyperMem's retrieval capabilities into
- * OpenClaw's memory slot contract (`kind: "memory"`).
- *
- * The context engine plugin (hypercompositor) owns the full lifecycle:
- * ingest, assemble, compact, afterTurn, bootstrap, dispose.
- *
- * This plugin owns the memory slot contract:
- * - registerMemoryCapability() with runtime + publicArtifacts
- * - memory_search tool backing via MemorySearchManager
- * - Public artifacts for memory-wiki bridge
- *
- * Both plugins share the same HyperMem singleton (loaded from repo dist).
- */
-declare const _default: {
-    id: string;
-    name: string;
-    description: string;
-    configSchema: import("openclaw/plugin-sdk").OpenClawPluginConfigSchema;
-    register: NonNullable<import("openclaw/plugin-sdk/plugin-entry").OpenClawPluginDefinition["register"]>;
-} & Pick<import("openclaw/plugin-sdk/plugin-entry").OpenClawPluginDefinition, "kind" | "reload" | "nodeHostCommands" | "securityAuditCollectors">;
-export default _default;

package/memory-plugin/dist/index.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;GAUG;;;;;;;;AA0VH,wBAmBG"}