mirror of
https://github.com/block/buzz.git
synced 2026-08-18 06:50:31 +02:00
npub17jjz49l9jjmhhk7cac63j8yt9z555n9cw8vk7v5jz4vzw4ppld5qgj57ccandTyler
5a2d8a2701
Every file:line citation in docs/remote-agents.md was labeled against `c1bca1b56` or `b4f4ed1a6`, neither of which is an ancestor of main (merge-base with28ae6cd21isaf4b7087d). Readers could not resolve them. Rather than assume offsets, each cited line's content was extracted at the old pin and located in the merged tree. 44 of 49 already resolved byte-exactly at28ae6cd21— they had been verified against the PR base, not the labeled pin, so the caveat paragraph had the accuracy backwards. Three drifted as pure offsets, corrected here: discovery.rs:74-193 -> 75-207 KNOWN_ACP_RUNTIMES; all four cited metadata fields occur only in this range runtime.rs:1006 -> 1001 spawn_agent_child(.., false, ..); the eager/lazy contrast with restore.rs:333 (true) still holds types.rs:809 -> 814 DEFAULT_AGENT_PARALLELISM, still 10, so the ~87s / ~197s arithmetic is unchanged One drift was not an offset but a factual error. PRESENCE_TTL_SECS is 180, not 90:bf139e8d0(#3783, Jul 30 15:26) raised it to preserve a three-heartbeat window after the desktop heartbeat moved to 60s, landing after this spec's base (Jul 30 12:30) but before it merged. The spec merged onto a main that had already invalidated the number. Pinned by test at presence.rs:114-115. 90s was load-bearing in three places, all understating the real bound by 2x (I3 at :206, the BUZZ_ACP_NO_PRESENCE argument at :216, the same argument for I5 at :928), and the spec quotes the vision's "ninety seconds" prose inline. Corrected in both documents. I3's promise is that the staleness window is bounded, never indefinite; the width was inherited from a relay-wide constant that moved for unrelated perf reasons, and the binding's grace period targets the avoidable half either way. Each Known Defect claim was re-verified live at28ae6cd21rather than relabeled — a re-pin carrying a stale assertion forward is worse than the offset it fixes. All eight still hold: KD1 bare strip_prefix at backend.rs:467, KD3 deploy_payload_json emits 15 flat fields with no launch block, KD4 BUZZ_ACP_EXIT_AFTER_INACTIVITY has zero occurrences, KD5 provider_deploy invokes deploy with no preceding info, KD8's empty-string arm in coerceConfigValues. Docs-only. No behavior change. Co-authored-by: Tyler <109685178+tlongwell-block@users.noreply.github.com> Signed-off-by: Tyler <109685178+tlongwell-block@users.noreply.github.com>