akm-cli 0.9.0-beta.32 → 0.9.0-beta.33

package/CHANGELOG.md

@@ -6,6 +6,22 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 
 ## [Unreleased]
 
+## [0.9.0-beta.33] — 2026-06-21
+
+### Fixed
+
+- **`akm extract` decoupled from the improve-stage toggle.** `processes.extract.enabled`
+  now gates extract only as a STAGE of `akm improve` (the active improve profile, per
+  #593/#594); an explicit `akm extract` command always runs. Previously dropping extract
+  from the daily improve profile silently disabled the standalone command (and its LLM
+  calls, via the shared `session_extraction` feature gate).
+- **`extract --session-id` now respects the content-hash ledger; `--force` overrides.**
+  Explicit single-session extraction previously bypassed the #602 already-extracted skip
+  unconditionally — re-paying the LLM on every call and risking double-extraction against
+  the cron. Now a targeted `extract --session-id <id>` is idempotent (skips an unchanged,
+  already-extracted session with zero LLM calls) and only `--force` re-extracts. This
+  makes a session-end hook firing `extract --session-id <id>` precise AND idempotent.
+
 ## [0.9.0-beta.32] — 2026-06-21
 
 ### Added

package/dist/commands/improve/extract.js

@@ -37,7 +37,7 @@ import { getAvailableHarnesses } from "../../integrations/session-logs/index.js"
 import { preFilterSession } from "../../integrations/session-logs/pre-filter.js";
 import { chatCompletion } from "../../llm/client.js";
 import { embed } from "../../llm/embedder.js";
-import { isLlmFeatureEnabled, tryLlmFeature } from "../../llm/feature-gate.js";
+import { tryLlmFeature } from "../../llm/feature-gate.js";
 import { sha256Hex } from "../../runtime.js";
 import { createProposal, isProposalSkipped } from "../proposal/validators/proposals.js";
 import { buildExtractPrompt, EXTRACT_JSON_SCHEMA, parseExtractPayload } from "./extract-prompt.js";
@@ -180,7 +180,7 @@ triage, sessionIndexing, schemaSimilarityCtx,
 // prior row + bypass flags are threaded in from the caller. Skipping here still
 // costs ZERO LLM calls (the expensive resource #602 protects); only the cheap
 // file read is incurred.
-prior, force, singleSession) {
+prior, force) {
     const warnings = [];
     let data;
     try {
@@ -201,10 +201,12 @@ prior, force, singleSession) {
     // #602 — content-hash skip. Computed on the RAW event stream immediately after
     // a successful read, BEFORE the pre-filter / minContentChars / triage gates, so
     // an unchanged session never reaches the LLM. Hash-based ⇒ clock-independent
-    // (immune to the Jun 11-12 timestamp double-extract/over-throttle bug). --force
-    // and single-session (explicit sessionId) modes bypass the skip entirely.
+    // (immune to the Jun 11-12 timestamp double-extract/over-throttle bug). The skip
+    // applies UNIFORMLY — including explicit `--session-id` targeting (so a
+    // session-end hook firing `extract --session-id <id>` is idempotent). ONLY
+    // `--force` overrides it to re-extract a previously-extracted session.
     const contentHash = hashSessionContent(data);
-    if (!force && !singleSession && shouldSkipAlreadyExtractedSession(prior, contentHash)) {
+    if (!force && shouldSkipAlreadyExtractedSession(prior, contentHash)) {
         return {
             sessionId: sessionRef.sessionId,
             harness: harness.name,
@@ -470,9 +472,13 @@ export async function akmExtract(options) {
     const extractProcess = activeProfile
         ? activeProfile.processes?.extract
         : config.profiles?.improve?.default?.processes?.extract;
-    const extractEnabled = activeProfile
-        ? resolveProcessEnabled("extract", activeProfile)
-        : isLlmFeatureEnabled(config, "session_extraction");
+    // The `extract.enabled` process toggle gates extract as a STAGE of `akm improve`
+    // (the activeProfile path) — consistent with #593/#594 where the active profile,
+    // not `default`, is the source of truth. An EXPLICIT `akm extract` invocation
+    // (no activeProfile) is a direct user/cron action and always runs; gating it on
+    // the default improve profile's stage toggle was a footgun — dropping extract
+    // from the daily improve profile would silently disable the standalone command.
+    const extractEnabled = activeProfile ? resolveProcessEnabled("extract", activeProfile) : true;
     // Feature-gate early so we get a clean "skipped because disabled" envelope.
     if (!extractEnabled) {
         return {
@@ -685,7 +691,7 @@ export async function akmExtract(options) {
             break;
         }
         try {
-            const result = await processSession(harness, summary, stashDir, config, llmConfig, chat, options.ctx, sourceRun, dryRun, timeoutMs, maxTotalChars, minContentChars, triage, sessionIndexing, schemaSimilarityCtx, prior, options.force === true, typeof options.sessionId === "string" && options.sessionId.length > 0);
+            const result = await processSession(harness, summary, stashDir, config, llmConfig, chat, options.ctx, sourceRun, dryRun, timeoutMs, maxTotalChars, minContentChars, triage, sessionIndexing, schemaSimilarityCtx, prior, options.force === true);
             sessions.push(result);
             // #626 — triage aggregation. A session reached the triage gate only when it
             // was NOT already preempted by an earlier skip (read_failed / too_short /

package/dist/llm/feature-gate.js

@@ -30,10 +30,14 @@ const FEATURE_LOCATION = {
     proposal_quality_gate: (cfg) => cfg.profiles?.improve?.default?.processes?.reflect?.qualityGate?.enabled ?? false,
     // Legacy default: false
     memory_contradiction_detection: (cfg) => cfg.profiles?.improve?.default?.processes?.consolidate?.contradictionDetection?.enabled ?? false,
-    // Default: true. Session extraction replaces the akm-plugin checkpoint hook
-    // and is the primary path for capturing durable signal from real sessions.
-    // Opt out via `profiles.improve.default.processes.extract.enabled: false`.
-    session_extraction: (cfg) => cfg.profiles?.improve?.default?.processes?.extract?.enabled ?? true,
+    // Always on at the LLM-wrapper level. Enablement is decided ONCE at the
+    // extract entry point (`akmExtract`): the `extract.enabled` process toggle
+    // gates extract as a STAGE of `akm improve` (the active improve profile, per
+    // #593/#594), while an explicit `akm extract` command always runs. Gating the
+    // inner LLM calls on `default.processes.extract.enabled` here was a footgun —
+    // dropping extract from the daily improve profile silently disabled the
+    // standalone `akm extract` command. (cfg unused — kept for resolver signature.)
+    session_extraction: (_cfg) => true,
 };
 /**
  * Pure predicate: is the named feature gate enabled in `config`?

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "akm-cli",
-  "version": "0.9.0-beta.32",
+  "version": "0.9.0-beta.33",
   "type": "module",
   "description": "akm (Agent Knowledge Management) — A package manager for AI agent skills, commands, tools, and knowledge. Works with Claude Code, OpenCode, Cursor, and any AI coding assistant.",
   "keywords": [