akm-cli 0.9.17-alpha.8 → 0.9.17

package/dist/storage/repositories/proposals-repository.js

@@ -168,6 +168,50 @@ function validatePresentMetadata(meta) {
     if (Object.hasOwn(meta, "eligibilitySource") && typeof meta.eligibilitySource !== "string") {
         invalidPresentField("eligibilitySource");
     }
+    if (Object.hasOwn(meta, "promotionSource") && typeof meta.promotionSource !== "string") {
+        invalidPresentField("promotionSource");
+    }
+    if (Object.hasOwn(meta, "promotionSourceHash") && typeof meta.promotionSourceHash !== "string") {
+        invalidPresentField("promotionSourceHash");
+    }
+    if (Object.hasOwn(meta, "retirement")) {
+        const retirement = meta.retirement;
+        if (typeof retirement !== "object" ||
+            retirement === null ||
+            typeof retirement.retiredRef !== "string" ||
+            typeof retirement.successorRef !== "string" ||
+            typeof retirement.cosine !== "number" ||
+            !Number.isFinite(retirement.cosine) ||
+            (retirement.judgeLabel !== "duplicate" &&
+                retirement.judgeLabel !== "subsumed" &&
+                retirement.judgeLabel !== "supersedes") ||
+            typeof retirement.judgeReason !== "string" ||
+            typeof retirement.retiredContentHash !== "string" ||
+            typeof retirement.successorContentHash !== "string" ||
+            (retirement.reason !== "duplicate" && retirement.reason !== "subsumed" && retirement.reason !== "superseded")) {
+            invalidPresentField("retirement");
+        }
+    }
+    if (Object.hasOwn(meta, "retiredArchive")) {
+        const archive = meta.retiredArchive;
+        if (typeof archive !== "object" ||
+            archive === null ||
+            !Array.isArray(archive.dirs) ||
+            archive.dirs.length === 0 ||
+            archive.dirs.some((dir) => typeof dir !== "string" || dir.length === 0)) {
+            invalidPresentField("retiredArchive");
+        }
+    }
+    if (Object.hasOwn(meta, "retireAcceptIntent")) {
+        const intent = meta.retireAcceptIntent;
+        if (typeof intent !== "object" ||
+            intent === null ||
+            typeof intent.assetPath !== "string" ||
+            intent.assetPath.length === 0 ||
+            typeof intent.backupContent !== "string") {
+            invalidPresentField("retireAcceptIntent");
+        }
+    }
 }
 /**
  * Convert a raw `ProposalRow` to the public `Proposal` shape.
@@ -233,6 +277,13 @@ export function proposalRowToProposal(row) {
         ...(typeof meta.eligibilitySource === "string"
             ? { eligibilitySource: meta.eligibilitySource }
             : {}),
+        ...(typeof meta.promotionSource === "string" ? { promotionSource: meta.promotionSource } : {}),
+        ...(typeof meta.promotionSourceHash === "string" ? { promotionSourceHash: meta.promotionSourceHash } : {}),
+        ...(meta.retirement !== undefined ? { retirement: meta.retirement } : {}),
+        ...(meta.retiredArchive !== undefined ? { retiredArchive: meta.retiredArchive } : {}),
+        ...(meta.retireAcceptIntent !== undefined
+            ? { retireAcceptIntent: meta.retireAcceptIntent }
+            : {}),
     };
 }
 /**
@@ -291,6 +342,16 @@ export function proposalToRowValues(proposal, stashDir) {
         metaObj.acceptedTarget = proposal.acceptedTarget;
     if (proposal.eligibilitySource !== undefined)
         metaObj.eligibilitySource = proposal.eligibilitySource;
+    if (proposal.promotionSource !== undefined)
+        metaObj.promotionSource = proposal.promotionSource;
+    if (proposal.promotionSourceHash !== undefined)
+        metaObj.promotionSourceHash = proposal.promotionSourceHash;
+    if (proposal.retirement !== undefined)
+        metaObj.retirement = proposal.retirement;
+    if (proposal.retiredArchive !== undefined)
+        metaObj.retiredArchive = proposal.retiredArchive;
+    if (proposal.retireAcceptIntent !== undefined)
+        metaObj.retireAcceptIntent = proposal.retireAcceptIntent;
     validatePresentMetadata(metaObj);
     return {
         id: proposal.id,

package/dist/storage/repositories/salience-repository.js

@@ -58,23 +58,6 @@ export function getAssetSalience(db, ref) {
     // Bun SQLite returns null (not undefined) when no row found.
     return row == null ? undefined : row;
 }
-/**
- * Load ALL rank scores from the asset_salience table (full-stash query).
- *
- * Used by the forgetting-safety report (plan §WS-1 step 7) to compute stash-wide
- * rank positions rather than pool-relative positions. Returns an empty Map when the
- * table is empty (first WS-1 run = no pre-existing rows).
- *
- * Order is unspecified; callers must sort before assigning 1-indexed positions.
- */
-export function getAllRankScores(db) {
-    const rows = db.prepare("SELECT asset_ref, rank_score FROM asset_salience").all();
-    const result = new Map();
-    for (const row of rows) {
-        result.set(row.asset_ref, row.rank_score);
-    }
-    return result;
-}
 // ── Plasticity helpers ────────────────────────────────────────────────────────
 /**
  * Increment `consecutive_no_ops` for an asset. Called after a no-op reflect/distill.
@@ -84,8 +67,7 @@ export function getAllRankScores(db) {
  * Invariant: recordNoOp must never originate rank_score semantics. If the asset has
  * no salience row yet (persistence's best-effort try/catch may have swallowed an
  * error), we do nothing — a no-op counter is meaningless without a rank_score row,
- * and a synthetic INSERT would fabricate a rank_score=0 entry that could produce
- * false catastrophic-forgetting signals in buildRankChangeReport.
+ * and a synthetic INSERT would fabricate a rank_score=0 entry with nothing behind it.
  */
 export function recordNoOp(db, ref) {
     db.prepare(`UPDATE asset_salience SET consecutive_no_ops = consecutive_no_ops + 1, updated_at = ? WHERE asset_ref = ?`).run(Date.now(), ref);

package/docs/migration/README.md

@@ -5,7 +5,7 @@ Upgrade guides and per-release migration notes.
 - [v0.9.1 -> v0.9.2 migration guide](v0.9.1-to-v0.9.2.md) -- Task-v2/task-v3 to task source v4 conversion, the durable-v4-family workflow boundary at executable `irVersion: 5`, and release behavior changes
 - [v0.9.2 release note](release-notes/0.9.2.md) -- Self-contained terminal upgrade summary shipped for `akm help migrate 0.9.2`
 - [v0.9.16 release note](release-notes/0.9.16.md) -- Source-bound scheduler grants, local execution authority, and split unsafe overrides
-- [v0.9.17 release note](release-notes/0.9.17.md) -- Tolerant readers, one config migration step, a plain scheduler list, less machinery, and the upgrade rehearsal gate
+- [v0.9.17 release note](release-notes/0.9.17.md) -- Consolidate's retire proposals and index layout 26, replacing the LLM entity graph with declared links, and `akm improve` scoped to what retrieval actually returns
 - [v0.8 -> current v0.9 migration guide](v0.8-to-v0.9.md) -- Package upgrade with fresh current config/state and explicit task conversion
 - [v0.7 -> v0.8 migration guide](v0.7-to-v0.8.md) -- Task schema and 0.8-era changes
 - [v0.5 -> v0.6 migration guide](https://github.com/itlackey/akm/blob/main/docs/migration/v0.5-to-v0.6.md) -- Terminology cut, registry schema v3, publisher changes

package/docs/migration/release-notes/0.9.17.md

@@ -1,43 +1,132 @@
 Migration notes for akm v0.9.17
 
-Upgrading no longer needs a manual step to keep working, and there is less
-machinery to break.
-
-Readers tolerate what older releases wrote, except task sources. A
-`version: 2` or `version: 3` task source fails on its own with
-`TASK_SCHEMA_VERSION_UNSUPPORTED`, naming `akm migrate apply`, which converts
-it to `version: 4` once; the other tasks keep running. A config key this
-release does not know -- retired, misspelled, or written by a newer release --
-is kept in memory and named once, never a reason to refuse the config;
-ordinary writes round-trip it, and `akm migrate apply` drops it.
-`akm migrate apply` has one config step (`configFile`): read config.json
-through the same pipeline every load runs and write the current shape back,
-under a backup.
-
-Scheduling is one list. `scheduler.enabled` in config.json holds the
-fully-qualified refs this host schedules (`bundle//tasks/x`). The
-0.9.17-alpha `{kind, ref, sourceId}` grant objects are read as their ref. A
-config with no list at all -- every release before 0.9.17 -- means "keep
-what is installed": the first `akm task sync` (or `setup`, `task enable`,
-`task disable`, `task add`) after the upgrade takes the akm-written rows
-already in the native scheduler as the host's choice, writes the list, and
-says so. An explicit list, empty or not, is never second-guessed. There are
-no grants, no source identities, no carry-forward and no fire-time gate.
-
-Removed machinery: filesystem transaction journals for proposal accept/revert
-(the asset is written, then the proposal row and its event are recorded in
-one state.db transaction; a crash in between leaves a re-acceptable pending
-proposal); the maintenance barrier, its per-process activity registry (the
-source of the lock-sidecar leak) and the SQLite lock-operation mutex (a lock
-file is one `O_EXCL` create); startup version reconciliation and
-`--host-local`; the akm-install enumerator and `akm upgrade --version/--tag`;
-the upgrade and transaction health advisories; the `akm info` compat
-manifest. `akm migrate apply` removes the files those left under `$DATA`,
-`$STATE` and `$CONFIG`.
-
-Every historical shape akm has written is exercised by the upgrade rehearsal
-(`tests/integration/upgrade-rehearsal/`) before each release: a real previous
-release builds a home, the candidate installs over it in place, and the
-rehearsal drives migrate, bundle list, search, show, task sync, health and a
-scheduled task's generated cron command, then confirms the previous release
-still runs against the candidate-written home.
+Run this after upgrading:
+
+```sh
+akm migrate apply
+akm task sync
+```
+
+akm migrate apply reads config.json through the normal load pipeline and
+writes its current shape back under a backup, dropping every retired key it
+finds -- run it with --dry-run first to see the exact list for your config.
+From 0.9.16, that includes index.graph.*, index.metadataEnhance,
+search.minScore, search.graphBoost.*, improve.utilityDecay.*, and a dozen
+smaller ones. None of them do anything any more -- leaving them in
+config.json is harmless until you run migrate apply, which drops them for
+good. It also deletes files nothing reads any more: 0.9.16's transaction
+journals ($DATA/txn/ and $DATA/txn-quarantine/), its maintenance barrier
+lock, and the maintenance-activities/ registry, which leaked an entry per
+process and reached 927 MB on one host. It also drops a leftover
+improve.strategies["graph-refresh"] override block, but not
+defaults.improveStrategy: "graph-refresh" itself -- if you set that, change
+it to a different strategy by hand, since graph-refresh now refuses
+outright, naming the retirement, rather than quietly running as a no-op. The
+shipped akm-graph-refresh-weekly task template is gone; remove or repoint
+any task that used it. Separately, akm search --no-project-context and akm
+proposal drain --policy/--max-diff-lines now fail as unknown flags; drop
+them from any script or task that still passes them.
+
+The first akm index after upgrading migrates index.db to layout 26 in
+place -- for a 0.9.16 index this includes a one-time full-text rebuild it
+was already due for, so budget a few seconds for a 24k-entry index rather
+than a fraction of one. This also drops the LLM entity-graph tables -- the
+per-file entity/relation extraction that fed akm show's old related list is
+retired -- and ends with a VACUUM that reclaims the space both steps free;
+akm index has never VACUUMed index.db before, so this is the first time it
+happens at all, not a repeat of something 0.9.16 already did. Nothing is
+re-embedded by this migration.
+
+Embeddings are a separate matter if you use a nomic-embed or E5 model:
+akm index now sends the model's own document template (nomic:
+"search_document: ", E5: "passage: ") instead of the raw text, which changes
+what gets embedded, so every entry re-embeds once on the next akm index.
+Qwen3, the BGE/mxbai/arctic family, and the default local model have no
+document template and keep their stored vectors untouched. Set
+embedding.documentTemplate: "" if you'd rather keep the old vectors than pay
+for a full re-embed. If you had index.metadataEnhance on before upgrading
+(it defaulted off), run akm index --full once afterward to replace the
+LLM-written descriptions it left behind with the plain deterministic ones --
+an ordinary incremental akm index does not touch them.
+
+The first akm task sync after upgrading rewrites every akm-managed
+scheduler row once, in place. Each row now sets its own AKM_BUNDLE_DIR
+(plus any AKM_CONFIG_DIR/AKM_DATA_DIR/AKM_CACHE_DIR/AKM_STATE_DIR the
+syncing shell had set explicitly) inline, instead of pointing at a
+--scheduler-context <file> descriptor, and a crontab's PATH moves the same
+way, into a # akm:env block next to the task rows. The rewrite keeps each
+row's existing launcher and schedule -- it is reported as an update, never
+an add or a remove -- and rows written by 0.9.0 through 0.9.16 keep firing
+normally until that sync runs. Once akm task doctor lists no binding still
+pointing at a descriptor file, the old $DATA/tasks/context/ files can be
+deleted.
+
+akm improve now reworks only what retrieval actually returned -- an asset a
+real search, curate, show, or feedback touched in the last 90 days -- plus
+material no improve stage has processed yet. The proactive-maintenance and
+high-salience lanes, and the memory consolidation judge, no longer reach
+into the unread tail of a stash; an asset left out this way shows up under a
+new retrieval gate in akm improve --dry-run and under akm health's
+not_retrieved skip reason, not silently.
+
+Consolidation gets a second pass. It compares each new-or-changed memory,
+flat knowledge/ file, or lesson against its nearest neighbours, and where an
+LLM judge calls a pair duplicate, subsumed, or superseding, it mints a
+reviewed retire proposal for the losing side -- nothing is retired
+automatically. Review these like any other proposal: akm proposal list
+--generator consolidate-pair (or just akm proposal list, which flags one
+carrying continuity risk inline), show, diff, then accept or reject.
+Accepting one archives the losing file instead of deleting it, and akm
+proposal revert restores it exactly; archived files are only deleted 30 days
+after retirement, and only once git holds them clean and unmodified.
+Accepting a promotion (a consolidate promote proposal, by a person or by
+triage auto-promotion) now also archives the source memory it was promoted
+from, so a promotion no longer leaves a duplicate sitting next to the
+knowledge doc it produced.
+
+akm proposal drain, and improve's own triage pre-pass, no longer take a
+policy. Both now accept only a proposal the quality judge passed on its
+exact content and reject an empty diff; everything else goes to
+processes.triage.judgment or waits for review -- including extract and
+consolidate proposals, which used to be auto-accepted on size alone under
+the personal-stash default.
+
+akm show no longer has a related field. It lists an asset's links instead:
+the relations a bundle already declares -- cross-references, supersededBy,
+a .derived memory's parent, a wiki's citations, resolved page links, a
+workflow's or task's target -- grouped outgoing/incoming/unresolved,
+computed with no LLM call. Curate's support refs are drawn from the same
+links now, not from the retired entity graph.
+
+akm info always exits 0 and always prints a report, even when something is
+wrong: an invalid config.json, a missing or unreadable bundle directory, or
+a locked/newer/corrupt index.db is named in the report (configError,
+bundleDirError, indexStats.unavailable) instead of failing the command or
+showing unexplained zeros. It also reports link counts per kind, including
+how many are unresolved.
+
+Decide every pending retire proposal -- akm proposal accept or reject --
+before downgrading to 0.9.16. Older releases predate the retire proposal
+shape entirely: akm proposal show/diff/drain exits 70 on one it doesn't
+recognize, and drain's own nightly pre-pass failing on the first pending
+retire proposal it meets stops that run's auto-promotion for the whole
+stash, not just for the one proposal.
+
+0.9.16 already refuses to open a newer-layout index.db outright
+(INDEX_SCHEMA_INCOMPATIBLE, naming the upgrade) and leaves the file
+untouched, so downgrading needs a fresh index: move index.db aside and run
+akm index --full under 0.9.16, which re-embeds everything from scratch.
+
+A workflow run started under 0.9.17 freezes its plan as irVersion 6,
+which 0.9.16 does not understand and refuses to resume
+(WORKFLOW_IR_VERSION_UNSUPPORTED) -- let any in-flight workflow runs finish
+before downgrading, or plan to restart them fresh under 0.9.16.
+
+The state.db migration that adds the improve ledger
+(028-improve-ledger) drops six tables 0.9.16 and earlier used
+(proposal_fingerprints and friends). Because it drops schema, the akm that
+runs it first copies the database to state.db.pre-028-improve-ledger.bak
+before making the change. That backup is a snapshot from the moment of
+upgrade -- restoring it to downgrade discards every proposal, event, and run
+state.db has recorded since, not just the ledger's own six tables, so treat
+it as a last resort rather than routine.

