akm-opencode 0.7.6 → 0.8.0-rc.8

package/index.ts

@@ -74,7 +74,7 @@ const AKM_WORKFLOW_INSTRUCTION = [
   "Use AKM as a reusable knowledge and workflow stash.",
   "",
   "Before writing from scratch:",
-  "1. Use `akm_search` or `akm_curate`.",
+  "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 the dedicated v0.7.0 tools for the proposal flow: `akm_proposal` (list/show/diff/accept/reject), `akm_reflect`, `akm_propose`, and `akm_distill`. Fall back to `akm_help` for any verb without a dedicated tool.",
@@ -1135,7 +1135,16 @@ function extractToolRefs(
 const AKM_HINTS_PREFIX = [
   "# AKM is available in this session",
   "",
-  "You have an AKM stash on this machine. Before writing anything from scratch, call `akm_search` or `akm_curate` to see if the stash already covers it. Record `akm_feedback <ref> positive|negative` whenever an asset materially helps or misses, and use `akm_remember` to persist durable learnings so future sessions inherit them.",
+  "You have an AKM stash on this machine. Before writing anything from scratch, call `akm_curate` with a task description that includes the current project name to find relevant assets with LLM-reranked relevance scores.",
+  "",
+  "**Choosing the right lookup command:**",
+  "",
+  "- **`akm_curate` (query including project name)** — use this when starting any new task, looking for patterns, docs, skills, or workflows. Always include the current project name or domain in the query so the reranker can filter cross-project noise. This is the PRIMARY lookup command.",
+  '  - Good: `akm_curate("akm CLI improve command performance analysis")`',
+  '  - Bad: `akm_curate("improve performance analysis")` (missing project context — pulls unrelated stash noise)',
+  "- **`akm_search` (known name)** — 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.",
+  "",
+  "Record `akm_feedback <ref> positive|negative` whenever an asset materially helps or misses, and use `akm_remember` to persist durable learnings so future sessions inherit them.",
   "",
   AKM_WORKFLOW_INSTRUCTION,
 ].join("\n")
@@ -2288,6 +2297,8 @@ export const AkmPlugin: Plugin = async ({ client, worktree, directory }) => {
               ref: captured,
             })
             await maybeIndexSessionMemory(logClient, sid, type, captured)
+            // Auto-signal so improve picks up this session memory on the next run.
+            runCliSyncRaw(["feedback", captured, "--positive", "--note", "session checkpoint: auto-signal for improve eligibility"], AKM_CURATE_TIMEOUT_MS)
           }
           if (type === "session.compacted") {
             writeStructuredEvent({
@@ -2335,6 +2346,8 @@ export const AkmPlugin: Plugin = async ({ client, worktree, directory }) => {
             ref: captured,
           })
           await maybeIndexSessionMemory(logClient, sid, "stop", captured)
+          // Auto-signal so improve picks up this session memory on the next run.
+          runCliSyncRaw(["feedback", captured, "--positive", "--note", "session checkpoint: auto-signal for improve eligibility"], AKM_CURATE_TIMEOUT_MS)
         }
       } catch (error: unknown) {
         await logHookFailure(logClient, "stop", error)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "akm-opencode",
-  "version": "0.7.6",
+  "version": "0.8.0-rc.8",
   "type": "module",
   "description": "OpenCode plugin for AKM v0.7.0 - search, show, and manage extension assets via the akm CLI, including vaults, wikis, workflows, the proposal queue, lesson assets, and reflect/propose/distill commands, with agentic hooks that auto-load relevant stash assets, record feedback, and harvest session memories so the stash improves every session.",
   "keywords": [