pi-mega-compact 0.9.1 → 0.9.2

package/dist/extensions/mega-runtime/game-state.js

@@ -108,6 +108,13 @@ export function ensureGameStateWatcherImpl(self, view) {
                 }
             }
         });
+        // The watcher is a cache-eviction convenience, never a reason to stay
+        // alive: an active+referenced fs_event handle holds node's event loop
+        // open, so a runtime that was never dispose()d (every extension test, and
+        // any `pi -p` run that skips session_shutdown) hangs the process after all
+        // work is done. unref'd like the perf interval — while pi runs there are
+        // always other referenced handles, so the watcher still fires normally.
+        self.gameStateWatcher.unref?.();
         self.gameStateWatchDir = self.currentStateDir;
     }
     catch {

package/dist/src/memoryOps.test.js

@@ -1,3 +1,18 @@
+// This file exercises the sync node:sqlite memory ops only, but every
+// applyMemoryOps() write also fires indexMemoryWrite() → upsertMemoryEmbedding()
+// at the machine-wide PGlite index, fire-and-forget, keyed by repoKey(stateDir)
+// — which for these tmp state dirs is the tmp path itself. Left alone that lands
+// in the developer's real ~/.pi/mega-compact-vector, where the rows stay
+// eligible for cross-repo recall forever: a live session can be handed
+// "threshold is 50k" and "the threshold is 100k" from this file as if they were
+// another project's memories. scripts/run-tests.mjs sets MEGACOMPACT_INDEX_DIR
+// per child, so the suite was already safe; running the file directly was not.
+//
+// Disabling PGlite is the same guard memoryRoundtrip.test.ts uses for the same
+// reason, and it also keeps the file's exit clean (no WASM handle, and no
+// initdb still running when the first test ends). MEGACOMPACT_INDEX_DIR is set
+// as well so the isolation holds if a later test needs the index re-enabled.
+process.env.MEGACOMPACT_PGLITE_DISABLED = "true";
 import { test } from "node:test";
 import assert from "node:assert/strict";
 import { mkdtempSync, rmSync } from "node:fs";
@@ -6,6 +21,7 @@ import { join } from "node:path";
 import { applyMemoryOps } from "./memoryOps.js";
 import { addMemory, listMemories, replaceMemory, referenceMemory, MEMORY_MAX_CHARS, } from "./store/sqlite.js";
 const baseTmp = mkdtempSync(join(tmpdir(), "mc-memops-"));
+process.env.MEGACOMPACT_INDEX_DIR = join(baseTmp, "index");
 test("applyMemoryOps: ADD inserts a new memory", async () => {
     const dir = join(baseTmp, "add");
     await applyMemoryOps([{ op: "add", memory: { content: "we use node:sqlite as the store", category: "decision", sourceTurn: 0 } }], dir);

package/extensions/mega-runtime/game-state.ts

@@ -14,6 +14,8 @@ import { disposePerf, type PerfContext } from "./perf.js";
 
 export interface GameWatcherLike {
 	close(): void;
+	/** fs.FSWatcher has it; test doubles need not. */
+	unref?(): unknown;
 }
 
 export interface GameStateContext {
@@ -142,6 +144,13 @@ export function ensureGameStateWatcherImpl(self: GameStateContext, view: GameSta
 				}
 			},
 		);
+		// The watcher is a cache-eviction convenience, never a reason to stay
+		// alive: an active+referenced fs_event handle holds node's event loop
+		// open, so a runtime that was never dispose()d (every extension test, and
+		// any `pi -p` run that skips session_shutdown) hangs the process after all
+		// work is done. unref'd like the perf interval — while pi runs there are
+		// always other referenced handles, so the watcher still fires normally.
+		self.gameStateWatcher.unref?.();
 		self.gameStateWatchDir = self.currentStateDir;
 	} catch {
 		/* non-fatal: missing dir / platform issue — next snapshot re-queries */

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pi-mega-compact",
-  "version": "0.9.1",
+  "version": "0.9.2",
   "description": "Layered, local, vector-backed context compressor for pi — supersede/collapse/cluster compaction with deduped inline recall.",
   "type": "module",
   "license": "BSD-3-Clause",

package/src/memoryOps.test.ts

@@ -1,3 +1,18 @@
+// This file exercises the sync node:sqlite memory ops only, but every
+// applyMemoryOps() write also fires indexMemoryWrite() → upsertMemoryEmbedding()
+// at the machine-wide PGlite index, fire-and-forget, keyed by repoKey(stateDir)
+// — which for these tmp state dirs is the tmp path itself. Left alone that lands
+// in the developer's real ~/.pi/mega-compact-vector, where the rows stay
+// eligible for cross-repo recall forever: a live session can be handed
+// "threshold is 50k" and "the threshold is 100k" from this file as if they were
+// another project's memories. scripts/run-tests.mjs sets MEGACOMPACT_INDEX_DIR
+// per child, so the suite was already safe; running the file directly was not.
+//
+// Disabling PGlite is the same guard memoryRoundtrip.test.ts uses for the same
+// reason, and it also keeps the file's exit clean (no WASM handle, and no
+// initdb still running when the first test ends). MEGACOMPACT_INDEX_DIR is set
+// as well so the isolation holds if a later test needs the index re-enabled.
+process.env.MEGACOMPACT_PGLITE_DISABLED = "true";
 import { test } from "node:test";
 import assert from "node:assert/strict";
 import { mkdtempSync, rmSync } from "node:fs";
@@ -13,6 +28,7 @@ import {
 } from "./store/sqlite.js";
 
 const baseTmp = mkdtempSync(join(tmpdir(), "mc-memops-"));
+process.env.MEGACOMPACT_INDEX_DIR = join(baseTmp, "index");
 
 test("applyMemoryOps: ADD inserts a new memory", async () => {
   const dir = join(baseTmp, "add");