package/docs/migration/release-notes/README.md

@@ -7,6 +7,13 @@ live one level up in `docs/migration/`.
 
 ## Available notes
 
+- [0.9.17](0.9.17.md) — consolidate's retire proposals and continuity check,
+  promotions archiving their source memory, declared links replacing the LLM
+  entity graph, index layout 26, scheduler rows carrying their own context,
+  and `akm improve` scoped to what retrieval actually returns
+- [0.9.16](0.9.16.md) — source-bound scheduler grants, local execution
+  authority, config inheritance's portable-data boundary, and split unsafe
+  overrides
 - [0.9.15](0.9.15.md) — exit-code 75 for lease/state.db contention,
   `--require-engines` scheduled task templates, `--no-probe` cli-version
   skip, thinking-control wire forms, embedding re-embed safety and

package/docs/reference/cli.md

@@ -104,7 +104,7 @@ with an `INVALID_SHAPE_VALUE` usage error (exit 2) — an honest rejection rathe
 than a silent fallback. It returns a compact view suitable for capability
 discovery:
 
-- **show**: `type`, `name`, canonical `ref`, `description`, `tags`, `parameters`, `workflowTitle`, `action`, `run`, `origin`, `keys`, `related`, `links`
+- **show**: `type`, `name`, canonical `ref`, `description`, `tags`, `parameters`, `workflowTitle`, `action`, `run`, `origin`, `keys`, `links`
 
 ## Exit Codes and Error Envelope
 
