-
Notifications
You must be signed in to change notification settings - Fork 1
feat: output policy v2 — review-policy rewrite #77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
8f3ed4c
feat: add output_policy.py — narration suppression, confidence gate, …
Fieldnote-Echo dd4ed44
feat: add summary_only_findings and output policy telemetry to schema
Fieldnote-Echo cebd31a
feat: wire output policy into retry.py, review.py, mcp_server.py
Fieldnote-Echo 15bb90c
feat: snippet rendering, summary-only section, policy-bypassed warning
Fieldnote-Echo bf425ca
test: output policy test suite (34 tests) + regression fixes
Fieldnote-Echo 338f653
test: coverage for output policy rendering in github_review.py
Fieldnote-Echo 6f51356
style: add # nogrip to test fixture SQL patterns
Fieldnote-Echo 86cf613
fix: nogrip suppression in output policy + resolve stale threads
Fieldnote-Echo 049f3ba
fix: output policy closure — evidence grounding, split telemetry, ide…
Fieldnote-Echo e4c936d
fix: thread resolution uses stdin for JSON arrays + nogrip on test ev…
Fieldnote-Echo File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🟡 MEDIUM: Malformed summary-only findings rendering code style
Confidence: 90%
The rendering logic for 'summary_only_findings' in the summary comment diverges from the format used for normal findings and omits key fields (e.g. confidence or grippy_note). This may cause confusion/inconsistency for consumers or break downstream automation expecting uniform markdown structure.
Suggestion: Make the rendering structure for summary-only findings match the normal finding comment (including confidence % and grippy_note). Consider extracting a shared formatting helper.
— Consistency in report formatting helps prevent confusion and bugs.