@gamaze/hicortex 0.19.3 → 0.19.5

package/dist/recall-index.js

@@ -33,6 +33,19 @@
  * unchanged. Turn suppression still wins: a recently shown novelty pick is
  * suppressed like any other (the guarantee is about candidate inclusion, not
  * forcing re-shows).
+ *
+ * #329 item 3 — the pure search is SKIPPED when it would be byte-identical
+ * to the blended one: turn 1 (no centroid yet — nothing to blend) or
+ * sessionIntentWeight 0 (blend disabled). The blended result IS the pure
+ * result there, so the floor is trivially satisfied by the blended picks and
+ * the second search (embeds aside, its whole DB + FTS half) is pure waste.
+ *
+ * #329 item 4 — novelty backfill: when the blended picks are empty/short,
+ * unclaimed maxItems slots are filled from the remaining filtered
+ * pure-prompt tail (gate + suppression already applied). Without it the
+ * topic-switch turn — the one the floor exists for — got the MOST truncated
+ * menu: novelty slots + a diluted remainder, while further pure candidates
+ * that had already passed every gate sat unused.
  */
 var __createBinding = (this && this.__createBinding) || (Object.create ? (function(o, m, k, k2) {
     if (k2 === undefined) k2 = k;
@@ -68,7 +81,7 @@ var __importStar = (this && this.__importStar) || (function () {
     };
 })();
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.DEFAULT_NOVELTY_FLOOR_SLOTS = void 0;
+exports.MAX_SESSION_ID_CHARS = exports.DEFAULT_NOVELTY_FLOOR_SLOTS = void 0;
 exports.resolveNoveltyFloorSlots = resolveNoveltyFloorSlots;
 exports.memoryTitle = memoryTitle;
 exports.formatIndexLine = formatIndexLine;
@@ -116,6 +129,16 @@ function resolveNoveltyFloorSlots(rawSlots, rawMaxItems) {
  *  gate is correct, not a defect); raise only if blocks are persistently
  *  under-filled in production. */
 const CANDIDATE_MULTIPLIER = 3;
+/**
+ * Hard cap on `session_id` length (#328 item 2a). The id is retained as a Map
+ * key by SessionRecallRegistry for the process lifetime (maxSessions=500 LRU
+ * + a per-session shown-set + intent centroid), so an unbounded id is an OOM
+ * vector: ~4.9MB ids × 500 sessions ≈ 2.4GB of retained keys from an
+ * authenticated-but-hostile tenant. Real session ids (CC UUIDs, plugin
+ * session keys) are ≤64 chars — 128 is generous headroom. Longer → 400 with
+ * a clear error; the client treats it like any bad request.
+ */
+exports.MAX_SESSION_ID_CHARS = 128;
 /** First content line, de-markdowned and truncated — the index line title. */
 function memoryTitle(content, maxLen = DEFAULT_TITLE_CHARS) {
     const firstLine = content
@@ -191,6 +214,15 @@ function passesRelevanceGate(r, minSimilarity) {
  *     fold, or the pure prompt with NO centroid state for #324);
  *   - retrieve() with noStrengthen (exposure is recorded by
  *     handleRecallIndex via touchMemoriesShown, never here).
+ *
+ * #329 CR finding 1b: the FTS candidate list is ALSO computed once per
+ * request (ftsOnce, keyed on query + candidate window) and threaded into both
+ * retrieve() calls via the ftsCandidates provider — the blended and pure
+ * searches of one request carry identical query text and window, so their FTS
+ * halves were byte-identical SQL executed twice. `ftsFn` is the DI seam for
+ * tests (production: storage.searchFts); a throwing FTS computation memoizes
+ * to an empty shared list — the same vector-only degradation retrieve()'s
+ * catch always produced, never an error.
  */
 function createRecallRetrieveFn(deps) {
     let embMemo = null;
@@ -200,6 +232,21 @@ function createRecallRetrieveFn(deps) {
         }
         return embMemo.p;
     };
+    const ftsResolve = deps.ftsFn ?? storage.searchFts;
+    let ftsMemo = null;
+    const ftsOnce = (query, limit) => {
+        if (!ftsMemo || ftsMemo.query !== query || ftsMemo.limit !== limit) {
+            try {
+                ftsMemo = { query, limit, rows: ftsResolve(deps.db, query, limit) };
+            }
+            catch {
+                // Same degradation retrieve()'s own catch always produced — the FTS
+                // list is dropped and the search proceeds vector-only.
+                ftsMemo = { query, limit, rows: [] };
+            }
+        }
+        return ftsMemo.rows;
+    };
     return async (query, limit, filters, sessionId, purePrompt) => {
         const { weight, alpha } = (0, retrieval_js_1.getSessionIntent)();
         const promptEmb = await embedOnce(query);
@@ -216,6 +263,10 @@ function createRecallRetrieveFn(deps) {
             project: filters?.project,
             missionDomains: filters?.mission_domains,
             queryEmbedding: queryVec,
+            // #329: shared per-request FTS list. The recall path never passes
+            // sourceAgent, so the memo is keyed on (query, fetchLimit) only —
+            // exactly the two things retrieve() would pass to searchFts.
+            ftsCandidates: (fetchLimit) => ftsOnce(query, fetchLimit),
         });
     };
 }
@@ -242,6 +293,16 @@ async function handleRecallIndex(deps, body) {
     if (!sessionId) {
         return { status: 400, body: { error: "Missing 'session_id'" } };
     }
+    // Length cap (#328 item 2a) — BEFORE the reset branch so an oversized id
+    // never reaches ANY registry call (reset() itself only deletes, but the
+    // next non-reset call with the same id would beginTurn it into a retained
+    // Map key). Clear error so a misbehaving client can self-diagnose.
+    if (sessionId.length > exports.MAX_SESSION_ID_CHARS) {
+        return {
+            status: 400,
+            body: { error: `'session_id' too long (max ${exports.MAX_SESSION_ID_CHARS} chars, got ${sessionId.length})` },
+        };
+    }
     // Reset: SessionStart (startup/resume/clear/compact) — fresh context, so the
     // shown-set is stale by definition.
     if (req.reset === true) {
@@ -270,26 +331,30 @@ async function handleRecallIndex(deps, body) {
         project: typeof req.project === "string" && req.project ? req.project : undefined,
         mission_domains: parseStringListParam(req.mission_domains),
     };
-    // #324: when the floor is armed, TWO searches run per recall — the blended
-    // (session-intent) query that has always run, and a PURE-prompt query with
-    // no centroid blend. Issued together so the second adds no wall-clock
-    // latency beyond its own DB work (the prompt is embedded once — the closure
-    // memoizes). Same failure domain (same db + embedder): either failing fails
-    // the request explicitly; no silent blended-only degradation.
+    // #324 + #329 item 3: when the floor is armed AND would differ from the
+    // blended search, TWO searches run per recall — the blended (session-intent)
+    // query that has always run, and a PURE-prompt query with no centroid blend.
+    // Issued together so the second adds no wall-clock latency beyond its own DB
+    // work (the prompt is embedded once — the closure memoizes). Same failure
+    // domain (same db + embedder): either failing fails the request explicitly;
+    // no silent blended-only degradation.
     //
-    // The pure call fetches the SAME candidate window as the blended call
-    // (maxItems × 3). A narrower window would break the guarantee at the edge:
-    // sqlite-vec KNN candidates are fetched at limit × 3 and re-ranked by
-    // composite score, so a memory the fresh-session path ranks #1 by
-    // strength/recency but that sits at raw-vector rank 19+ would never enter
-    // a small window's candidate set — the #324 failure shape surviving at the
-    // edge. The guarantee is therefore: the top passing pure-prompt hit WITHIN
-    // the shared candidate window always survives into the index.
+    // The SKIP (#329 item 3): on turn 1 the registry has no centroid yet (the
+    // blended call reads-before-fold — recallQueryVector), and at
+    // sessionIntentWeight 0 the centroid is never read at all. In both cases
+    // the blended query vector IS the pure prompt vector, so the second search
+    // would return byte-identical candidates — skip it (the floor is trivially
+    // satisfied: every pure hit is by construction among the blended picks).
+    // The decision is made BEFORE any retrieveFn call, i.e. on the centroid
+    // state of the PREVIOUS turns — exactly the turn-1/turn-2 distinction.
+    const runPureSearch = noveltySlots > 0 &&
+        (0, retrieval_js_1.getSessionIntent)().weight > 0 &&
+        deps.registry.getCentroid(sessionId) !== undefined;
     let results;
     let pureResults;
     try {
         const blended = deps.retrieveFn(prompt, maxItems * CANDIDATE_MULTIPLIER, filters, sessionId);
-        const pure = noveltySlots > 0
+        const pure = runPureSearch
             ? deps.retrieveFn(prompt, maxItems * CANDIDATE_MULTIPLIER, filters, sessionId, true)
             : Promise.resolve([]);
         [results, pureResults] = await Promise.all([blended, pure]);
@@ -316,10 +381,14 @@ async function handleRecallIndex(deps, body) {
     // unchanged. Suppression applies BEFORE the guarantee (suppression wins:
     // the floor is about candidate inclusion, not forcing re-shows). FTS-sourced
     // pure hits pass the gate unconditionally, same as the blended path.
-    const blendedIds = new Set(blendedPicks.map((r) => r.id));
-    const noveltyPicks = pureResults
+    //
+    // The gate + suppression are applied ONCE to the pure list: the head feeds
+    // the novelty floor, the tail feeds the #329 backfill below.
+    const pureFiltered = pureResults
         .filter((r) => passesRelevanceGate(r, minSimilarity))
-        .filter((r) => deps.registry.isShowable(sessionId, r.id))
+        .filter((r) => deps.registry.isShowable(sessionId, r.id));
+    const blendedIds = new Set(blendedPicks.map((r) => r.id));
+    const noveltyPicks = pureFiltered
         .filter((r) => !blendedIds.has(r.id))
         .slice(0, noveltySlots);
     // The floor takes precedence (#324 vs #192 cold slots): novelty picks hold
@@ -329,10 +398,24 @@ async function handleRecallIndex(deps, body) {
     // exceeds maxItems. Render order: novelty picks FIRST — on a topic switch
     // they are the most relevant lines to the CURRENT turn, and the head of the
     // block carries the most weight for a reader scanning the menu.
-    const picked = [
+    let picked = [
         ...noveltyPicks,
         ...blendedPicks.slice(0, Math.max(0, maxItems - noveltyPicks.length)),
     ];
+    // #329 item 4 — backfill: a topic-switch turn dilutes the blended picks, so
+    // picked can land below maxItems even though FURTHER pure candidates have
+    // already passed the gate + suppression + dedup (they sit in the pure tail
+    // beyond the first noveltyFloorSlots). Fill the unclaimed slots from that
+    // tail — without it, the turn the floor exists for got the most truncated
+    // menu. Continuing-intent sessions are untouched: blended picks full →
+    // nothing to backfill (zero-delta output preserved).
+    if (picked.length < maxItems) {
+        const pickedIds = new Set(picked.map((r) => r.id));
+        const backfill = pureFiltered
+            .filter((r) => !pickedIds.has(r.id))
+            .slice(0, maxItems - picked.length);
+        picked = [...picked, ...backfill];
+    }
     if (picked.length === 0) {
         return { status: 200, body: { block: null, shown: [], turn } };
     }

package/dist/retrieval.d.ts

@@ -231,6 +231,17 @@ export declare function retrieve(db: Database.Database, embedFn: EmbedFn, query:
      *  and get pure-prompt behavior (the query string is embedded here). The
      *  FTS path still uses the raw `query` text regardless. */
     queryEmbedding?: Float32Array;
+    /** #329 CR finding 1b: caller-provided FTS candidate resolution, called
+     *  INSTEAD of running storage.searchFts here. The /recall-index closure
+     *  passes a per-request memoized provider so the blended and pure
+     *  searches of ONE request — same query text, same candidate window —
+     *  execute the FTS half exactly once and share the list. The provider
+     *  receives the fetchLimit/sourceAgent THIS call would have used, so the
+     *  shared list is always computed with the right window. Callers that
+     *  omit it get the previous behavior (retrieve runs searchFts itself). */
+    ftsCandidates?: (fetchLimit: number, sourceAgent?: string) => Array<Memory & {
+        rank: number;
+    }>;
 }): Promise<MemorySearchResult[]>;
 /**
  * Get recent context, optionally filtered by project.

package/dist/retrieval.js

@@ -556,8 +556,12 @@ async function retrieve(db, embedFn, query, options) {
     try {
         // sourceAgent is pushed into the FTS SQL (hard filter). project is NOT (it
         // is a soft affinity boost in computeScore as of #203). privacy is NOT
-        // (0.16.x: vestigial column, never filtered).
-        ftsCandidates = storage.searchFts(db, query, fetchLimit, sourceAgent);
+        // (0.16.x: vestigial column, never filtered). With a caller-provided
+        // provider (#329 request-level memo) the same list is shared across the
+        // retrieves of one recall request instead of re-executed.
+        ftsCandidates = options?.ftsCandidates
+            ? options.ftsCandidates(fetchLimit, sourceAgent)
+            : storage.searchFts(db, query, fetchLimit, sourceAgent);
     }
     catch {
         // FTS5 search can fail on special characters; fall back to vector-only

package/dist/storage.d.ts

@@ -137,6 +137,36 @@ export interface Bm25Weights {
 export declare function configureBm25Fts(config?: Record<string, unknown> | null): Bm25Weights;
 /** Current resolved weights (tests + status output). */
 export declare function getBm25Weights(): Bm25Weights;
+/**
+ * Cap on tokens fed to an FTS5 MATCH expression (#329 CR finding 1a).
+ * Quoting made pasted term lists LEGAL queries — and an all-common-tokens AND
+ * is expensive: measured at 100K rows, a 50-token AND runs ~518ms and a
+ * 200-token one 6.3s, and the /recall-index hot path would pay it twice per
+ * prompt. Beyond ~24 tokens the implicit AND is semantic noise anyway (a
+ * memory matching 24+ ANDed prompt tokens is either the exact text or
+ * nothing), so the FIRST 24 tokens are used. 24 is a shipped bound, not a
+ * config knob — change it deliberately, with a perf measurement.
+ */
+export declare const FTS_MATCH_MAX_TOKENS = 24;
+/**
+ * FTS5 MATCH-safety quoting (#329 item 1). The raw prompt is NOT valid FTS5
+ * query syntax: ordinary prompt punctuation (?, -, (, :, URLs, apostrophes, a
+ * leading AND/OR) crashes the FTS5 parser, and retrieval.retrieve's catch then
+ * silently drops the ENTIRE FTS candidate list — the perf sweep measured 8/12
+ * realistic prompts affected, and it is why relevance eval #3 saw 0 FTS rows
+ * in 2,208 candidates. Fix: tokenize on whitespace, strip embedded double
+ * quotes (a raw `"` would terminate our own quoting), and wrap each token in
+ * double quotes — a quoted token is a phrase of LITERAL strings, immune to
+ * FTS5 query syntax (`"what" "is" "the" "deployment" "status"`). Punctuation
+ * INSIDE a token is kept: the tokenizer strips it identically on both sides,
+ * so `"status?"` still matches content containing "status". Joined with spaces
+ * (implicit AND — the same semantics clean prompts always had; a PROSE prompt
+ * whose content holds only most of the tokens matches nothing, which is why
+ * FTS fires on short keyword prompts, not prose recall). Capped at the first
+ * FTS_MATCH_MAX_TOKENS tokens. A query that quotes away to nothing yields ""
+ * and the caller skips the SQL entirely.
+ */
+export declare function buildFtsMatchExpression(query: string): string;
 /**
  * Full-text search using FTS5 fielded BM25 (BM25F) ranking.
  * Returns memories with a rank field (lower is better — see sign note below).

package/dist/storage.js

@@ -4,6 +4,7 @@
  * Ported from hicortex/storage.py. All functions are synchronous (better-sqlite3).
  */
 Object.defineProperty(exports, "__esModule", { value: true });
+exports.FTS_MATCH_MAX_TOKENS = void 0;
 exports.embedToBlob = embedToBlob;
 exports.insertMemory = insertMemory;
 exports.resolveMemoryId = resolveMemoryId;
@@ -20,6 +21,7 @@ exports.getStoredEmbedding = getStoredEmbedding;
 exports.vectorSearch = vectorSearch;
 exports.configureBm25Fts = configureBm25Fts;
 exports.getBm25Weights = getBm25Weights;
+exports.buildFtsMatchExpression = buildFtsMatchExpression;
 exports.searchFts = searchFts;
 exports.addLink = addLink;
 exports.getLinks = getLinks;
@@ -345,6 +347,44 @@ function configureBm25Fts(config) {
 function getBm25Weights() {
     return { ...bm25Weights };
 }
+/**
+ * Cap on tokens fed to an FTS5 MATCH expression (#329 CR finding 1a).
+ * Quoting made pasted term lists LEGAL queries — and an all-common-tokens AND
+ * is expensive: measured at 100K rows, a 50-token AND runs ~518ms and a
+ * 200-token one 6.3s, and the /recall-index hot path would pay it twice per
+ * prompt. Beyond ~24 tokens the implicit AND is semantic noise anyway (a
+ * memory matching 24+ ANDed prompt tokens is either the exact text or
+ * nothing), so the FIRST 24 tokens are used. 24 is a shipped bound, not a
+ * config knob — change it deliberately, with a perf measurement.
+ */
+exports.FTS_MATCH_MAX_TOKENS = 24;
+/**
+ * FTS5 MATCH-safety quoting (#329 item 1). The raw prompt is NOT valid FTS5
+ * query syntax: ordinary prompt punctuation (?, -, (, :, URLs, apostrophes, a
+ * leading AND/OR) crashes the FTS5 parser, and retrieval.retrieve's catch then
+ * silently drops the ENTIRE FTS candidate list — the perf sweep measured 8/12
+ * realistic prompts affected, and it is why relevance eval #3 saw 0 FTS rows
+ * in 2,208 candidates. Fix: tokenize on whitespace, strip embedded double
+ * quotes (a raw `"` would terminate our own quoting), and wrap each token in
+ * double quotes — a quoted token is a phrase of LITERAL strings, immune to
+ * FTS5 query syntax (`"what" "is" "the" "deployment" "status"`). Punctuation
+ * INSIDE a token is kept: the tokenizer strips it identically on both sides,
+ * so `"status?"` still matches content containing "status". Joined with spaces
+ * (implicit AND — the same semantics clean prompts always had; a PROSE prompt
+ * whose content holds only most of the tokens matches nothing, which is why
+ * FTS fires on short keyword prompts, not prose recall). Capped at the first
+ * FTS_MATCH_MAX_TOKENS tokens. A query that quotes away to nothing yields ""
+ * and the caller skips the SQL entirely.
+ */
+function buildFtsMatchExpression(query) {
+    return query
+        .split(/\s+/)
+        .map((token) => token.replace(/"/g, ""))
+        .filter((token) => token.length > 0)
+        .slice(0, exports.FTS_MATCH_MAX_TOKENS)
+        .map((token) => `"${token}"`)
+        .join(" ");
+}
 /**
  * Full-text search using FTS5 fielded BM25 (BM25F) ranking.
  * Returns memories with a rank field (lower is better — see sign note below).
@@ -366,8 +406,13 @@ function getBm25Weights() {
  * caching is unaffected and the config path is the only editor.
  */
 function searchFts(db, query, limit = 10, sourceAgent) {
+    // #329: quote the query into literal phrases — a raw prompt crashes the
+    // FTS5 parser on punctuation and the caller's catch drops the whole list.
+    const matchExpr = buildFtsMatchExpression(query);
+    if (!matchExpr)
+        return [];
     const conditions = ["memories_fts MATCH ?"];
-    const params = [query];
+    const params = [matchExpr];
     if (sourceAgent) {
         conditions.push("m.source_agent = ?");
         params.push(sourceAgent);

package/dist/type-classify.js

@@ -84,7 +84,9 @@ function buildTypeClassifyPrompt(content) {
         `"adopted the graded-schema tag model"). Not knowledge (it can change) and ` +
         `not an experience (it persists). A bare AI recommendation or proposal is ` +
         `NEVER a decision — "AI proposed X → user declined/held" is experience ` +
-        `(#290).\n\n` +
+        `(#290). Even if carried out by the user, a version bump, merge, or count ` +
+        `is never a decision — only the durable user-confirmed standardization it ` +
+        `embodies is (#329).\n\n` +
         `IMPORTANCE (0.0–1.0):\n` +
         `- 0.8–1.0: load-bearing — a core piece of knowledge or a decision the ` +
         `agent must know.\n` +

package/dist/types.d.ts

@@ -413,6 +413,15 @@ export interface HicortexConfig {
      * accepts no client limit.
      */
     recallLimit?: number;
+    /**
+     * OC plugin (#326): auto-scaffold the dead-man guard line into the agent
+     * workspace bootstrap file (BOOTSTRAP.md) at service start — the #313
+     * SECONDARY layer under the injected IDENTITY UNAVAILABLE banner (which is
+     * the primary, plugin-side mechanism). Idempotent: a bootstrap already
+     * carrying the line is never rewritten. Default true; `false` disables both
+     * the write and any file creation entirely.
+     */
+    scaffoldDeadMan?: boolean;
     /**
      * Soft cap on the memory corpus (default 10000). When the corpus exceeds this,
      * the nightly's capacity-eviction stage (#245) removes the lowest-
@@ -465,6 +474,14 @@ export interface HicortexConfig {
      * Operator-owned: point at a mounted backup volume, a tmpfs, etc.
      */
     backupDir?: string;
+    /**
+     * Backup retention (#327): how many of the newest `hicortex-*.tar.gz`
+     * artifacts the backup dir keeps after each successful write. Default 7;
+     * 0 keeps everything. Without it every full nightly (and `hicortex backup`)
+     * adds an artifact forever — unbounded growth, per hosted tenant too. Only
+     * artifacts matching the product's own name pattern are ever pruned.
+     */
+    backupRetention?: number;
     /**
      * Post-backup offsite hook (#6). When set, `hicortex backup` and the nightly
      * backup stage invoke this command with the artifact path appended as the LAST

package/dist/uninstall.d.ts

@@ -14,4 +14,37 @@
 export declare const SESSION_START_HOOK_COMMAND_RE: RegExp;
 /** True when a CC hook `command` string runs the Hicortex SessionStart hook. */
 export declare function isHicortexSessionStartHook(command: string): boolean;
+/**
+ * Matches a CC hook `command` that runs the Hicortex recall hook — the
+ * `recall-hook` subcommand (#192). Same word-boundary discipline as the
+ * learnings matcher: an unrelated command that merely CONTAINS the substring
+ * ("my-recall-hook", "recall-hooks-old") is never swept up. Used for BOTH
+ * event arrays the installer writes (UserPromptSubmit + SessionStart).
+ */
+export declare const RECALL_HOOK_COMMAND_RE: RegExp;
+/** True when a CC hook `command` string runs the Hicortex recall hook. */
+export declare function isHicortexRecallHook(command: string): boolean;
+/** One hook group removed from settings.json (for per-group logging). */
+export interface RemovedHookGroup {
+    /** CC event array the entries were removed from ("SessionStart", "UserPromptSubmit"). */
+    event: string;
+    /** Which Hicortex hook set: "learnings" (learnings-identity/lessons-context) or "recall". */
+    kind: "learnings" | "recall";
+    /** Number of matcher entries removed. */
+    count: number;
+}
+/**
+ * Remove every Hicortex hook entry from a PARSED ~/.claude/settings.json
+ * (#327): the SessionStart learnings hook (canonical + legacy alias) AND the
+ * recall-hook pair (UserPromptSubmit + SessionStart, installed together by
+ * installRecallHooks — leaving either behind is a silent npx spawn per prompt
+ * forever). Mutates `settings` in place; returns what was removed (empty when
+ * nothing matched — a clean no-op). Exact-match discipline throughout: only
+ * entries whose `hooks[].command` matches a Hicortex subcommand are removed;
+ * foreign hooks (and prefix-colliding names) stay untouched.
+ *
+ * Pure on the parsed object so the uninstall behavior is unit-testable
+ * without spinning up CC; runUninstall owns the file I/O.
+ */
+export declare function removeHicortexCcHooks(settings: Record<string, unknown>): RemovedHookGroup[];
 export declare function runUninstall(): Promise<void>;

package/dist/uninstall.js

@@ -4,8 +4,10 @@
  * Preserves the database (user data).
  */
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.SESSION_START_HOOK_COMMAND_RE = void 0;
+exports.RECALL_HOOK_COMMAND_RE = exports.SESSION_START_HOOK_COMMAND_RE = void 0;
 exports.isHicortexSessionStartHook = isHicortexSessionStartHook;
+exports.isHicortexRecallHook = isHicortexRecallHook;
+exports.removeHicortexCcHooks = removeHicortexCcHooks;
 exports.runUninstall = runUninstall;
 const paths_js_1 = require("./paths.js");
 const node_fs_1 = require("node:fs");
@@ -33,6 +35,69 @@ exports.SESSION_START_HOOK_COMMAND_RE = /(^|\s)(?:learnings-identity|lessons-con
 function isHicortexSessionStartHook(command) {
     return typeof command === "string" && exports.SESSION_START_HOOK_COMMAND_RE.test(command);
 }
+/**
+ * Matches a CC hook `command` that runs the Hicortex recall hook — the
+ * `recall-hook` subcommand (#192). Same word-boundary discipline as the
+ * learnings matcher: an unrelated command that merely CONTAINS the substring
+ * ("my-recall-hook", "recall-hooks-old") is never swept up. Used for BOTH
+ * event arrays the installer writes (UserPromptSubmit + SessionStart).
+ */
+exports.RECALL_HOOK_COMMAND_RE = /(^|\s)recall-hook(\s|$)/;
+/** True when a CC hook `command` string runs the Hicortex recall hook. */
+function isHicortexRecallHook(command) {
+    return typeof command === "string" && exports.RECALL_HOOK_COMMAND_RE.test(command);
+}
+/**
+ * Remove every Hicortex hook entry from a PARSED ~/.claude/settings.json
+ * (#327): the SessionStart learnings hook (canonical + legacy alias) AND the
+ * recall-hook pair (UserPromptSubmit + SessionStart, installed together by
+ * installRecallHooks — leaving either behind is a silent npx spawn per prompt
+ * forever). Mutates `settings` in place; returns what was removed (empty when
+ * nothing matched — a clean no-op). Exact-match discipline throughout: only
+ * entries whose `hooks[].command` matches a Hicortex subcommand are removed;
+ * foreign hooks (and prefix-colliding names) stay untouched.
+ *
+ * Pure on the parsed object so the uninstall behavior is unit-testable
+ * without spinning up CC; runUninstall owns the file I/O.
+ */
+function removeHicortexCcHooks(settings) {
+    const hooks = settings.hooks;
+    if (!hooks || typeof hooks !== "object")
+        return [];
+    const groups = [
+        { event: "SessionStart", kind: "learnings", match: isHicortexSessionStartHook },
+        { event: "SessionStart", kind: "recall", match: isHicortexRecallHook },
+        { event: "UserPromptSubmit", kind: "recall", match: isHicortexRecallHook },
+    ];
+    const removed = [];
+    for (const g of groups) {
+        const arr = hooks[g.event];
+        if (!Array.isArray(arr))
+            continue;
+        const filtered = arr.filter((entry) => {
+            if (typeof entry !== "object" || entry === null)
+                return true;
+            const e = entry;
+            if (Array.isArray(e.hooks)) {
+                return !e.hooks.some((h) => typeof h === "object" &&
+                    h !== null &&
+                    typeof h.command === "string" &&
+                    g.match(h.command));
+            }
+            return true;
+        });
+        if (filtered.length < arr.length) {
+            // Drop the event key entirely when the filter emptied it — no
+            // `"UserPromptSubmit": []` husk left in the settings file.
+            if (filtered.length > 0)
+                hooks[g.event] = filtered;
+            else
+                delete hooks[g.event];
+            removed.push({ event: g.event, kind: g.kind, count: arr.length - filtered.length });
+        }
+    }
+    return removed;
+}
 async function ask(question) {
     const rl = (0, node_readline_1.createInterface)({ input: process.stdin, output: process.stdout });
     return new Promise((resolve) => {
@@ -146,34 +211,21 @@ async function runUninstall() {
     }
     if (removedCmds > 0)
         console.log(`  ✓ Removed ${removedCmds} legacy CC command${removedCmds > 1 ? "s" : ""} (/learn, /hicortex-activate)`);
-    // 4. Remove SessionStart hook (JSON merge — filter out entries containing
-    //    EITHER the canonical "learnings-identity" OR the legacy "lessons-context"
-    //    alias, #264 backcompat: an install may have written either name.)
+    // 4. Remove ALL Hicortex CC hooks (#327): the SessionStart learnings hook
+    //    (canonical `learnings-identity` OR the legacy `lessons-context` alias,
+    //    #264 backcompat) AND BOTH `recall-hook` entries (UserPromptSubmit +
+    //    SessionStart — installed as a pair by installRecallHooks; leaving
+    //    either behind keeps a silent npx spawn per prompt forever).
+    //    Fail-soft when absent; word-boundary matchers never touch foreign hooks.
     try {
         const raw = (0, node_fs_1.readFileSync)(CC_SETTINGS, "utf-8");
         const settings = JSON.parse(raw);
-        const hooks = settings.hooks;
-        const sessionStart = hooks && Array.isArray(hooks.SessionStart) ? hooks.SessionStart : null;
-        if (hooks && sessionStart) {
-            const before = sessionStart.length;
-            const filtered = sessionStart.filter((entry) => {
-                if (typeof entry !== "object" || entry === null)
-                    return true;
-                const e = entry;
-                if (Array.isArray(e.hooks)) {
-                    return !e.hooks.some((h) => {
-                        if (typeof h !== "object" || h === null)
-                            return false;
-                        const hook = h;
-                        return typeof hook.command === "string" && isHicortexSessionStartHook(hook.command);
-                    });
-                }
-                return true;
-            });
-            if (filtered.length < before) {
-                hooks.SessionStart = filtered;
-                (0, node_fs_1.writeFileSync)(CC_SETTINGS, JSON.stringify(settings, null, 2));
-                console.log("  ✓ Removed SessionStart learnings-identity hook");
+        const removed = removeHicortexCcHooks(settings);
+        if (removed.length > 0) {
+            (0, node_fs_1.writeFileSync)(CC_SETTINGS, JSON.stringify(settings, null, 2));
+            for (const r of removed) {
+                const name = r.kind === "learnings" ? "learnings-identity" : "recall-hook";
+                console.log(`  ✓ Removed ${r.event} ${name} hook${r.count > 1 ? "s" : ""}`);
             }
         }
     }

package/dist/viz.d.ts

@@ -54,7 +54,7 @@ export declare const VIZ_VENDOR_FILES: ReadonlySet<string>;
  * this — a hosted tenant dir is fail-closed by default. mcp-server.ts captures
  * the marker state once at boot and passes it in (no per-request stat).
  */
-export declare function createAuthMiddleware(authToken: string | undefined, authTokenPrevious?: string, allowLocalhostBypass?: boolean): express.RequestHandler;
+export declare function createAuthMiddleware(authToken: string | undefined, authTokenPrevious?: string, allowLocalhostBypass?: boolean, bodyLimitBytes?: number): express.RequestHandler;
 /**
  * Resolve the on-disk path of the viz page. Throws (fail explicitly) when the
  * asset is missing — a broken install should surface, not degrade silently.

package/dist/viz.js

@@ -101,10 +101,37 @@ function safeBearerMatch(headerValue, expectedToken) {
  * this — a hosted tenant dir is fail-closed by default. mcp-server.ts captures
  * the marker state once at boot and passes it in (no per-request stat).
  */
-function createAuthMiddleware(authToken, authTokenPrevious, allowLocalhostBypass) {
+function createAuthMiddleware(authToken, authTokenPrevious, allowLocalhostBypass, bodyLimitBytes) {
     const previous = authTokenPrevious && authTokenPrevious.length > 0 ? authTokenPrevious : undefined;
     const bypassEnabled = allowLocalhostBypass === true;
+    const contentLengthCap = Number.isFinite(bodyLimitBytes) && bodyLimitBytes > 0
+        ? bodyLimitBytes
+        : null;
     return (req, res, next) => {
+        // #328 item 4 (package-server half) — BELT. The PRIMARY gate is
+        // makeContentLengthGate (mcp-server.ts), registered BEFORE express.json:
+        // this middleware sits AFTER the parser, so by the time it runs the body
+        // has already been buffered (up to the parser's limit) — its Content-Length
+        // check can only catch what a caller wires WITHOUT the front gate. Kept
+        // for standalone/reuse callers of createAuthMiddleware and as
+        // defense-in-depth; 413 mirrors express.json's own oversize status.
+        //
+        // RESIDUAL RISK (unchanged by either check): chunked transfer-encoding
+        // sends no Content-Length, so neither gate sees it — those requests still
+        // buffer up to the parser limit inside express.json before the 413
+        // (bounded per request, no pre-auth rejection), and there is no
+        // concurrency cap here. Full pre-auth bounding lives in the hosted
+        // router's webhook path (stripe.ts, #328 item 4) — the tenant data plane
+        // trusts its bearer (self-hosted threat model) or sits behind the
+        // provider's edge (hosted).
+        if (contentLengthCap !== null) {
+            const declared = req.headers["content-length"];
+            const declaredNum = typeof declared === "string" ? Number(declared) : NaN;
+            if (Number.isFinite(declaredNum) && declaredNum > contentLengthCap) {
+                res.status(413).json({ error: "request body too large" });
+                return;
+            }
+        }
         if (req.path === "/health")
             return next();
         // The /viz page SHELL is public like /health — it contains no data and no

package/openclaw.plugin.json

@@ -2,7 +2,7 @@
   "id": "hicortex",
   "name": "Hicortex — Long-term Memory That Learns",
   "description": "Your agents remember past decisions, avoid repeated mistakes, and get smarter every day. Nightly reflection generates actionable lessons that automatically update agent behavior.",
-  "version": "0.19.3",
+  "version": "0.19.5",
   "kind": "lifecycle",
   "skills": ["./skills/hicortex-memory"],
   "configSchema": {
@@ -25,6 +25,11 @@
         "type": "number",
         "default": 8,
         "description": "Max memories per recall on the pre-0.14 /search fallback (default 8). The pushed recall index is sized by SERVER config (recallMaxItems) — the server accepts no client limit."
+      },
+      "scaffoldDeadMan": {
+        "type": "boolean",
+        "default": true,
+        "description": "Auto-scaffold the dead-man identity-guard line into the agent workspace bootstrap (BOOTSTRAP.md) at startup — the secondary defense under the identity-unavailable banner the plugin injects when the identity fetch fails. Idempotent: the .bak backup is written once and never touched again. Set false to keep the plugin from writing any bootstrap file."
       }
     },
     "required": []
@@ -46,6 +51,10 @@
     "recallLimit": {
       "label": "Recall Limit",
       "placeholder": "8"
+    },
+    "scaffoldDeadMan": {
+      "label": "Scaffold Dead-Man Guard",
+      "placeholder": "true"
     }
   }
 }