From 14508ca05928618d5039c2217987b5f7e81262e8 Mon Sep 17 00:00:00 2001 From: mintaka Date: Sat, 29 Aug 2026 15:28:52 -0400 Subject: [PATCH] docs(ui): refresh GetRoster field-name commentary for the handle flip (RIG-2882) RIG-2880 (#698) flipped the request-side comms fields from account-ids to `@handle` inputs, renaming `GetRosterRequest.agent_account_id` -> `vantage_handle`. The `fetchSnapshot` comment still named the old `agent_account_id` field twice while describing the current wire contract; retarget it at `vantage_handle`. Code was already correct (the call site sends only `{ scope }`, leaving the handle field empty). This is the T7 stale-commentary item from the frozen handle-addressing cutover record. Sweep-confirm + suite-run (1029/0 against the regenerated client) recorded on RIG-2882. Co-authored-by: Matt Wilkinson --- apps/ui/src/live/stream.ts | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/apps/ui/src/live/stream.ts b/apps/ui/src/live/stream.ts index 6e00b8fe..e753b6a2 100644 --- a/apps/ui/src/live/stream.ts +++ b/apps/ui/src/live/stream.ts @@ -95,9 +95,9 @@ export async function fetchSnapshot( ): Promise { const opts = { signal }; // GetRoster joins the SAME failure domain as the other snapshot reads — NOT - // best-effort. It carries no agent_account_id: the server defaults the - // vantage to the caller and resolves a user caller to its own owned set (R6). - // GetRosterRequest carries only scope + agent_account_id (no snapshotSeq), so + // best-effort. It carries no vantage_handle: the server defaults the vantage + // to the caller and resolves a user caller to its own owned set (R6). + // GetRosterRequest carries only scope + vantage_handle (no snapshotSeq), so // the presence seed is unversioned and converges via the seq'd tail replay. // A rejection propagates (throws) exactly like the sibling reads, is caught // in runCommsStream, and retries the whole snapshot with backoff — never a