@@ -195,8 +195,8 @@ akm setup
 The setup wizard configures AKM in two steps:
 
 **Step 1 — Small model connection** (for background processing)
-Configures the OpenAI-compatible endpoint and model used for `akm index`
-metadata enhancement and `akm remember --enrich`. Supports Ollama,
+Configures the OpenAI-compatible endpoint and model used for `akm improve`
+and `akm remember --enrich`. Supports Ollama,
 OpenAI, LM Studio, or any custom endpoint. Skipping disables enrichment features.
 
 **Step 2 — Agent connection** (for agentic commands)
@@ -300,10 +300,8 @@ invokes `akm index` directly should pass `--skip-if-locked` so it steps
 aside instead of piling up behind a longer rebuild (the shipped
 `index-refresh` task does this).
 
-`akm index` always rebuilds the search index and keeps metadata in the index.
-When a selected named LLM engine (`defaults.llmEngine` or an indexing-pass
-override) is configured and the per-pass gate allows it, metadata
-enhancement runs during indexing. In text mode, the default CLI UI shows a
+`akm index` always rebuilds the search index and keeps metadata in the
+index, generated deterministically. In text mode, the default CLI UI shows a
 spinner with processed-versus-total source counts; structured output modes
 (`json`, `yaml`, `jsonl`) stay clean and machine-readable.
 
