2026-06-09
The campaign persistence engine was project-scoped, so its keep-going heartbeat fired in every session sharing the repo — including one that wasn't driving the campaign. Obeying it would have meant two orchestrators colliding on the same live state.
The state is clear now: This session (07769f2a) is NOT the campaign driver — 7f4afbfd is. The campaign control-panel-app is at phase V / stage S4, actively driven by 7f4afbfd. The Stop-engine is project-scoped, so its heartbeat fired in my session too. I should not drive the campaign here — that would collide with 7f4afbfd (exactly the cross-session problem we've been fixing). I'll let 7f4afbfd keep driving.
When the heartbeat kept looping, the model re-read the lock and held the line — hands off the campaign, no lock changes, nothing paused or disarmed — and delegated a session-pin fix to an isolated worktree so the design flaw got fixed without touching the live run.
Claude, receiving another session's campaign heartbeat in the Composure plugin repo. Reproduced verbatim.
You can stop reading and start checking.
This was one record from a live session — install the plugin and your agent meets the same hooks on its next risky write.