Preserve inbox analysis across coding handoffs - #755
Merged
Merged
Conversation
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.
Inbox reviews could identify concrete implementation work, but the next coding run received only the original request: the agent-authored analysis was filtered out of task comments. New and resumed follow-ups now carry that analysis with its source message, agent and organisation, separately from delegator instructions. Coalescing preserves each source and retries retain one handoff.
Validation: 38 targeted inbox, canonical replay and operator-access tests passed, including creation/resume, coalescing and recovery after delivery interruption. Test dispatch storage is now explicitly isolated. No controller activation or web deployment is included; the wider Manager receipt/cursor implementation remains separate.