@@ -320,8 +318,10 @@ Returns a JSON object with:
 | Field | Description |
 | --- | --- |
 | `version` | Current akm version |
-| `bundleDir` | Primary bundle directory — same resolution `akm bundle list` uses |
+| `bundleDir` | Primary bundle directory — same resolution `akm bundle list` uses. Falls back to the platform-default location when no bundle resolves. |
 | `defaultBundle` | Name of the primary bundle from config, or `null` when none is configured |
+| `configError` | Present only when `config.json` exists but could not be loaded (parse or schema failure); every config-derived field falls back to the same defaults a fresh install reports |
+| `bundleDirError` | Present when a bundle IS configured (an env override or `bundles.*` in config) but its path doesn't resolve, OR when the platform-default fallback itself can't resolve (e.g. `HOME` unset) — absent for the ordinary "no bundle created yet" state, where `bundleDir` needs no explanation |
 | `dataDir` | Resolved data directory (`getDataDir()`) |
 | `configDir` | Resolved config directory (`getConfigDir()`) |
 | `cacheDir` | Resolved cache directory (`getCacheDir()`) |
@@ -331,7 +331,14 @@ Returns a JSON object with:
 | `semanticSearch` | Semantic search status: `mode`, `status`, and optional `reason`/`message` |
 | `registries` | Configured registries |
 | `sourceProviders` | Configured sources (filesystem, git, website, npm) |
