fix: bounded status stickiness — no frozen statuses (0.16.3)#87
Merged
Conversation
…oard (0.16.3)
"How come no status was sent?" A status WAS on the bus — but frozen:
an explicit declaration ("shipping 0.16.1") stayed put while the work
moved on, because 0.16.1 made explicit statuses sticky FOREVER and
nothing refreshed it. Sticky-forever turns a nice declaration into a
stale lie.
Now stickiness is time-bounded (statusAt timestamp,
AGENTCOMM_EXPLICIT_STICKY_MS, default 15min): an explicit status wins
over the task list while fresh, then a newer task refreshes it — so the
board can't freeze on old work. Re-declaring resets the window. Best of
all three: rich narrative when you set one, terse-but-current task
subject when you don't touch it, never a frozen stale status.
Test: fresh explicit blocks a task; backdated explicit yields to a
task; a re-declaration wins immediately.
Co-Authored-By: Claude Fable 5 <[email protected]>
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 free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
0.16.1 made explicit statuses sticky forever, so a declaration froze the board on old work ('how come no status was sent?' — it was, but stale). Now sticky is time-bounded (15min, env-tunable): explicit wins while fresh, a newer task refreshes it after, re-declaring resets. Tested at the Bus level.