akm-cli 0.9.17-alpha.1 → 0.9.17-alpha.10

package/STABILITY.md

@@ -281,8 +281,8 @@ CHANGELOG with a migration note.
   print unredacted. `akm task validate <path>` (new in 0.9.11) is the same
   kind of zero-write introspection as `explain`, but takes a bare filesystem
   path rather than a bundle-qualified ref — it reports whether that ONE file
-  would parse cleanly (`valid`), auto-convert from task v2/v3 (`converts`),
-  need a human decision the deterministic migrator can't make (`blocked`),
+  would parse cleanly (`valid`), need `akm migrate apply` first (`blocked`:
+  task v2/v3, or a retired `schedule[].enabled`),
   fail schema validation (`invalid`), or isn't a task source at all
   (`not-a-task`) — exactly the diagnostic `akm task sync` would produce for
   it, before the file is ever wired into a bundle or the scheduler.
@@ -366,8 +366,8 @@ for scripted use.
 ### `akm improve` autonomy — opt-in in 0.9.0
 
 **`akm improve` is review-first by default in 0.9.0.** The command itself is ON
-— its schedules, reflect/distill proposals, and graph extraction all run — but
-the lanes that mutate assets *without* review require an explicit opt-in:
+— its schedules and reflect/distill proposals all run — but the lanes that
+mutate assets *without* review require an explicit opt-in:
 
 ```sh
 akm config set experimental.improveAutonomy true
@@ -388,9 +388,10 @@ review-first config correctly shows `queue`.
 | memory cleanup | Belief-state frontmatter rewrites, archive moves | analyzed but not applied |
 | `triage` `applyMode: "promote"` | Auto-accepts queued proposals into the bundle | downgraded to `queue` — triage still runs, it just does not auto-accept |
 
-Consolidation remains enabled with autonomy off because merge, delete, and
-contradiction operations are advisory; promotion only emits a reviewable
-proposal.
+Consolidation remains enabled with autonomy off: both its passes (promotion,
+and the pair pass's duplicate/subsumed/supersedes judging) only ever emit a
+reviewable proposal, and a pair-pass `retire` proposal is never auto-accepted
+by `triage` `applyMode: "promote"` regardless of this gate.
 
 Because the gate is applied before the LLM preflight, a review-first workspace
 also needs fewer engines configured: a strategy whose only model-backed process
@@ -409,9 +410,9 @@ Autonomy is never inferred: an absent `experimental` section, an absent key, and
 an explicit `false` all read as off, so a partially-written or older config is
 review-first rather than accidentally permissive.
 
-Reflect, distill, extract candidates, validation, proactive-maintenance
-selection, and graph extraction are proposal-only and never write assets
-directly. Two further direct writes are ungated by design: `extract`'s session
+Reflect, distill, extract candidates, validation, and proactive-maintenance
+selection are proposal-only and never write assets directly. Two further
+direct writes are ungated by design: `extract`'s session
 indexing (additive `sessions/**` writes,
 `processes.extract.indexSessions`, default on) and distill's
 encoding-salience frontmatter stamp (metadata only).

package/dist/akm

@@ -4,212 +4,143 @@
 // file, You can obtain one at https://mozilla.org/MPL/2.0/.
 
 import { spawn, spawnSync } from "node:child_process";
-import { createHash } from "node:crypto";
-import fs from "node:fs";
-import path from "node:path";
 import { fileURLToPath } from "node:url";
 
-const CONTEXT_ARG = "--scheduler-context";
-const CONTEXT_KEYS = ["AKM_BUNDLE_DIR", "AKM_CONFIG_DIR", "AKM_DATA_DIR", "AKM_CACHE_DIR", "AKM_STATE_DIR"];
-const CONTROL_CHARACTER = /[\u0000-\u001f\u007f-\u009f]/;
-
-function invalidContext(file, reason) {
-  throw new Error(`Invalid scheduler context descriptor "${file}": ${reason}.`);
-}
-
-function readSchedulerContext(file) {
-  if (CONTROL_CHARACTER.test(file) || (!path.posix.isAbsolute(file) && !path.win32.isAbsolute(file))) {
-    invalidContext(file, "path must be absolute");
-  }
-  let linkStat;
-  try {
-    linkStat = fs.lstatSync(file);
-  } catch (error) {
-    invalidContext(file, error instanceof Error ? error.message : String(error));
-  }
-  if (linkStat.isSymbolicLink()) invalidContext(file, "symbolic links are not allowed");
-  if (!linkStat.isFile()) invalidContext(file, "path is not a regular file");
-
-  let bytes;
-  let fd;
-  try {
-    const noFollow = process.platform === "win32" ? 0 : fs.constants.O_NOFOLLOW;
-    fd = fs.openSync(file, fs.constants.O_RDONLY | noFollow);
-    const stat = fs.fstatSync(fd);
-    if (!stat.isFile()) invalidContext(file, "path is not a regular file");
-    if (process.platform !== "win32") {
-      if (typeof process.getuid !== "function") {
-        invalidContext(file, "current uid is unavailable for ownership verification");
-      }
-      const uid = process.getuid();
-      if (stat.uid !== uid) invalidContext(file, `file owner ${stat.uid} does not match uid ${uid}`);
-      if ((stat.mode & 0o077) !== 0) invalidContext(file, "group or other permissions must be disabled");
-    }
-    bytes = fs.readFileSync(fd);
-  } finally {
-    if (fd !== undefined) fs.closeSync(fd);
-  }
-
-  const match = /^([a-f0-9]{64})\.json$/.exec(path.basename(file));
-  const digest = createHash("sha256").update(bytes).digest("hex");
-  if (!match || match[1] !== digest) {
-    invalidContext(file, "content SHA-256 does not match the descriptor filename");
+// #956 round 3: install the signal-forwarding scaffolding before ANYTHING
+// else in this process — env var setup, the bun-version probe, spawning the
+// child — gets a chance to run. The three `process.once` listeners used to
+// go up only after spawn() (below) returned; a scheduler preemption right
+// after that syscall was enough for a signal to arrive with no listener yet,
+// and the runtime's default (process-terminating) disposition killed the
+// launcher outright, never reaching the child at all. `child` starts
+// unset: a signal that arrives before it exists is queued and flushed the
+// moment it does; if this process ends up never spawning one (the
+// direct-import branch below), the queued signal is re-raised against
+// ourselves once we hand default disposition back, so it behaves exactly
+// like the runtime's own default rather than being silently swallowed.
+let child;
+let childExited = false;
+const pendingSignals = [];
+const forwardHandlers = new Map();
+const forwardSignal = (signal) => {
+  if (childExited) return;
+  if (!child) {
+    pendingSignals.push(signal);
+    return;
   }
-
-  let descriptor;
   try {
-    descriptor = JSON.parse(bytes.toString("utf8"));
-  } catch (error) {
-    invalidContext(file, error instanceof Error ? error.message : String(error));
-  }
-  if (
-    typeof descriptor !== "object" ||
-    descriptor === null ||
-    Array.isArray(descriptor) ||
-    descriptor.version !== 1 ||
-    Object.keys(descriptor).sort().join("\0") !== "environment\0version"
-  ) {
-    invalidContext(file, "expected the scheduler context v1 schema");
+    child.kill(signal);
+  } catch {
+    // Child exited in the race between the check above and here.
   }
-  const environment = descriptor.environment;
-  const expected = [...CONTEXT_KEYS, "PATH"].sort();
-  const keys =
-    environment && typeof environment === "object" && !Array.isArray(environment)
-      ? Object.keys(environment).sort()
-      : [];
-  if (keys.length !== expected.length || keys.some((key, index) => key !== expected[index])) {
-    invalidContext(file, "environment keys do not match the scheduler context v1 schema");
-  }
-  for (const key of CONTEXT_KEYS) {
-    const value = environment[key];
-    if (
-      typeof value !== "string" ||
-      value.trim() === "" ||
-      CONTROL_CHARACTER.test(value) ||
-      (!path.posix.isAbsolute(value) && !path.win32.isAbsolute(value))
-    ) {
-      invalidContext(file, `${key} must be an absolute path without control characters`);
-    }
-  }
-  if (typeof environment.PATH !== "string" || CONTROL_CHARACTER.test(environment.PATH)) {
-    invalidContext(file, "PATH must be a string without control characters");
-  }
-  return environment;
+};
+// `.once`, not `.on`: Node/Bun suppress a signal's default
+// (process-terminating) disposition for as long as ANY listener stays
+// registered for it. A persistent `.on` listener would still be registered
+// when the `process.kill(process.pid, result.signal)` re-raise below runs at
+// shutdown, swallowing it and leaving this launcher exiting 0 instead of
+// reflecting the child's signal. `.once` consumes only the
+// externally-delivered signal that triggers the forward, so the re-raise
+// correctly falls through to the OS default.
+for (const signal of ["SIGTERM", "SIGINT", "SIGHUP"]) {
+  const handler = () => forwardSignal(signal);
+  forwardHandlers.set(signal, handler);
+  process.once(signal, handler);
 }
 
-const contextIndex = process.argv.indexOf(CONTEXT_ARG);
-let contextValid = true;
-if (contextIndex !== -1) {
-  try {
-    const contextPath = process.argv[contextIndex + 1];
-    if (!contextPath) throw new Error(`${CONTEXT_ARG} requires an absolute path.`);
-    const environment = readSchedulerContext(contextPath);
-    const expected = [...CONTEXT_KEYS, "PATH"].sort();
-    for (const key of expected) process.env[key] = environment[key];
-    process.argv.splice(contextIndex, 2);
-  } catch (error) {
-    console.error(`akm: ${error instanceof Error ? error.message : String(error)}`);
-    process.exitCode = 78;
-    contextValid = false;
-  }
-}
+// A scheduled row sets its environment itself (a cron `VAR=value` prefix, a
+// launchd plist's EnvironmentVariables), and the scheduler supplies PATH, so
+// runtime selection below needs nothing from it. A row written by 0.9.0 –
+// 0.9.17-alpha.6 passes `--scheduler-context <descriptor>` instead; it passes
+// through untouched, and the CLI applies it (`consumeSchedulerContextArg` in
+// src/cli.ts). This launcher used to re-validate the descriptor with its own
+// copy of the schema, and that copy rejected every descriptor 0.9.17 wrote.
 
-if (contextValid) {
-  process.env.AKM_LAUNCHER_NODE = process.execPath;
-  process.env.AKM_LAUNCHER_PATH = fileURLToPath(import.meta.url);
-  // #956: lets the child (and its lock payloads) name the launcher pid
-  // alongside its own, and lets the child's parent-death watchdog tell a
-  // real launcher-managed run apart from a direct `bun src/cli.ts` run.
-  process.env.AKM_LAUNCHER_PID = String(process.pid);
+process.env.AKM_LAUNCHER_NODE = process.execPath;
+process.env.AKM_LAUNCHER_PATH = fileURLToPath(import.meta.url);
+// #956: lets the child (and its lock payloads) name the launcher pid
+// alongside its own, and lets the child's parent-death watchdog tell a
+// real launcher-managed run apart from a direct `bun src/cli.ts` run.
+process.env.AKM_LAUNCHER_PID = String(process.pid);
 
-  if (!process.versions.bun) {
-    const [major = 0, minor = 0] = process.versions.node.split(".").map(Number);
-    if (major < 22) {
-      console.error("The akm-cli npm package requires Node.js >= 22 to bootstrap.");
-      process.exit(1);
-    }
+if (!process.versions.bun) {
+  const [major = 0, minor = 0] = process.versions.node.split(".").map(Number);
+  if (major < 22) {
+    console.error("The akm-cli npm package requires Node.js >= 22 to bootstrap.");
+    process.exit(1);
   }
+}
 
-  const bunProbe = process.versions.bun
-    ? { status: 0, stdout: process.versions.bun }
-    : spawnSync("bun", ["--version"], {
-        encoding: "utf8",
-        stdio: ["ignore", "pipe", "ignore"],
-        timeout: 5_000,
-      });
-  const [bunMajor = 0] = (bunProbe.status === 0 ? bunProbe.stdout.trim() : "").split(".").map(Number);
-  const useBun = bunMajor >= 1;
-  const bunEntry = fileURLToPath(new URL("./cli.js", import.meta.url));
-  const nodeEntry = fileURLToPath(new URL("./cli-node.mjs", import.meta.url));
+const bunProbe = process.versions.bun
+  ? { status: 0, stdout: process.versions.bun }
+  : spawnSync("bun", ["--version"], {
+      encoding: "utf8",
+      stdio: ["ignore", "pipe", "ignore"],
+      timeout: 5_000,
+    });
+const [bunMajor = 0] = (bunProbe.status === 0 ? bunProbe.stdout.trim() : "").split(".").map(Number);
+const useBun = bunMajor >= 1;
+const bunEntry = fileURLToPath(new URL("./cli.js", import.meta.url));
+const nodeEntry = fileURLToPath(new URL("./cli-node.mjs", import.meta.url));
 
-  if (!useBun && !process.versions.bun) {
-    await import("./cli-node.mjs");
-  } else {
-    const command = useBun ? (process.versions.bun ? process.execPath : "bun") : "node";
-    const entry = useBun ? bunEntry : nodeEntry;
-    const runtime = useBun ? "Bun" : "Node.js";
-    const result = await new Promise((resolve) => {
-      const child = spawn(command, [entry, ...process.argv.slice(2)], {
-        stdio: "inherit",
-        env: process.env,
-        // #956: give the child its OWN process group on POSIX (`setsid()` —
-        // does not touch its inherited stdio; see `spawnsOwnProcessGroup` in
-        // src/core/subprocess.ts for the Windows caveat that rules this out
-        // there). Without this, a spawned child shares the launcher's
-        // process group by default, so a signal delivered to that GROUP (a
-        // terminal's Ctrl-C, or `kill -SIGINT -<pgid>`) reaches the child
-        // directly AND the launcher, which then also forwards it — a real
-        // second signal lands microseconds after the first. The child's
-        // `process.once(signal, ...)` handler has already unregistered
-        // itself for its first (direct) copy, so the second falls through
-        // to the runtime's default disposition (immediate termination) and
-        // the child's graceful shutdown (lock release, in-flight abort)
-        // never runs. Detaching the child's process group makes the
-        // launcher's forward below the SOLE delivery path to the child, so
-        // it is always exactly one signal.
-        detached: process.platform !== "win32",
-      });
-      // A `kill <launcher-pid>` (a scheduler timeout, a supervisor, an
-      // operator) used to end only this wrapper, orphaning the bun child —
-      // it kept running (and holding locks) for as long as its own work took.
-      // Forward the same signal so the child dies with its parent. Never
-      // forward once the child has already exited: forwarding to a
-      // dead/replaced pid would be at best a no-op and at worst a signal to
-      // an unrelated process that reused the pid.
-      let childExited = false;
-      child.once("exit", () => {
-        childExited = true;
-      });
-      const forwardSignal = (signal) => {
-        if (childExited) return;
-        try {
-          child.kill(signal);
-        } catch {
-          // Child exited in the race between the check above and here.
-        }
-      };
-      // `.once`, not `.on`: Node/Bun suppress a signal's default
-      // (process-terminating) disposition for as long as ANY listener stays
-      // registered for it. A persistent `.on` listener would still be
-      // registered when the `process.kill(process.pid, result.signal)`
-      // re-raise below runs at shutdown, swallowing it and leaving this
-      // launcher exiting 0 instead of reflecting the child's signal. `.once`
-      // consumes only the externally-delivered signal that triggers the
-      // forward, so the re-raise correctly falls through to the OS default.
-      for (const signal of ["SIGTERM", "SIGINT", "SIGHUP"]) {
-        process.once(signal, () => forwardSignal(signal));
-      }
-      child.once("error", (error) => resolve({ error }));
-      child.once("exit", (code, signal) => resolve({ code, signal }));
+if (!useBun && !process.versions.bun) {
+  // No child is ever spawned on this path — the imported module runs
+  // in-process, so it IS the work, and the runtime's ordinary default signal
+  // disposition is exactly correct for it. Hand that back (the forwarding
+  // listeners above no longer apply here), re-raising anything that already
+  // arrived so it is not silently swallowed by a listener that now does
+  // nothing.
+  for (const [signal, handler] of forwardHandlers) process.removeListener(signal, handler);
+  if (pendingSignals.length > 0) process.kill(process.pid, pendingSignals[0]);
+  else await import("./cli-node.mjs");
+} else {
+  const command = useBun ? (process.versions.bun ? process.execPath : "bun") : "node";
+  const entry = useBun ? bunEntry : nodeEntry;
+  const runtime = useBun ? "Bun" : "Node.js";
+  const result = await new Promise((resolve) => {
+    child = spawn(command, [entry, ...process.argv.slice(2)], {
+      stdio: "inherit",
+      env: process.env,
+      // #956: give the child its OWN process group on POSIX (`setsid()` —
+      // does not touch its inherited stdio; see `spawnsOwnProcessGroup` in
+      // src/core/subprocess.ts for the Windows caveat that rules this out
+      // there). Without this, a spawned child shares the launcher's
+      // process group by default, so a signal delivered to that GROUP (a
+      // terminal's Ctrl-C, or `kill -SIGINT -<pgid>`) reaches the child
+      // directly AND the launcher, which then also forwards it — a real
+      // second signal lands microseconds after the first. The child's
+      // `process.once(signal, ...)` handler has already unregistered
+      // itself for its first (direct) copy, so the second falls through
+      // to the runtime's default disposition (immediate termination) and
+      // the child's graceful shutdown (lock release, in-flight abort)
+      // never runs. Detaching the child's process group makes the
+      // launcher's forward below the SOLE delivery path to the child, so
+      // it is always exactly one signal.
+      detached: process.platform !== "win32",
     });
+    // A `kill <launcher-pid>` (a scheduler timeout, a supervisor, an
+    // operator) used to end only this wrapper, orphaning the bun child —
+    // it kept running (and holding locks) for as long as its own work took.
+    // Forward the same signal so the child dies with its parent. Never
+    // forward once the child has already exited: forwarding to a
+    // dead/replaced pid would be at best a no-op and at worst a signal to
+    // an unrelated process that reused the pid.
+    child.once("exit", () => {
+      childExited = true;
+    });
+    // Flush whatever arrived in the (now much smaller) window between the
+    // listeners going up and the child existing to receive them.
+    for (const signal of pendingSignals.splice(0)) forwardSignal(signal);
+    child.once("error", (error) => resolve({ error }));
+    child.once("exit", (code, signal) => resolve({ code, signal }));
+  });
 
-    if (result.error) {
-      console.error(`akm launcher could not start ${runtime}: ${result.error.message}`);
-      process.exitCode = 127;
-    } else if (result.signal) {
-      process.kill(process.pid, result.signal);
-    } else {
-      process.exitCode = result.code ?? 1;
-    }
+  if (result.error) {
+    console.error(`akm launcher could not start ${runtime}: ${result.error.message}`);
+    process.exitCode = 127;
+  } else if (result.signal) {
+    process.kill(process.pid, result.signal);
+  } else {
+    process.exitCode = result.code ?? 1;
   }
 }

package/dist/akm-migrate

@@ -6,6 +6,40 @@
 import { spawn, spawnSync } from "node:child_process";
 import { fileURLToPath } from "node:url";
 
+// #956 round 3: install the signal-forwarding scaffolding before ANYTHING
+// else in this process — the Node-version check, the bun-version probe,
+// spawning the child — gets a chance to run. See the matching fix and
+// comment in scripts/node-runtime/akm: the three `process.once` listeners
+// used to go up only after spawn() (below) returned; a scheduler preemption
+// right after that syscall was enough for a signal to arrive with no
+// listener yet, and the runtime's default (process-terminating) disposition
+// killed the launcher outright, never reaching the child at all. `child`
+// starts unset: a signal that arrives before it exists is queued and
+// flushed the moment it does.
+let child;
+let childExited = false;
+const pendingSignals = [];
+const forwardSignal = (signal) => {
+  if (childExited) return;
+  if (!child) {
+    pendingSignals.push(signal);
+    return;
+  }
+  try {
+    child.kill(signal);
+  } catch {
+    // Child exited in the race between the check above and here.
+  }
+};
+// `.once`, not `.on`: see the matching comment in scripts/node-runtime/akm —
+// a persistent `.on` listener would still be registered when the
+// `process.kill(process.pid, result.signal)` re-raise below runs,
+// suppressing the OS default disposition and leaving this launcher exiting
+// 0 instead of reflecting the child's signal.
+for (const signal of ["SIGTERM", "SIGINT", "SIGHUP"]) {
+  process.once(signal, () => forwardSignal(signal));
+}
+
 if (!process.versions.bun) {
   const [major = 0, minor = 0] = process.versions.node.split(".").map(Number);
   if (major < 22) {
@@ -34,7 +68,7 @@ const nodeEntry = fileURLToPath(new URL("./scripts/akm-migrate-node.js", import.
   const command = process.versions.bun ? process.execPath : useBun ? "bun" : process.execPath;
   const entry = process.versions.bun || useBun ? bunEntry : nodeEntry;
   const result = await new Promise((resolve) => {
-    const child = spawn(command, [entry, ...process.argv.slice(2)], {
+    child = spawn(command, [entry, ...process.argv.slice(2)], {
       stdio: "inherit",
       env,
       // #956: own process group on POSIX so the launcher's forward below is
@@ -43,27 +77,12 @@ const nodeEntry = fileURLToPath(new URL("./scripts/akm-migrate-node.js", import.
       // directly — see the matching comment in scripts/node-runtime/akm.
       detached: process.platform !== "win32",
     });
-    let childExited = false;
     child.once("exit", () => {
       childExited = true;
     });
-    const forwardSignal = (signal) => {
-      if (childExited) return;
-      try {
-        child.kill(signal);
-      } catch {
-        // Child exited in the race between the check above and here.
-      }
-    };
-    // `.once`, not `.on`: see the matching comment in
-    // scripts/node-runtime/akm — a persistent `.on` listener would still be
-    // registered when the `process.kill(process.pid, result.signal)`
-    // re-raise below runs, suppressing the OS default disposition and
-    // leaving this launcher exiting 0 instead of reflecting the child's
-    // signal.
-    for (const signal of ["SIGTERM", "SIGINT", "SIGHUP"]) {
-      process.once(signal, () => forwardSignal(signal));
-    }
+    // Flush whatever arrived in the (now much smaller) window between the
+    // listeners going up and the child existing to receive them.
+    for (const signal of pendingSignals.splice(0)) forwardSignal(signal);
     child.once("error", (error) => resolve({ error }));
     child.once("exit", (code, signal) => resolve({ code, signal }));
   });

package/dist/assets/hints/cli-hints-full.md

@@ -245,10 +245,9 @@ akm improve --no-push                         # commit but skip push for this ru
 akm improve --sync                            # force sync even on strategies that disable it
 ```
 
-Strategy sync defaults: `catchup`, `consolidate`, `default`,
-`graph-refresh`, `quick`, and `thorough` auto-commit + push;
-`proactive-maintenance` and `reflect-distill` skip sync entirely. Override
-with `--sync` / `--no-sync` flags.
+Strategy sync defaults: `catchup`, `consolidate`, `default`, `quick`, and
+`thorough` auto-commit + push; `proactive-maintenance` and `reflect-distill`
+skip sync entirely. Override with `--sync` / `--no-sync` flags.
 
 The `--writable` flag on `akm bundle add` opts a remote git bundle into push-on-sync:
 
@@ -308,8 +307,8 @@ akm bundle create                                      # Initialize working bund
 akm setup                                     # Interactive wizard: bundle + LLM/embedding + agent + registry config
 akm setup --dir ~/custom-bundle                # Run the wizard against a custom bundle path
 akm setup --yes                               # Non-interactive, accepts all defaults
-akm index                                     # Rebuild search index (metadata enrichment when configured)
-akm index --full                              # Full reindex (metadata enrichment when configured)
+akm index                                     # Rebuild search index
+akm index --full                              # Full reindex
 akm bundle list                                      # List all sources
 akm lint                                      # Structural lint over the bundle; exits 0 regardless of findings
 akm lint --fix                                # Auto-fix Tier 1 issues
@@ -399,7 +398,7 @@ akm agent --model sonnet --prompt "..."         # Model override (aliases or exa
 ```sh
 akm info                                       # Capabilities, bundle dir, index stats, semantic-search status
 akm health                                     # Runtime diagnostics; exit 0 ok / 4 warn / 1 fail
-akm health --report                            # Adds accept-rate and graph-coverage metrics
+akm health --report                            # Adds accept-rate metrics
 akm log                                        # Append-only event stream (mutations, feedback, indexing)
 akm log --ref <ref>                            # One asset's event trail
 akm log --since @offset:<id>                   # Durable row-id cursor — poll this to follow the stream

package/dist/assets/improve-strategies/catchup.json

@@ -16,9 +16,6 @@
     "memoryInference": {
       "enabled": false
     },
-    "graphExtraction": {
-      "enabled": false
-    },
     "extract": {
       "enabled": false
     },

package/dist/assets/improve-strategies/consolidate.json

@@ -5,7 +5,6 @@
     "distill": { "enabled": false },
     "consolidate": { "enabled": true, "allowedTypes": ["memory"], "maxChunkSize": 25 },
     "memoryInference": { "enabled": false },
-    "graphExtraction": { "enabled": false },
     "extract": { "enabled": false },
     "triage": { "enabled": false },
     "validation": { "enabled": false },

package/dist/assets/improve-strategies/default.json

@@ -1,5 +1,5 @@
 {
-  "description": "Standard improve pass — reflect, distill, advisory consolidation, graph extraction, and validation. Memory inference is listed below but only runs when experimental.improveAutonomy is set; improve-stage extract and proactive maintenance off.",
+  "description": "Standard improve pass — reflect, distill, consolidation (promotion plus the reviewed pair-pass retire/supersede proposals), and validation. Memory inference is listed below but only runs when experimental.improveAutonomy is set; improve-stage extract and proactive maintenance off.",
   "processes": {
     "reflect": {
       "enabled": true,
@@ -9,7 +9,6 @@
     "distill": { "enabled": true, "allowedTypes": ["memory"], "requirePlannedRefs": true },
     "consolidate": { "enabled": true, "allowedTypes": ["memory"] },
     "memoryInference": { "enabled": true },
-    "graphExtraction": { "enabled": true },
     "extract": { "enabled": false, "triage": { "enabled": true, "minScore": 2 } },
     "validation": { "enabled": true },
     "proactiveMaintenance": { "enabled": false, "dueDays": 30, "maxPerRun": 15 },

package/dist/assets/improve-strategies/proactive-maintenance.json

@@ -1,5 +1,5 @@
 {
-  "description": "Opt-in proactive-maintenance pass — reflect, distill, proposal triage (promote, high budget), and the proactive-maintenance lane (maxPerRun 100); consolidate/memoryInference/graphExtraction/extract off. Sync disabled: an interrupted run would otherwise leave an uncommitted backlog.",
+  "description": "Opt-in proactive-maintenance pass — reflect, distill, proposal triage (promote, high budget), and the proactive-maintenance lane (maxPerRun 100); consolidate/memoryInference/extract off. Sync disabled: an interrupted run would otherwise leave an uncommitted backlog.",
   "processes": {
     "reflect": {
       "enabled": true,
@@ -8,7 +8,6 @@
     "distill": { "enabled": true, "allowedTypes": ["memory"] },
     "consolidate": { "enabled": false },
     "memoryInference": { "enabled": false },
-    "graphExtraction": { "enabled": false },
     "extract": { "enabled": false },
     "validation": { "enabled": false },
     "triage": {

package/dist/assets/improve-strategies/quick.json

@@ -1,5 +1,5 @@
 {
-  "description": "Reflect-only pass — no extract, distill, consolidate, memoryInference, or graphExtraction.",
+  "description": "Reflect-only pass — no extract, distill, consolidate, or memoryInference.",
   "processes": {
     "reflect": {
       "enabled": true,
@@ -9,7 +9,6 @@
     "distill": { "enabled": false },
     "consolidate": { "enabled": false },
     "memoryInference": { "enabled": false },
-    "graphExtraction": { "enabled": false },
     "triage": { "enabled": false },
     "validation": { "enabled": false },
     "proactiveMaintenance": { "enabled": false }

package/dist/assets/improve-strategies/reflect-distill.json

@@ -1,5 +1,5 @@
 {
-  "description": "Reflect + distill pass — reflect, distill, memoryInference, and proposal triage (promote); proactiveMaintenance/consolidate/graphExtraction/extract off. Sync disabled: an interrupted run would otherwise leave an uncommitted backlog.",
+  "description": "Reflect + distill pass — reflect, distill, memoryInference, and proposal triage (promote); proactiveMaintenance/consolidate/extract off. Sync disabled: an interrupted run would otherwise leave an uncommitted backlog.",
   "processes": {
     "reflect": {
       "enabled": true,
@@ -8,7 +8,6 @@
     "distill": { "enabled": true, "allowedTypes": ["memory"], "requirePlannedRefs": false },
     "consolidate": { "enabled": false },
     "memoryInference": { "enabled": true },
-    "graphExtraction": { "enabled": false },
     "extract": {
       "enabled": false,
       "timeoutMs": 300000,

package/dist/assets/improve-strategies/thorough.json

@@ -18,9 +18,6 @@
     "memoryInference": {
       "enabled": true
     },
-    "graphExtraction": {
-      "enabled": true
-    },
     "extract": {
       "enabled": false,
       "triage": {

package/dist/assets/prompts/consolidate-pair.md

@@ -0,0 +1,20 @@
+You compare two assets from one person's agent-memory library (memories and knowledge notes an AI coding agent reads). Asset A is the OLDER one and asset B the NEWER one, by the dates shown.
+
+Classify the relation between them as exactly one of:
+
+- "duplicate": they state the same durable facts. Wording, title or formatting may differ, but neither adds a claim a reader would need that the other lacks.
+- "subsumed": one of them contains every durable claim of the other, plus more. The smaller one is redundant.
+- "supersedes": B updates, corrects, reverses or replaces a claim in A (a newer version, a changed decision, a fixed bug, a new value). A is now stale or wrong on that point.
+- "contradicts": they make logically exclusive claims about the same thing and nothing shows which one is current.
+- "overlap": same subject, but each has durable claims the other lacks. Keeping both loses nothing; merging them would keep both sets of claims.
+- "unrelated": different subjects or different facts that happen to share words.
+
+Rules:
+- A durable claim is a fact, decision, value, command, path, number or rule someone would act on. Ignore dates, headings, tags and phrasing.
+- Prefer "overlap" over "duplicate" when either asset has a specific detail (a number, command, file, version or condition) that the other lacks.
+- "supersedes" needs a specific claim in A that B changes. Being newer or longer is not enough.
+- "contradicts" needs two claims that cannot both be true. Different scope, project or time is not a contradiction.
+
+Set "redundant" to "A" or "B" when that asset could be removed with no loss (only for "duplicate" or "subsumed"; for "duplicate" name the less complete or older one), else null. Set "stale" to "A" when the relation is "supersedes", else null.
+
+Answer ONLY with JSON: {"relation": "...", "redundant": "A"|"B"|null, "stale": "A"|null, "confidence": 0.0-1.0, "reason": "<at most 25 words>"}