akm-opencode 0.9.6202608312025 → 0.9.8202609020939

package/README.md

@@ -1,6 +1,6 @@
 # akm-opencode
 
-OpenCode plugin for [AKM](https://github.com/itlackey/akm) `^0.9.6`. It exposes exactly five public tools and uses lifecycle hooks to bring relevant AKM context into a session.
+OpenCode plugin for [AKM](https://github.com/itlackey/akm) `^0.9.8`. It exposes exactly five public tools and uses lifecycle hooks to bring relevant AKM context into a session.
 
 ## Installation
 
@@ -18,13 +18,13 @@ Add the plugin to `opencode.json`:
 | --- | --- |
 | `akm_search` | Search configured bundles or registries. `source` accepts `local`, `registry`, `all`, or a configured bundle name. |
 | `akm_show` | Show a concept by `[bundle//]conceptId[#fragment]`. A fragment selects a Markdown section. |
-| `akm_curate` | Return ranked concepts for a task or topic. |
+| `akm_curate` | Return ranked concepts for a task or topic. Optional `pack` is a token budget that returns the selected local assets' full content in one response; registry hits are omitted from packed items. |
 | `akm_feedback` | Record positive or negative feedback for a concept. |
 | `akm_remember` | Save durable knowledge as a searchable memory. |
 
 `akm_search`, `akm_show`, and `akm_curate` call the bundled AKM read APIs in process. `akm_feedback` and `akm_remember` use the compatible AKM CLI because they mutate AKM state. Failures return structured results and are logged through OpenCode app logging.
 
-Use the `ref` returned by search or curate directly with show or feedback. Concept IDs look like `skills/code-review`, `memories/release-retro`, or `team-playbook//knowledge/deploy#Rollback`.
+Use the `ref` returned by search or curate directly with show or feedback. When `akm_curate.pack` is set, the response already includes packed local content, so a separate show call is only needed for omitted or registry-only hits. Concept IDs look like `skills/code-review`, `memories/release-retro`, or `team-playbook//knowledge/deploy#Rollback`.
 
 ## Lifecycle Hooks
 
@@ -113,7 +113,7 @@ These three are read once, when the plugin module is imported, so they must be s
 
 ## Usage
 
-1. Start with `akm_curate` for task-oriented discovery.
+1. Start with `akm_curate` for task-oriented discovery; set `pack` when you want the selected local content immediately.
 2. Use `akm_search` when you know the concept name and need its exact ID.
 3. Fetch the full concept with `akm_show` before relying on it.
 4. Record the outcome with `akm_feedback`.

package/index.ts

@@ -1,6 +1,6 @@
 import { type Plugin, tool } from "@opencode-ai/plugin"
 // @ts-expect-error akm-cli does not publish declarations for this in-process entrypoint.
-import { akmCurate } from "akm-cli/dist/commands/read/curate.js"
+import { akmCurate, packCuratedHits } from "akm-cli/dist/commands/read/curate.js"
 // @ts-expect-error akm-cli does not publish declarations for this in-process entrypoint.
 import { akmSearch } from "akm-cli/dist/commands/read/search.js"
 // @ts-expect-error akm-cli does not publish declarations for this in-process entrypoint.
@@ -48,7 +48,7 @@ const AKM_REQUIRED_VERSION_RANGE = AKM_VERSION_RANGE
 // The consent banner's package specification is kept explicit so it remains a
 // valid npm install target even if the shared compatibility range later grows
 // extra clauses. Keep it in sync with the minimum supported stable release.
-const AKM_RECOMMENDED_INSTALL_REF = "akm-cli@^0.9.6"
+const AKM_RECOMMENDED_INSTALL_REF = "akm-cli@^0.9.8"
 
 const AKM_AUTO_FEEDBACK = (process.env.AKM_AUTO_FEEDBACK ?? "1") !== "0"
 const AKM_AUTO_CURATE = (process.env.AKM_AUTO_CURATE ?? "1") !== "0"
@@ -194,7 +194,7 @@ const akmVersionProbeCache = new Map<string, string | null>()
 // whitespace-token extractor and is the single source of truth here.
 const PROPOSED_QUALITY_WARNING = "Do not treat proposed assets as curated until accepted."
 const AKM_WORKFLOW_INSTRUCTION = [
-  "# AKM workflow (v0.9.6)",
+  "# AKM workflow (v0.9.7)",
   "",
   "Use AKM as a reusable knowledge and workflow bundle.",
   "",
@@ -820,7 +820,7 @@ async function getPendingProposalCount(client: LogCapableClient, sessionID?: str
   const command = resolveAkmCommand()
   if (typeof command === "object" && "ok" in command) return { count: 0, unsupported: true }
   try {
-    // AKM 0.9.6 canonical proposal-queue listing path: `akm proposal list`.
+    // AKM 0.9.7 canonical proposal-queue listing path: `akm proposal list`.
     const stdout = execResolvedAkm(command, ["proposal", "list", "--status", "pending", "--format", "json"], {
       encoding: "utf8",
       timeout: AKM_PENDING_PROPOSAL_TIMEOUT_MS,
@@ -2662,11 +2662,24 @@ async function runInProcess(
   meta: CliLogMeta,
 ): Promise<string> {
   try {
+    if (
+      operation === "curate"
+      && input.pack !== undefined
+      && (typeof input.pack !== "number" || !Number.isInteger(input.pack) || input.pack <= 0)
+    ) {
+      throw new Error("pack must be a positive integer token budget")
+    }
     const result = operation === "search"
       ? await akmSearch(input as Parameters<typeof akmSearch>[0])
       : operation === "show"
         ? await akmShowUnified(input as Parameters<typeof akmShowUnified>[0])
-        : await akmCurate(input as Parameters<typeof akmCurate>[0])
+        : await (async () => {
+            const { pack, ...curateInput } = input
+            const curated = await akmCurate(curateInput as Parameters<typeof akmCurate>[0])
+            return typeof pack === "number"
+              ? packCuratedHits(curated, pack)
+              : curated
+          })()
     const output = JSON.stringify(result)
     const refs = extractAkmRefsFromString(output)
     noteRecentRefs(meta.sessionID, refs)
@@ -3580,18 +3593,19 @@ const akmPlugin: Plugin = async ({ client, worktree, directory }) => {
         // zero akm_* calls while curation was demonstrably available (#95).
         // Leading with the decision — when to reach for this instead of just
         // reading the file — is what it has to win on.
-        description: "Reach for this 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 — including a file already present in the workspace, since having read a file does not mean you know its schema. PRIMARY discovery entry point for the bundle: describe the task in natural language and this returns the top matches as a ranked list. Pass a hit's ref to akm_show before relying on it, then record akm_feedback once the result is known.",
+        description: "Reach for this 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 — including a file already present in the workspace, since having read a file does not mean you know its schema. PRIMARY discovery entry point for the bundle: describe the task in natural language and this returns the top matches as a ranked list. Set pack to a token budget when you need the selected local assets' full content in one response; otherwise pass a hit's ref to akm_show before relying on it. Record akm_feedback once the result is known.",
         args: {
           query: tool.schema.string().describe("Task, topic, or natural-language description of what you want to do."),
           type: tool.schema.enum(ASSET_TYPES as unknown as [string, ...string[]]).optional().describe("Optional asset type filter."),
           limit: tool.schema.number().optional().describe("Maximum number of curated matches to return. Defaults to 4."),
           source: tool.schema.string().optional().describe("Search source: 'local', 'registry', 'all', or a configured bundle name."),
+          pack: tool.schema.number().optional().describe("Optional positive token budget for packing ranked local assets' full content into this response. Registry hits are never packed."),
         },
-        async execute({ query, type, limit, source }, context) {
+        async execute({ query, type, limit, source, pack }, context) {
           return runInProcess(
             client as unknown as LogCapableClient,
             "curate",
-            { query, type: type === "any" ? undefined : type, limit, source },
+            { query, type: type === "any" ? undefined : type, limit, source, pack },
             { toolName: "akm_curate", sessionID: context.sessionID, directory: context.directory },
           )
         },

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "akm-opencode",
-  "version": "0.9.6202608312025",
+  "version": "0.9.8202609020939",
   "type": "module",
   "description": "OpenCode plugin for AKM 0.9 with in-process search, show, and curate tools plus feedback and remember.",
   "keywords": [
@@ -39,7 +39,7 @@
   },
   "dependencies": {
     "@opencode-ai/plugin": "^1.18.14",
-    "akm-cli": "^0.9.6"
+    "akm-cli": "^0.9.8"
   },
   "devDependencies": {
     "@types/node": "^26.1.1",

package/shared/akm-version.ts

@@ -13,27 +13,31 @@
 // same code path runs on both sides.
 //
 // A single caret clause anchored at the stable release covers the whole
-// supported line: `^0.9.6` admits stable 0.9.6 and later 0.9.x releases.
-// 0.9.6 is the compatibility floor: its ref grammar, progressive-search
-// metadata, workflow lifecycle, and task/workflow wire contracts are the ones
-// these plugins implement.
+// supported line: `^0.9.8` admits stable 0.9.8 and later 0.9.x releases.
+// 0.9.8 is the compatibility floor, and the reason is a one-way one: 0.9.8
+// adds state migrations 025 and 026, so once any 0.9.8 command opens
+// `state.db` an older CLI refuses to open it at all. A home these plugins
+// have driven is therefore a 0.9.8+ home, and admitting 0.9.7 would point
+// the gate at a CLI that cannot read it. Its ref grammar, progressive-search
+// metadata, token-budgeted curate packing, workflow lifecycle, and
+// task/workflow wire contracts are the ones these plugins implement.
 //
-// KNOWN GAP: NO prerelease satisfies this range — not 0.9.6-rc.1, and not a
-// *future* line such as 0.9.7-rc.1. That is node-semver's documented behavior
+// KNOWN GAP: NO prerelease satisfies this range — not 0.9.8-rc.1, and not a
+// *future* line such as 0.9.9-rc.1. That is node-semver's documented behavior
 // and the vendored matcher reproduces it: a prerelease only satisfies a range
 // whose lower bound is a prerelease with the same major.minor.patch. Admitting
 // a prerelease line again is an explicit one-clause edit here
-// (`^0.9.6 || ^0.9.7-rc.1`) when such a build actually needs testing — a
+// (`^0.9.8 || ^0.9.9-rc.1`) when such a build actually needs testing — a
 // deliberate opt-in rather than a range that silently accepts untested
 // prereleases.
 //
 // Earlier 0.9 releases are deliberately excluded as well: accepting them
 // would silently pass the version gate onto a CLI with retired ref and
-// workflow contracts.
+// workflow contracts, or one that cannot open a migrated state.db.
 
 import { satisfies } from "./vendor-semver"
 
-export const AKM_VERSION_RANGE = "^0.9.6"
+export const AKM_VERSION_RANGE = "^0.9.8"
 
 /**
  * True when `version` is a valid semver string that satisfies

package/shared/recall-policy.ts

@@ -36,7 +36,7 @@ export function shouldRecall(prompt: string, options?: { activeWorkflow?: boolea
     return { shouldRecall: false, reason: "skip-chitchat", query: text, scopeHints }
   }
   // Reuse the resolver-facing parser rather than carrying a second, stale
-  // grammar here. AKM 0.9.6 refs are [bundle//]conceptId[#fragment]; retired
+  // grammar here. AKM 0.9.7 refs are [bundle//]conceptId[#fragment]; retired
   // type:name strings must not turn an otherwise low-signal prompt into an
   // explicit AKM recall.
   if (/\bakm\b|\bbundle\b/.test(lower) || extractAkmRefsFromString(text).length > 0) {