fix(ui): relabel agent owner attribution from "owned by" to "managed by" - #2133
Merged
Merged
Conversation
"owned by" reads like a collar tag on something that talks back; "managed by" is accurate and neutral. Applies to all user-visible agent-owner copy: message header, mention autocomplete (desktop + mobile), members sidebar, new-message search rows, profile popover, and profile panel field label. Renames the internal label constant, the user-profile-owned-by testId, and updates the e2e assertions to match. Comments describing ownership semantics (not UI copy) are unchanged. Decided in buzz-launch: owner label copy review, 2026-07-19. Co-authored-by: Tyler Longwell <tlongwell@block.xyz> Signed-off-by: Tyler Longwell <tlongwell@block.xyz>
BradGroux
pushed a commit
to BradGroux/buzz
that referenced
this pull request
Aug 23, 2026
…by" (block#2133) Signed-off-by: Tyler Longwell <tlongwell@block.xyz> Co-authored-by: npub1qyvc0c5kl4gqv2fd97fsk46tu378sqgy35vc83rvgfwne90sel7s0ed67d <011987e296fd5006292d2f930b574be47c7801048d1983c46c425d3c95f0cffd@sprout-oss.stage.blox.sqprod.co> Co-authored-by: Tyler Longwell <tlongwell@block.xyz>
tucktuck101
pushed a commit
to tucktuck101/buzz
that referenced
this pull request
Sep 17, 2026
…lock#2131) The phase table claimed Phase 1 was "Not started". It shipped on 2026-09-08 as PR block#2106, hardened by PR block#2133 on 2026-09-09. Both rows now state what is true and name the merged PRs. Phase 1b reads BUILT, NOT MERGED -- deliberately not "shipped". Every criterion in its own review gate has been demonstrated with transcripts under launchpad/plans/evidence/, but the branch has not been reviewed, gated or opened as a pull request, and the row says so rather than letting a demonstration read as a merge. The second-pass re-dispatch observable is specified and wired, but a full two-pass run over a finished page belongs to Phase 2, the first phase that produces one; that is stated rather than implied. Phases 2-7 still read "Not started", correctly. Five decisions recorded, under the honesty convention the rest of the document uses -- what was decided, why, and what it does NOT solve. Open questions items 1-9 all closed on 2026-09-04, so these are a new section rather than new items: 10. the re-dispatch observable, and its named independence limitation 11. the roster-names redact-plus-flag shape, and its accepted contract cost 12. column offsets as candidate identity, now demonstrated rather than argued 13. what a missing headless CLI demonstrates -- consequences, not absence 14. the verdict goes last in the response grammar, from measurement Section 6.7's mechanism row said stdout was "captured as the verdict". That is no longer precise: the whole response is matched against a two-line grammar by equality, and completion is judged separately from content, so a non-zero exit, a timeout or a truncated response each block whatever the text said. Verified after editing, per this document's own house rules: every local section cross-reference resolves to a real heading; the three references that do not (2b, 2d, 4a) are to verify-claims/SKILL.md and each names that file immediately before the reference; all three mermaid diagrams still present. Signed-off-by: Serina Mcfall <serina.mcfall@gmail.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.
What
Relabels agent owner attribution across all user-visible surfaces from "owned by" to "managed by", per copy review in buzz-launch (2026-07-19).
Where
MessageAgentOwner), mention autocomplete subtitles + titles, members sidebar add-member rows, new-message search result rows, profile popover owner line, profile panel "Managed by" field label (plus its ordering constant and testIduser-profile-owned-by->user-profile-managed-by; the testId had exactly one reference).suggestions.dart), plus comments that quote the label.mentions.spec.ts,messaging.spec.ts,pubkey-display-screenshots.spec.tsupdated to the new copy.Not touched: backend/relay "owned by" strings about channels, tokens, and repos (ownership semantics, not the agent label), and code comments describing ownership behavior.
Testing
At 58b0a2f:
tsc --noEmitclean (desktop).pnpm buildthen Playwright on the three touched specs: 87 passed, 1 failed — the failure (messaging.spec.ts"shows your avatar on your own message...") is untouched by this diff and passes solo; parallelism flake.dart format+flutter analyzeclean via pre-commit hooks (mobile).