v0.3.2

The failover now tells the next agent what happened

Two hours ago, someone on r/ClaudeCode pulled this repo, ran the test suite, and pointed out a failure mode we hadn't covered: continuation, not routing. When agent A hits its cap halfway through editing your repo and usher fails over to agent B, replaying the original prompt isn't a handoff — B has no idea A already changed things, and might duplicate or revert that partial work.

They were right. This release is their suggestion, almost verbatim.

• Continuation notice: when a failover agent takes over from one that actually ran, its prompt now opens with a warning — a previous agent was already working on this task; inspect git status and the diff before continuing. The original prompt follows, untouched.
• Envelope visibility: guarded attempts carry "continuation_guard": true in the --json attempts array. First attempts and pre-0.3.2 envelope shapes are byte-identical.
• Opt-out: continuation_guard = false in config.toml if your pipeline needs the prompt verbatim.
• An agent that fails to start never touched the workspace, so it doesn't trigger the notice.

Their four-step scenario is now an E2E test in tests/e2e_headless_test.go. The stronger version of their idea — a user-supplied handoff file — is open as #6 if you want to build it.

brew upgrade usher