cargo-hauler 0.6.8 → 0.6.9

package/CHANGELOG.md

@@ -1,5 +1,12 @@
 # Changelog
 
+## 0.6.9
+
+### Patch Changes
+
+- e160307: Print usage and exit 2 when `hauler daemon` is missing or given an unknown subcommand, and accept `hauler daemon stop --force` as a no-op alias for stop (#138).
+- 8dfe1c3: Flag cargo that ran outside the broker. An agent that wraps cargo in a script calling the toolchain binary by absolute path (`~/.rustup/toolchains/*/bin/cargo`) slips past both the `tool/before` rewrite (the command never says `cargo`) and the PATH shim (never on PATH), so its builds get no lane, no attach, and no ledger row while the machine saturates. The `tool/after` preflight and route now recognise cargo's status lines (`   Compiling …`, `    Finished … profile`, `     Running …`) in the output of a command that named neither cargo nor hauler, record the call in the hook log with reason `cargo ran outside cargo-hauler`, and tell the agent to name `cargo` in the command or run `hauler exec -- cargo …`. A file reader showing a saved log (`tail build.log`) is not treated as a run. The skill now says not to wrap cargo that way — besides leaving the broker, a toolchain binary called directly sets no `RUSTUP_TOOLCHAIN`, so registry crates compile under the default toolchain and fail with `E0514` — and how to drop a rustc wrapper or pin a toolchain through the broker instead.
+
 ## 0.6.8
 
 ### Patch Changes

package/README.md

@@ -156,9 +156,16 @@ the full path). Only a matching command evaluates the parser and the rewrite.
 The `tool/after` entry runs the token test and one bounded socket ping to the
 daemon (the `session-completed` request with the session's hook-state cursor,
 500 ms, no Effect runtime); it loads the telemetry and notification code only
-when the command was cargo-related or the daemon reported finished tickets. A
-non-cargo call with nothing finished — or no daemon at all — exits with no
-output. Measured with `/usr/bin/time -v` on a Claude `ls -la` envelope, the
+when the command was cargo-related, the daemon reported finished tickets, or
+the command's output carries cargo's own status lines (`   Compiling …`,
+`    Finished … profile`) without the command naming cargo. That last case is
+cargo run through a wrapper script, an alias, or a shell variable — the one
+shape neither the rewrite nor the PATH shim sees, since a script can call the
+toolchain's `cargo` binary by absolute path. It is recorded in the hook log
+with its reason and the agent is told to name `cargo` in the command or use
+`hauler exec -- cargo …`; a file reader showing a saved log (`tail
+build.log`) is not mistaken for a run. A non-cargo call with nothing finished
+— or no daemon at all — exits with no output. Measured with `/usr/bin/time -v` on a Claude `ls -la` envelope, the
 compiled entries take ~50 ms wall and ~49 MB RSS, against ~100 ms and 64 MB
 for the 0.4.8 event-route wrappers with a shared runtime available and
 ~560 ms and 144 MB without one.
@@ -831,7 +838,7 @@ the same filter as its `session` field). Results carry
 | `event:session/start` | new session | daemon state and the no-kill rule as context |
 | `event:stop` | agent stopping | holds the stop while a foreground ticket is pending (bounded, re-deniable) |
 | `event:tool/before` | shell tool about to run | the preflight continues a non-cargo command without loading the route; otherwise rewrites `cargo …` to `hauler exec --session … --host … -- cargo …`, denies `cargo clean` during in-flight builds, brokers it while the daemon is too busy to answer |
-| `event:tool/after` | shell tool finished | the preflight pings the daemon once per call; the route records cargo commands and injects finished background-ticket results once per session |
+| `event:tool/after` | shell tool finished | the preflight pings the daemon once per call; the route records cargo commands, injects finished background-ticket results once per session, and flags cargo that ran unbrokered through a wrapper script (cargo status lines in the output of a command that never named cargo) |
 
 #### Skills
 

package/artifact/.claude-plugin/marketplace.json

