Repository navigation
Fix robust evidence matching and extraction recovery - #4
Merged
Merged
Conversation
FFFFFFpy
marked this pull request as ready for review
July 10, 2026 19:15
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.
Summary
This is the second-pass fix driven by the supplied debug bundle. The previous quote-based evidence design exposed three new failure modes: typography-only quote differences were rejected, YAML/H1 title duplication was treated as ambiguous, and malformed stage responses such as
{}were counted as successful empty output.Changes
Evidence resolution
Stage response contract and retry
summary,concepts,entities, orrelationsat the top level with the expected value type{}, misspelled keys, null values, and wrong container types as malformed responses0/0 okattempt-2/Concept/entity separation
Relations
subject_id/object_idwhile retaining legacy name-based relation output compatibilityValidation
{}relation response triggers exactly one corrective retryVersion bumped to
0.2.1.