Repository navigation
Reject cyclic reply headers before walking email thread ancestry - #1049
Merged
msitarzewski merged 1 commit intoOct 6, 2026
Merged
msitarzewski merged 1 commit into
msitarzewski merged 1 commit into
Conversation
Signed-off-by: Rudy Celekli <47457359+rudycelekli@users.noreply.github.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.
Agent Information
Agent file:
engineering/engineering-email-intelligence-engineer.mdMotivation
Two messages replying to each other or a self-reply produce cyclic parent graphs; parent-body walkers can loop forever.
Testing
git diff --checkpass.scripts/test-convert-outputs.sh --drift=advisorypasses all 32 checks over 282 agents and 15 tool formats. Expected content drift is advisory; the generated-output manifest is left to maintainers.Native extracted example with controlled local inputs; no production system or model-effectiveness claim. No paid API call, real invoice, production data or actual model-effectiveness evaluation was performed.
Candidate listed before publication in #917: #917 (comment). This single-profile correction adds no tooling or generated outputs. AI assistance was used to investigate, implement and test it; the commit is signed and includes DCO sign-off.