akm-opencode 0.9.21202610012143 → 0.9.21202610030351

package/README.md

@@ -85,7 +85,6 @@ Every kill switch below is opt-out and reads the same way: only the literal `0`
 | `AKM_AUTO_CURATE` | `1` | Set to `0` to disable automatic prompt curation. |
 | `AKM_AUTO_FEEDBACK` | `1` | Set to `0` to disable automatic feedback: the retrospective ("that worked") confirmation. |
 | `AKM_AUTO_LEARNING` | `1` | Set to `0` to disable prompt-signal capture and automatic learning/skill proposal submission. Native session extraction is controlled separately by `AKM_AUTO_MEMORY`. |
-| `AKM_AUTO_HINTS` | `1` | Set to `0` to skip the per-session `akm hints` call. The missing-bundle warning is deliberately not gated on this: it explains why the bundle is empty in the first place. |
 | `AKM_AUTO_MEMORY` | `1` | Set to `0` to disable interval-gated native-session extraction through `akm proposal extract`. The Claude plugin honours the same variable for its `SessionEnd` extraction. |
 | `AKM_INDEX_ON_SESSION_END` | `1` | Set to `0` to skip the `akm index` refresh. It runs only on `session.deleted` — never on `session.idle`, which fires after every turn. |
 | `AKM_WRITE_GATE` | `observe` | The format-declaration write gate (#99). When a file the session **read** declares a format your bundle documents — an `apiVersion:` namespace, a `yaml-language-server` pragma, a `$schema` key, an XML root namespace — and that asset has not been opened this session, the FIRST `edit`/`write` to that file is blocked once and the model is told which ref to read. It ships in `observe`: everything runs and the would-fire count lands in the ledger, but nothing is blocked. Set `enforce` to block, or `off`/`0` to disable it entirely. An unrecognized value is a configuration error — it logs one error per process and the gate refuses to run rather than guessing a default. It never fires on a file this session created: the create is recorded when it happens — a `write` to a path this session has not read, or an `edit` with an empty `oldString` — and that path stays insulated for the rest of the session, so reading back the model's own output does not re-arm it (ledger reason `session-created`). It is inert on `apply_patch` (which carries no file path) — that case logs one warning per process rather than failing quietly. |

package/dist/index.js

@@ -1217,7 +1217,6 @@ var AKM_AUTO_FEEDBACK = (process.env.AKM_AUTO_FEEDBACK ?? "1") !== "0";
 var AKM_AUTO_LEARNING = (process.env.AKM_AUTO_LEARNING ?? "1") !== "0";
 var AKM_AUTO_SKILL_PROPOSALS = (process.env.AKM_AUTO_SKILL_PROPOSALS ?? "1") !== "0";
 var AKM_AUTO_CURATE = (process.env.AKM_AUTO_CURATE ?? "1") !== "0";
-var AKM_AUTO_HINTS = (process.env.AKM_AUTO_HINTS ?? "1") !== "0";
 var AKM_PENDING_PROPOSAL_TIMEOUT_MS = Math.max(500, (Number(process.env.AKM_PENDING_PROPOSAL_TIMEOUT ?? "2") || 2) * 1000);
 var AKM_CURATE_LIMIT = Math.max(1, Number(process.env.AKM_CURATE_LIMIT ?? "5") || 5);
 var AKM_CURATE_MIN_CHARS = Math.max(1, Number(process.env.AKM_CURATE_MIN_CHARS ?? "16") || 16);
@@ -1275,19 +1274,6 @@ var pendingProposalSummaryCache = new Map;
 var retrospectiveState = new Map;
 var cachedAkmBundleDir;
 var PROPOSED_QUALITY_WARNING = "Do not treat proposed assets as curated until accepted.";
-var AKM_WORKFLOW_INSTRUCTION = [
-  "# AKM workflow (v0.9.21)",
-  "",
-  "Use AKM as a reusable knowledge and workflow bundle.",
-  "",
-  "Before writing or editing anything whose exact syntax or keys you are not certain of (a file already in the workspace included):",
-  "1. Use `akm_curate` with a query that includes the current project name/domain (primary discovery). Fall back to `akm_search` only when you already know an asset exists and need its exact ref.",
-  "2. Use `akm_show <ref>` before relying on an asset.",
-  "3. Record `akm_feedback` after the result is known.",
-  "4. Use `akm_remember` to preserve durable project knowledge.",
-  `5. ${PROPOSED_QUALITY_WARNING}`
-].join(`
-`);
 function readPackageVersion() {
   try {
     const raw = readFileSync3(path4.join(moduleDir, "package.json"), "utf8");
@@ -2420,19 +2406,9 @@ function warnIfWriteGateInert(client) {
 var AKM_HINTS_PREFIX = [
   "# AKM is available in this session",
   "",
-  "You have an AKM bundle on this machine. Before writing **or editing** a config file, manifest, schema, or command for any tool, format, or API whose exact syntax or keys you are not certain of, call `akm_curate` with a task description to find relevant assets with LLM-reranked relevance scores. A file already being present in the workspace is not evidence that you know its schema \u2014 the values may be given to you while the key names and nesting are not, so check the bundle for that format's conventions before you edit it.",
-  "",
-  "**Choosing the right lookup command:**",
-  "",
-  "- **`akm_curate`** \u2014 use this when starting any new task, looking for patterns, docs, skills, or workflows. This is the PRIMARY lookup command. akm automatically boosts assets that match the current project (cwd-anchored project-context ranking), so an explicit project name in the query is not required for ranking \u2014 but it still helps the reranker frame intent.",
-  '  - Good: `akm_curate("akm CLI improve command performance analysis")` (explicit framing, still ideal)',
-  '  - Bad: `akm_curate("improve performance analysis")` (too generic \u2014 the reranker has less to work with even with auto-boost)',
-  '- **`akm_search` (known name)** \u2014 use ONLY when you already know an asset exists (e.g. after `akm_show` returned "not found") and need to locate its exact ref. Do not use as a discovery tool.',
-  "- **`akm_show <bundle>//meta`** \u2014 when working in or with an unfamiliar bundle, read its optional `.meta/` orientation (purpose, key assets, conventions, maintainer) before diving in. `akm_show meta` reads your working bundle's `.meta/index.md`; `akm_show meta:<name>` reads other `.meta/` docs (e.g. `meta:about`). These docs are direct-read and never appear in `akm_search`.",
-  "",
-  "When an asset's content is wrong, stale or incomplete, call `akm_feedback <ref> negative` with a note saying <what is wrong and what should change>: negative feedback is what triggers a review and fix of the asset, so make the note specific. Call it with `positive` when an asset materially helped (it only improves ranking). A failed akm call is not feedback on the asset. Use `akm_remember` to persist durable learnings so future sessions inherit them.",
-  "",
-  AKM_WORKFLOW_INSTRUCTION
+  "- Assets for this project (skills, knowledge, memories, workflows) live in the AKM bundle. Before writing or editing a file whose format or keys you are not sure of, find them with `akm_curate` (by task) or `akm_search` (by name), and read one with `akm_show` before relying on it.",
+  "- Record `akm_feedback` on an asset once you know whether it helped; keep durable project knowledge with `akm_remember`.",
+  "- `akm hints` has this bundle's conventions; `akm help` has the CLI."
 ].join(`
 `);
 var AKM_CURATED_TAIL = "\n\nTip: call `akm_show <ref>` to fetch full content. If an asset is wrong, stale or incomplete, call `akm_feedback <ref> negative` with a note saying <what is wrong and what should change>: that queues it for review and a fix. Use `positive` when it helped.";
@@ -3110,7 +3086,7 @@ var akmPlugin = async ({ client, worktree, directory }) => {
           }
           if (!sessionHints.has(sid)) {
             const bundleWarning = await getAkmBundleWarning(logClient);
-            const hints = AKM_AUTO_HINTS ? await runHintsForSession(logClient, sid) : null;
+            const hints = await runHintsForSession(logClient, sid);
             const body = [bundleWarning, hints].filter(Boolean).join(`
 
 `);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "akm-opencode",
-  "version": "0.9.21202610012143",
+  "version": "0.9.21202610030351",
   "type": "module",
   "description": "OpenCode plugin for AKM with discovery tools, feedback, memory, and automatic learning proposals from corrections and recurring workflows.",
   "keywords": [