fix(clawde): stop the steward's own probe manufacturing heartbeat edges - #23
Merged
Conversation
The change gate fires when the probe's fingerprint differs from the last one it fired on, so every field in that fingerprint is a wake reason. The steward's probe folded in three the steward never acts on: the shared checkout's dirty flag, which flips as peers work their worktrees; both revision shas, which move on every push by anyone; and the raw continuous integration state, which cycles through its pending values on every run. Ordinary fleet traffic therefore manufactured an edge almost every tick and the edge trigger degraded into the level trigger it replaced. kira's steward woke 73 times on 27 August, four an hour, for a repository whose actionable state had barely moved. Print the decision rather than the state it was read from: commits ahead and behind instead of the shas, and a failing-or-not boolean instead of the run's phase, reusing the same predicate steward-status already derives. A red run still wakes the steward; a queued one no longer does. Agent-Machine: kira Agent-Resume: claude --resume efee1316-8d94-438e-951e-e9c978626531
Uh oh!
There was an error while loading. Please reload this page.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
kira's steward woke 73 times on 27 August, four an hour, on a repository whose actionable state had barely moved.
The change gate is edge-triggered: it fires when the probe's fingerprint differs from the last fired one. So every field in that fingerprint is a wake reason. Three of them were things the steward never acts on:
dirtyhead/upstreamcontinuous_integration_statenone->pending->passingon every runOrdinary fleet traffic manufactured an edge nearly every tick, so the edge trigger degraded into the level trigger it was built to replace.
Fix: print the decision, not the state it was read from.
ahead/behindalready carry what the shas meant, andcontinuous_integration_failingreuses the predicatesteward-statusderives itself. A red run still wakes the steward; a queued one no longer does.Tests: the three new contract cases fail against the old probe and pass with the fix.