akm-cli 0.9.25-alpha.2 → 0.9.25-alpha.3

package/docs/reference/cli.md

@@ -2600,16 +2600,16 @@ default probe-on behavior) to check whether a named engine actually answers.
 
 `--show-prompt` (#952) is the cheapest way to exercise reflect alone: it
 builds the exact prompt reflect would send for one asset — the same source
-resolution, runner selection, feedback/schema-hint/related-lesson/rejected-
-proposal gathering `akm improve`'s live reflect step uses — and prints it
+resolution, runner selection, feedback/schema-hint/rejected-proposal
+gathering `akm improve`'s live reflect step uses — and prints it
 without reading a credential, so it never calls an engine. An LLM engine
 receives the reply's JSON Schema as `response_format`, and an agent engine as
 an instruction that dispatch appends to this prompt. Add
 `--format text` (the default JSON/yaml envelope escapes the prompt into one
 line, which defeats a by-eye read) to confirm by eye that recent feedback is
-framed as an unverified report to investigate (never a fact to insert
-verbatim) and that the response contract tells the model never to emit the
-truncation marker or any content from outside the shown asset.
+framed as a signal (never a fact to insert) and that the response contract asks
+only for `confidence` and a `frontmatterPatch` of `description`,
+`when_to_use` and `title`: akm keeps the body.
 
 When reinforced facts need promotion, `knowledge` is the higher-authority
 destination than `memory`.
@@ -2692,21 +2692,23 @@ authenticates its root; it never falls back to an ambient write target.
 #### proposal extract
 
 Extract durable insights from native coding-agent session files (claude-code,
-opencode) and queue them as proposals. This is the standalone entrypoint for
-session extraction — it replaces the legacy session-checkpoint hook and runs
-independently of the improve-stage extract toggle (see `improve` above).
+codex, opencode) and queue them as proposals. This is the standalone
+entrypoint for session extraction — it replaces the legacy session-checkpoint
+hook and runs independently of the improve-stage extract toggle (see `improve`
+above).
 
 ```sh
 akm proposal extract --type claude --session-id <id>
 akm proposal extract --type claude --since 24h
 akm proposal extract --type opencode --since 7d --dry-run
+akm proposal extract --type codex --since 24h
 akm proposal extract --auto                 # iterate every available harness
 akm proposal extract --type claude --location /custom/path --session-id <id>
 ```
 
 | Flag | Description |
 | --- | --- |
-| `--type <harness>` | Harness name (`claude`, `opencode`). Required unless `--auto`. |
+| `--type <harness>` | Harness name (`claude`, `codex`, `opencode`). Required unless `--auto`. |
 | `--session-id <id>` | Process only this session ID. When absent, discover sessions via `--since`. |
 | `--location <path>` | Override the harness's default session-discovery location. |
 | `--since <cutoff>` | Discovery cutoff. ISO timestamp or duration (`24h`, `7d`, `30m`). Default `24h`. |
@@ -2724,6 +2726,12 @@ session-log location on the current machine — and returns an aggregated
 per-harness `results`); the run exits non-zero only when every harness
 failed.
 
+The `codex` harness reads Codex's rollout files under `$CODEX_HOME/sessions`
+(`~/.codex/sessions` by default; `--location` points at another rollout
+directory). It lists a person's sessions, `codex exec` runs included, and
+leaves out the rollouts Codex writes for subagents and its other internal agents:
+those are not sessions of their own.
+
 There is no `akm proposal extract --watch`/`--debounce-ms` either (0.9.0:
 dropped — a foreground polling daemon in a one-shot CLI); the shipped
 `core/extract.yml` cron template (`akm proposal extract --auto` on a

package/docs/reference/configuration.md

@@ -467,9 +467,7 @@ guidance. When enabled, engine selection is judgment → triage → strategy →
 
 `processes.reflect.qualityGate` and `processes.distill.qualityGate` control
 each process's LLM-as-judge quality gate. Each is on unless it sets
-`enabled: false`, and each follows only its own switch. A reflect revision
-that changes the body is never auto-accepted; when the judge passes it, it
-waits for review. With the gate off, it waits for review too. The judge is the
+`enabled: false`, and each follows only its own switch. The judge is the
 process's own engine when that is an LLM engine, or the `defaults.llmEngine`
 engine when an agent generates. `engine`, `model`, `timeoutMs` and `llm` give the gate a judge of its own,
 resolved over the process's settings the way `triage.judgment` resolves over

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "akm-cli",
-  "version": "0.9.25-alpha.2",
+  "version": "0.9.25-alpha.3",
   "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": [