akm-opencode 0.9.7202608312104 → 0.9.9202609021827

package/README.md

@@ -1,6 +1,6 @@
 # akm-opencode
 
-OpenCode plugin for [AKM](https://github.com/itlackey/akm) `^0.9.7`. 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
 

package/index.ts

@@ -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.7"
+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"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "akm-opencode",
-  "version": "0.9.7202608312104",
+  "version": "0.9.9202609021827",
   "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.7"
+    "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.7` admits stable 0.9.7 and later 0.9.x releases.
-// 0.9.7 is the compatibility floor: its ref grammar, progressive-search
-// metadata, token-budgeted curate packing, 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.7-rc.1, and not a
-// *future* line such as 0.9.8-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.7 || ^0.9.8-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.7"
+export const AKM_VERSION_RANGE = "^0.9.8"
 
 /**
  * True when `version` is a valid semver string that satisfies