-| `indexStats` | Index stats: `entryCount`, `byType` (per-asset-type breakdown), `links` (declared links per kind with `total` and `unresolved`; absent when the index holds none), `lastBuiltAt`, `hasEmbeddings` |
+| `indexStats` | Index stats: `entryCount`, `byType` (per-asset-type breakdown), `links` (declared links per kind with `total` and `unresolved`; absent when the index holds none), `lastBuiltAt`, `hasEmbeddings`, `unreadable` (index.db exists but the filesystem refuses to read it — a permissions problem), `unavailable` (index.db is readable but the SQLite-level read didn't complete: locked by another akm process, a newer layout this akm can't understand, or a corrupt file) |
+
+`akm info` never refuses: an unreadable config, an unresolvable bundle
+directory, or an index.db that's locked, newer, older, corrupt, missing, or
+empty each degrade the relevant field(s) above instead of failing the
+command. It also never waits more than about 1.5s on a locked index.db,
+regardless of the shared 30s lock-wait every write command otherwise uses,
+and warns rather than refusing on an unrecognized flag.
 
 `semanticSearch.status` values:
 - `"ready-js"` — every entry has a vector; semantic search is active (the name is historical: `"ready-vec"`, the sqlite-vec variant, is gone)
@@ -389,7 +396,7 @@ Primary result fields:
 | `improve` | Recent improve-loop counts derived from `improve_invoked`, `improve_skipped`, and `improve_completed` events |
 
 The `improve` section includes counts for planned refs, reflect/distill actions,
