cargo-hauler 0.7.0 → 0.7.1

package/CHANGELOG.md

@@ -1,5 +1,11 @@
 # Changelog
 
+## 0.7.1
+
+### Patch Changes
+
+- 9a50169: Fail closed with exit 69 when a reattached `hauler exec` cannot restore the complete Cargo output stream, and serialize overlapping reattach claims so a stale connection cannot replace the latest ticket owner (#187).
+
 ## 0.7.0
 
 ### Minor Changes

package/README.md

@@ -403,11 +403,12 @@ killed as `killed while queued: submitter disconnected and did not reattach
 within 30s` only if nobody comes back; one already running continues, marked
 orphaned as before. A reattach rebinds the ticket to the new connection,
 clears the orphan flag, replays the output the client had not yet received
-from the replay buffer, and streams the rest, so the exit code is cargo's as
-if nothing had happened; output the buffer no longer holds is announced as
-`N bytes of output missed while reconnecting; full log: <path>` rather than
-invented. A ticket that finished in the meantime yields its exit code and log
-path. When the ticket cannot be reattached — it never ran cargo and was
+from the replay buffer, and streams the rest, so the exit code is cargo's only
+when the complete stdout/stderr stream was restored. If the replay buffer no
+longer holds every missed byte, or the ticket finished before its output
+stream could be rebound, the client names the full log and fails closed rather
+than return success with truncated machine-readable output. When the ticket
+cannot be reattached — its output is incomplete, it never ran cargo and was
 killed at the daemon's shutdown, `orphaned by daemon restart`, unknown to the
 daemon that answered, the daemon predates the message, or no daemon answered
 within the budget — the client exits `69` (`EX_UNAVAILABLE`) with `brokered

package/dist/.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.7.0"}]}
+{"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.7.1"}]}

package/dist/.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.7.0"}
+{"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.7.1"}

package/dist/.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.7.0"}
+{"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.7.1"}

package/dist/.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.7.0"}
+{"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.7.1"}

package/dist/INSTALL.md

@@ -2,7 +2,7 @@
 
 Coalesce, schedule, and stream cargo so concurrent agent sessions share compiles instead of fighting locks.
 
-Version: `0.7.0`
+Version: `0.7.1`
 
 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

package/dist/README.md

@@ -403,11 +403,12 @@ killed as `killed while queued: submitter disconnected and did not reattach
 within 30s` only if nobody comes back; one already running continues, marked
 orphaned as before. A reattach rebinds the ticket to the new connection,
 clears the orphan flag, replays the output the client had not yet received
-from the replay buffer, and streams the rest, so the exit code is cargo's as
-if nothing had happened; output the buffer no longer holds is announced as
-`N bytes of output missed while reconnecting; full log: <path>` rather than
-invented. A ticket that finished in the meantime yields its exit code and log
-path. When the ticket cannot be reattached — it never ran cargo and was
+from the replay buffer, and streams the rest, so the exit code is cargo's only
+when the complete stdout/stderr stream was restored. If the replay buffer no
+longer holds every missed byte, or the ticket finished before its output
+stream could be rebound, the client names the full log and fails closed rather
+than return success with truncated machine-readable output. When the ticket
+cannot be reattached — its output is incomplete, it never ran cargo and was
 killed at the daemon's shutdown, `orphaned by daemon restart`, unknown to the
 daemon that answered, the daemon predates the message, or no daemon answered
 within the budget — the client exits `69` (`EX_UNAVAILABLE`) with `brokered