jerry/buzz
1
0
Fork 0
mirror of https://github.com/block/buzz.git synced 2026-10-27 12:40:30 +00:00
Code Issues Packages Projects Releases Wiki Activity
Files
01958a73b96ca34c175fd4e1d151954af9f1ce0a
buzz/docs/agent-management-provenance.md
Logan Johnson 5073e075d7 fix(desktop): unify owned-agent cloud provenance markers (#7129) 
Unify presentation-only cloud provenance across agent identity surfaces. Keep successful local-inventory and verified-ownership gates; preserve main availability and mention spacing behavior.

Co-authored-by: Larry <627498bd4bd1f281a16431e3c6cce3b5c25b6692798c78672298aefbf2f8f8b5@buzz.block.builderlab.xyz>
Signed-off-by: Logan Johnson <loganj@squareup.com>
2026-09-03 02:35:37 +00:00

1.9 KiB
Raw Blame History

Agent management provenance

The shared Not managed on this device cloud marker means a viewer-owned identity has no exact-key record in successfully loaded local managed inventory. The glyph is the approved visual convention, not proof of physical cloud hosting. Locally managed provider-backed agents, unknown/failed local inventory, unknown owners, and other people's identities do not get the marker. Neither lifecycle state nor relay presence decides management provenance.

KnownAgentPubkeysProvider supplies stable inventory and ownership context to identity surfaces; rows must not create their own directory query observers. Picker candidates preserve exact local-management flags and use the same pure predicate. Profile ownership can supplement the shared directory evidence.

Pickers, member cards, authors, markdown mention chips, address controls, hover cards, profile headers/hero/subviews, new-message recipients and DM headers/sidebar rows use the same glyph and accessible label. The marker grants no membership, mention eligibility, availability or local management capability. This change does not change profile navigation, presence, native discovery or invitation/routing.

Regression gates: otherSetupAgent.test.mjs, useKnownAgentPubkeys.test.mjs, buildMentionCandidates.test.mjs, MentionAutocomplete.test.mjs, and tests/e2e/cloud-provenance.spec.ts. Browser evidence is mock-Tauri rendered UI, using an already eligible channel member and an existing DM, not a discovery or invitation acceptance test. mentions.spec.ts retains its marker-label assertions. The cloud smoke waits (at most 10 seconds, with per-query status diagnostics) for successful identity, local inventory and relay directory reads before opening the picker. Both immediate and delayed-directory fixtures exercise the same rendered workflow. Each cloud assertion retains its own normal deadline: successful data loading must not hide a missing glyph or accessible marker.