Preserve human mentions without waking a Runtime - #948
Draft
Y1fe1Zh0u wants to merge 1 commit into
Draft
Conversation
Native group replies already persist human mentions without dispatching work, but the Runtime at preflight rejected every non-Agent participant. Split public mention validation from Agent handoff validation so mixed human and Agent targets remain atomic while child Runs are created only for wakeable Agents. Constraint: Human mentions must remain visible without creating child Runs. Rejected: Strip human IDs during model repair | loses structured mention metadata and contradicts group message behavior. Confidence: high Scope-risk: narrow Directive: Keep public mention targets distinct from wakeable Agent targets. Tested: 232 scoped Runtime and group delivery tests; Ruff check on changed files. Not-tested: Browser rendering and live 3010 mixed-mention E2E pending deployment.
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 changed
Why
The group handoff preflight treated every mentioned participant as a Runtime target. A valid human mention therefore caused the entire mixed mention set to be rejected, even though native group replies already persist human mentions without dispatching work.
Impact
Human mentions remain visible in the final group message without waking a Runtime. Agent mentions continue to create child Runs, including when both participant types appear in the same response.
Validation
Remaining validation
CI baseline dependency
Drone #490 reaches the fresh database migration step and then fails on the existing
f061_enterprise_info_tenant_idduplicate-column defect inmain. This PR does not touch migrations. PR #945 contains the independent idempotence repair and passed the same fresh PostgreSQL lane in Drone #489; once that repair reachesmain, this branch must be refreshed and CI rerun.