memcue-dsh 0.5.0 → 0.5.2

package/README.md

@@ -42,9 +42,12 @@ once; `memcue_correct` of an approved fact is a deliberate correction, not a can
 
 ## Supported dsh
 
-The memcue binary must be 0.4.0 or newer: the plugin asks `memcue version -json` when it loads and, on an older
-binary, turns the session card and extraction off with one warning (recall keeps working, because the 0.3 hook is
-compatible). A build from source reports a suffixed version and counts as the current tree.
+The plugin asks `memcue version -json` when it loads. Without a configured `binary` or `MEMCUE_BIN`, a missing binary
+or one older than the plugin's release is replaced by that release, installed into
+`$XDG_DATA_HOME/memcue/<version>/` (`MEMCUE_AUTO_INSTALL=0` turns that off): an older release may not open the base
+the new one writes. A binary older than 0.4.0 that stays, a configured one or a failed install, turns the session card
+and extraction off with one warning (recall keeps working). A build from source reports a suffixed version and counts
+as the current tree.
 
 Tested with `dsh 0.2.0-rc.2`. Both the repository bundle and the standalone package declare
 `>=0.2.0-rc.2 <0.3.0` peer ranges for `@deepseek-ai/dsh-llm` and `@deepseek-ai/dsh-tools`, so dsh's compatibility

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "memcue-dsh",
-  "version": "0.5.0",
+  "version": "0.5.2",
   "description": "memcue long-term memory for DeepSeek Harness (dsh): facts recalled before a step, extracted when a turn ends",
   "type": "module",
   "license": "MIT",

package/src/index.mjs

@@ -529,15 +529,19 @@ export function apply(ctx, config) {
 		}
 	}
 
-	// Check once that the binary has the commands the plugin uses. Without a configured binary, a missing or older
-	// one is replaced by the release of this plugin, installed or downloaded; until that is done recall uses what
-	// PATH has. Anything else turns the card and extraction off with one clear line instead of failing every turn.
+	// Check once that the binary has the commands the plugin uses. Without a configured binary, a missing one, or one
+	// older than this plugin's release, is replaced by that release, installed or downloaded: an older release may not
+	// open the base the plugin's release writes (#272). Until that is done recall uses what PATH has. Anything else
+	// turns the card and extraction off with one clear line instead of failing every turn.
 	const checkBinary = async () => {
 		let { found, reported } = await versionOf()
-		if (!settings.pinned && !(found && versionAtLeast(reported, MIN_BINARY))) {
-			let version = ''
+		let version = ''
+		try {
+			version = await pluginVersion()
+		} catch {}
+		if (!settings.pinned && !(found && versionAtLeast(reported, version || MIN_BINARY))) {
 			try {
-				version = await pluginVersion()
+				version = version || (await pluginVersion())
 				settings.binary = await install(version)
 				;({ found, reported } = await versionOf())
 			} catch (error) {