Add channel-owned agent response policy - #3552
Draft
mgalpert wants to merge 1 commit into
Draft
Conversation
Signed-off-by: Michael Galpert <mgalpert@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
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.
Summary
mentions/allagent-response policy to channel metadata and persistenceWhy
Agent response behavior was runtime-local, so channel owners could not opt selected channels into untagged agent replies without broad per-agent overrides. This makes the channel policy authoritative for every agent member and keeps existing channels mention-only by default.
Impact
mentionsallto deliver untagged channel messages to agent membersValidation
cargo test -p buzz-sdk update_channelcargo test -p buzz-acp agent_responsecargo test -p buzz-db migration::tests::embedded_migrator_contains_consolidated_initial_schemajust cireaches the mobile test stage but is currently blocked by an unrelated existing assertion inmobile/test/features/channels/channel_detail_page_test.dart(keeps follow mode off while a tall newest message stays visible). This branch does not modify mobile files; the failure reproduces when that test is run alone.