FU-P13-T7: Enforce strict structuredContent compliance for empty-content tool results#61
Merged
SoundBlaster merged 7 commits intomainfrom Feb 16, 2026
Conversation
…tent_tool_results
…d troubleshooting docs
…ntent_tool_results (PASS)
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.
Description
Adds targeted regression tests and troubleshooting documentation for the strict
structuredContentcompliance requirement on empty-contenttools/callresponses (FU-P13-T7).The core injection logic (
structuredContent: {}forresult.content: []) was already implemented intransform.py(P4-T1/BUG-T5). This PR adds:TestEmptyContentStrictCompliancecovering theisError=true + content:[]path, notification passthrough, and already-compliant response preservationstructuredContentschema violationType of Change
Quality Gates
make test- All tests pass with ≥90% coverage (471 passed, 5 skipped; 95.6% coverage)make lint- No linting errors (ruff check src/clean)make format- Code is properly formattedmake typecheck- Type checking passesmake doccheck- Documentation is synced with DocC (if docs changed) — DocC catalog not present; N/ADocumentation Sync
docs/troubleshooting.mdmcpbridge-wrapper.docc/Troubleshooting.mdTesting
TestEmptyContentStrictCompliance)Checklist