@@ -1 +1 @@
-{"description":"Coalesce, schedule, and stream cargo so concurrent agent sessions share compiles instead of fighting locks.","name":"cargo-hauler-marketplace","owner":{"name":"cargo-hauler"},"plugins":[{"description":"Coalesce, schedule, and stream cargo so concurrent agent sessions share compiles instead of fighting locks.","name":"cargo-hauler","source":"./","version":"0.6.8"}]}
+{"description":"Coalesce, schedule, and stream cargo so concurrent agent sessions share compiles instead of fighting locks.","name":"cargo-hauler-marketplace","owner":{"name":"cargo-hauler"},"plugins":[{"description":"Coalesce, schedule, and stream cargo so concurrent agent sessions share compiles instead of fighting locks.","name":"cargo-hauler","source":"./","version":"0.6.9"}]}

package/artifact/.claude-plugin/plugin.json

@@ -1 +1 @@
-{"author":{"name":"cargo-hauler"},"description":"Coalesce, schedule, and stream cargo so concurrent agent sessions share compiles instead of fighting locks.","name":"cargo-hauler","version":"0.6.8"}
+{"author":{"name":"cargo-hauler"},"description":"Coalesce, schedule, and stream cargo so concurrent agent sessions share compiles instead of fighting locks.","name":"cargo-hauler","version":"0.6.9"}

package/artifact/.codex-plugin/plugin.json

@@ -1 +1 @@
-{"author":{"name":"cargo-hauler"},"description":"Coalesce, schedule, and stream cargo so concurrent agent sessions share compiles instead of fighting locks.","hooks":"./.codex-plugin/hooks.json","interface":{"capabilities":["mcp","hooks","skills"],"category":"Productivity","defaultPrompt":["Help me use cargo-hauler."],"developerName":"cargo-hauler","displayName":"cargo-hauler","longDescription":"Coalesce, schedule, and stream cargo so concurrent agent sessions share compiles instead of fighting locks.","shortDescription":"Coalesce, schedule, and stream cargo so concurrent agent sessions share compiles instead of fighting locks."},"mcpServers":"./.codex-plugin/mcp.json","name":"cargo-hauler","skills":"./skills/","version":"0.6.8"}
+{"author":{"name":"cargo-hauler"},"description":"Coalesce, schedule, and stream cargo so concurrent agent sessions share compiles instead of fighting locks.","hooks":"./.codex-plugin/hooks.json","interface":{"capabilities":["mcp","hooks","skills"],"category":"Productivity","defaultPrompt":["Help me use cargo-hauler."],"developerName":"cargo-hauler","displayName":"cargo-hauler","longDescription":"Coalesce, schedule, and stream cargo so concurrent agent sessions share compiles instead of fighting locks.","shortDescription":"Coalesce, schedule, and stream cargo so concurrent agent sessions share compiles instead of fighting locks."},"mcpServers":"./.codex-plugin/mcp.json","name":"cargo-hauler","skills":"./skills/","version":"0.6.9"}

package/artifact/.cursor-plugin/plugin.json

@@ -1 +1 @@
-{"description":"Coalesce, schedule, and stream cargo so concurrent agent sessions share compiles instead of fighting locks.","displayName":"cargo-hauler","hooks":"./.cursor-plugin/hooks.json","mcpServers":"./.cursor-plugin/mcp.json","name":"cargo-hauler","skills":"./skills/","version":"0.6.8"}
+{"description":"Coalesce, schedule, and stream cargo so concurrent agent sessions share compiles instead of fighting locks.","displayName":"cargo-hauler","hooks":"./.cursor-plugin/hooks.json","mcpServers":"./.cursor-plugin/mcp.json","name":"cargo-hauler","skills":"./skills/","version":"0.6.9"}

package/artifact/INSTALL.md

@@ -2,7 +2,7 @@
 
 Coalesce, schedule, and stream cargo so concurrent agent sessions share compiles instead of fighting locks.
 
-Version: `0.6.8`
+Version: `0.6.9`
 
 Run these commands from this bundle directory. The bundle is self-contained: every command below is
 a host command or the bundled installer, and nothing requires the `agent-bundle` CLI. Where that CLI is