fix: remove duplicate confidence/status from low-confidence escalation reason#12
Merged
Merged
Conversation
…n reason status and confidence appeared twice in the escalation reason: once in the inline bullet list and again inside predictedPromptSection. Removed the inline bullets; predictedPromptSection already has both. Also update test assertion to match new Confidence: 0.NNNNN format. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.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
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.
Summary
- status:,- confidence:,- threshold:) from the low-confidence escalation message — that information is already present inpredictedPromptSection, causing it to appear twiceConfidence: 0.NNNNN)Before
After