docs(remote-agents): presence staleness bound is 180s since #3783 - #4310
Open
webdevtodayjason wants to merge 1 commit into
Open
docs(remote-agents): presence staleness bound is 180s since #3783#4310webdevtodayjason wants to merge 1 commit into
webdevtodayjason wants to merge 1 commit into
Conversation
VISION_REMOTE_AGENTS.md and the remote-agents spec both state the dead-agent presence window as 90 seconds. PRESENCE_TTL_SECS was raised 90 -> 180 by block#3783 (merged 2026-07-30), shortly before both documents landed, so the promised bound is half the real one. Update the vision's prose and the spec's I3 references (206, 216, 928) to the 180-second / three-minute figure. The presence.rs:16 line reference is still accurate; only the value changed. Signed-off-by: webdevtodayjason <jason@webdevtoday.com>
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.
Problem
VISION_REMOTE_AGENTS.md and the remote-agents spec both promise a dead remote agent's presence dot can be wrong "by at most about ninety" seconds. That was true against the old presence lease (90s
PRESENCE_TTL_SECSrenewed on a 30s/60s beat), but #3783 (merged 2026-07-30) raised the lease to 180s with all publishers on a 60s beat. Both documents landed after that change (#3924 on 07-30, #3748 on 08-02), so the stated staleness bound is half the real one.The margin history is on #3795: the old 90s lease gave the agent harness a 1.5x margin (production capture in #3795 (comment)), #3783 restored 3x by doubling the TTL, and the doubled TTL is what these documents should state.
Fix
Five lines, docs only:
VISION_REMOTE_AGENTS.md"Honest Costs": ninety seconds becomes about three minutes.docs/remote-agents.mdI3: the 90 seconds bound becomes 180 seconds, the quoted vision phrase follows, and the two downstream restatements ("wrong for <=90s", "the 90s presence bound") match.The
presence.rs:16line reference in the spec is still accurate; only the constant's value changed. I checked both files for any other statement derived from the old 90/30 pair and found none.Validation
PRESENCE_TTL_SECS = 180atcrates/buzz-pubsub/src/presence.rs:16on current main.crates/buzz-acp/src/lib.rs:1583, desktop 60s atdesktop/src/features/presence/lib/presence.ts:42, so 180s = 3x the slowest publisher, and the worst-case wrong-dot window after an unceremonious kill is the full 180s lease.