-memory-prune actions, memory-inference writes, graph-extraction refreshes,
+memory-prune actions, memory-inference writes,
 session-extraction outcomes (`sessionsScanned`, `sessionsExtracted`, `proposalsCreated`),
 dead-URL detections, and skip reasons observed in the selected time window.
 
@@ -432,13 +439,6 @@ for an infrastructure reason (`llm_unavailable`, `read_failed`, `exception`,
 `locked_concurrent`) — naming the reason and, when recorded, the engine — and
 `pass` otherwise, with per-outcome counts.
 
-The indexed entity graph (entities/relations extracted from bundle assets) has
-no dedicated inspection command; its summary counts surface as an info-level
-metric in `akm health`. Graph data is automatically re-extracted on the first
-`akm improve` cycle after a `DB_VERSION` upgrade. The graph backs `akm show`'s
-`related` list; it does not affect search ranking. Curate's support refs come
-from declared links (`akm show`'s `links`), not from this graph.
-
 ### search
 
 Search bundle assets, registries, or both.
@@ -703,8 +703,7 @@ workflow and task targets name), `incoming` (the assets that name it), and
 kind is `{ "total": n, "refs": [...] }` with at most 10 refs; `total` counts
 them all. The field is omitted when nothing links either way. Links are read
 from frontmatter and parsed structure at index time, with no model; they do
