cargo-hauler 0.6.5 → 0.6.7

package/CHANGELOG.md

@@ -1,5 +1,17 @@
 # Changelog
 
+## 0.6.7
+
+### Patch Changes
+
+- 592863f: Make daemon replacement directional. Upgrading with long-lived sessions still on a previous plugin produced a war: the old clients shut down the new daemon on every hook call (and failed to start their own), the new clients started it again, and no daemon lived longer than two seconds. Now only a newer install replaces a daemon. The `shutdown` request carries the client's version; the daemon refuses a shutdown from a client older than itself or from one that sends no version (`shutdown-refused`), and a client that finds a newer daemon fails as `DaemonNewer` without touching it: `hauler exec` runs cargo directly with that reason, hooks continue, and `hauler status` / `hauler daemon status` name the newer daemon. `hauler daemon stop` from an older install is refused the same way.
+
+## 0.6.6
+
+### Patch Changes
+
+- 60fd579: Spawn the daemon from an absolute entry path. The daemon runs with the state dir as its cwd, so a relative entry (a host running the plugin script from its own directory, or a relative plugin root) resolved to `<state dir>/scripts/hauler.mjs` and every start died with `MODULE_NOT_FOUND`; with version gating that repeated on each hook call after an upgrade. The entry is now resolved against the client's cwd and checked for existence, falling back to the package entry beside the bundled module and only then to the running script.
+
 ## 0.6.5
 
 ### Patch Changes

package/README.md

@@ -634,8 +634,12 @@ unset, the daemon reads kache's configured local store from
   `hauler_last` read the ledger with the daemon marked `stopped` or
   `unresponsive`. Before any live daemon reply is parsed, these reads apply
   the one-version rule and replace a daemon left running by a previous
-  install. If replacement fails, they report that failure instead of reading
-  the stale payload.
+  install. Replacement is directional: only a newer install replaces a
+  daemon. A client older than the daemon it finds — a session still on a
+  previous plugin — never shuts it down (the daemon refuses a shutdown from
+  an older or unversioned client), reports the daemon as newer, and runs
+  cargo directly. If replacement fails, the reads report that failure
+  instead of reading the stale payload.
 - The state directory is not migrated between installs. Every rendered
   document names the one in use (`state dir …` in the header; `stateRoot` in
   `--json`), so a `CARGO_HAULER_STATE_DIR` change is visible on the next