-not affect search ranking. `related` is separate: the LLM entity graph's
-shared-entity neighbours.
+not affect search ranking.
 
 Opaque fragment shows and `--context lead` keep `ref` as the canonical parent
 identity and add
@@ -2528,7 +2527,7 @@ clock, or session-log changes.
 
 `plan.processes` (#947) is the resolved process -> engine -> model routing
 table: one row per improve process (`reflect`, `distill`, `consolidate`,
-`memoryInference`, `graphExtraction`, `extract`, `validation`, `triage`,
+`memoryInference`, `extract`, `validation`, `triage`,
 `proactiveMaintenance`), plus a `triage.judgment` row when the strategy
 configures a judgment engine. Each row carries `enabled`, the resolved
 `engine`/`model` (llm-backed processes only) and `engineKind`, this process's
@@ -2583,7 +2582,7 @@ field on the result (`result_json` in `improve_runs`, and in the
 `calls`, `failures`, `promptTokens`, `completionTokens`, `totalTokens`,
 `reasoningTokens`, and `totalDurationMs`. `noCalls` lists every LLM-backed
 process (`reflect`, `distill`, `consolidate`, `memoryInference`,
-`graphExtraction`, `extract`, `validation` — not `triage`/`proactiveMaintenance`,
+`extract`, `validation` — not `triage`/`proactiveMaintenance`,
 which never make an attributable LLM call themselves) the active strategy
 enabled but that ended the run with zero calls, each with a `reason` drawn
 from the existing skip-reason vocabulary: `"engine_unavailable"` (also in
@@ -2721,6 +2720,7 @@ akm proposal list
 akm proposal list --queue team-bundle
 akm proposal list --status pending|accepted|rejected|reverted
 akm proposal list --ref skills/deploy
+akm proposal list --generator consolidate-pair
 ```
 
 | Flag | Description |
@@ -2729,6 +2729,12 @@ akm proposal list --ref skills/deploy
 | `--status` | Filter by `pending`, `accepted`, `rejected`, or `reverted` |
 | `--ref` | Filter by asset ref. A qualified ref preserves bundle identity; a short ref matches that concept in the selected queue |
 | `--type` | Reserved type filter |
+| `--generator <name>` | Filter by generator/source (e.g. `reflect`, `distill`, `consolidate-pair`) — the same value `accept`/`reject --generator` take |
+
+Each retire proposal's `retirement.continuityRisk`, when present, also shows
+in the default listing (`⚠ continuity-risk` inline) and in `proposal show`'s
+text output (the specific failing/unverified queries) — see
+[Retirement continuity](https://github.com/itlackey/akm/blob/main/docs/architecture/improvement.md#retirement-continuity).
 
 Each proposal record carries an optional `confidence` field (0..1) emitted by
 reflect/propose runs. It is recorded for triage and ranking only — there is no

package/docs/reference/configuration.md

@@ -314,7 +314,7 @@ can select `engine`, `model`, `timeoutMs`, and LLM request overrides:
         "engine": "fast",
         "processes": {
           "reflect": { "llm": { "temperature": 0.2 } },
-          "graphExtraction": { "model": "qwen3-small" }
+          "memoryInference": { "model": "qwen3-small" }
         }
       }
     }
@@ -327,13 +327,6 @@ incompatible engine never falls back to another engine. Built-in strategies
 are complete presets. User-defined strategies inherit omitted fields from the
 built-in `default` strategy before applying their own overrides.
 
-Graph extraction also reads `index.graph`. Its `engine`, `model`, `timeoutMs`
-and `llm` apply over the strategy-wide values, and `processes.graphExtraction`
-overrides them. `processes.graphExtraction.batchSize` and `includeTypes` win
-over `index.graph.graphExtractionBatchSize` and `graphExtractionIncludeTypes`;
-with neither set, the batch size is 4 and the types are `memory` and
-`knowledge`.
-
 `processes.triage.judgment` explicitly controls the optional judgment tier.
 Use `true` to enable it, `false` to disable it, or an object with `enabled`,
 `engine`, `model`, `timeoutMs`, and/or `llm` overrides. Existing object values
@@ -848,7 +841,23 @@ profile identities.
 config that still sets it is simply ignored — it still loads, unvalidated
 and without warning.
 
-`index.graph.lazyGraphExtraction` is retired in 0.9.17: `akm show` and
-`akm curate` no longer extract or queue graph work, and graph extraction runs
-only in `akm improve`. A config that still sets it loads; the key is named
-once as unknown, and `akm migrate apply` removes it.
+`index.graph.*` and every strategy's `processes.graphExtraction.*` are retired
+in 0.9.17-alpha.9: the LLM entity graph they configured is gone —
+`akm show`'s links come from declared links instead (see `## Strategies`
+above). A config that still sets them loads; each key is named once as
+unknown, and `akm migrate apply` removes it. The built-in `graph-refresh`
+strategy is retired too, but not the same way as an ordinary unknown name:
+naming it via `--strategy` or a task always fails with a message pointing at
+the retirement, even when `improve.strategies["graph-refresh"]` still has a
+leftover override from customizing the built-in (the message names it;
+`akm migrate apply` drops it — a leftover override is never resolved as a new
+custom strategy, which would silently run a full, unplanned improve pass).
+`defaults.improveStrategy: "graph-refresh"` still loads config successfully;
+the refusal happens lazily, when the strategy is actually resolved.
+
+`improve.strategies.<name>.processes.consolidate.incrementalSince` and
+`.neighborsPerChanged` are retired in 0.9.17-alpha.9: the consolidate pair
+pass is now the candidate generator, narrowing per initiator through the
+improve ledger rather than a global time window. A config that still sets
+either key loads; each is named once as unknown, and `akm migrate apply`
+removes it.

package/docs/reference/data-and-telemetry.md

@@ -199,7 +199,6 @@ the set of types the code actually emits at HEAD (verified against every
 | `extract_triaged` | The pre-LLM extract triage gate evaluated at least one session | `evaluated`, `passed`, `triagedOut`, `sourceRun` (aggregated) |
 | `schema_repair_invoked` | The schema-repair pass inside `akm improve` (`runSchemaRepairPass`) attempts to patch missing frontmatter on an asset that failed schema validation. **There is no `akm lint --repair` flag** — `lint` has `--fix`/`--auto-fix`, unrelated to this event | `ref`, outcome |
 | `proactive_selected` | The proactive-maintenance selector runs (once per `akm improve` run) | `count`, `dueTotal`, `neverReflected` (aggregated) |
-| `improve_salience_rank_change` | Bundle-wide rank-change report, from the second improve run onward | `stashSize`, `totalChanged`, `forgettingCandidates`, `topDrops` |
 | `events_purged` | Old events deleted by improve maintenance (90-day default retention) | `purgedCount`, `retentionDays` |
 | `improve_runs_purged` | Old `improve_runs` rows deleted by improve maintenance (same retention window as events) | `purgedCount`, `retentionDays` |
 | `state_db_vacuumed` | state.db was VACUUMed after the retention purge because more than half its pages were free | `pagesBefore`, `pagesAfter`, `freelistRatioBefore` |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "akm-cli",
-  "version": "0.9.17-alpha.8",
+  "version": "0.9.17",
   "type": "module",
   "description": "akm (Agent Knowledge Manager) — a portable, local-first capability library for AI agents. Discover, load, share, and improve reusable skills, scripts, workflows, and knowledge across any shell-capable coding agent, including Claude Code, OpenCode, and Cursor.",
   "keywords": [