benchmarks: record repeated-investigation pre-fix failure - #31
Merged
Conversation
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.
Outcome
Records the completed repeated-investigation benchmark as a pre-fix baseline. The result is explicitly classified as a failure: GraphKeeper retrieved the stored grounded claims first, but the session still repeated substantial source and Git-history investigation.
The change is evidence-only under
benchmarks/results/repeated-investigation-pre-fix-2026-08-14/. It does not modify GraphKeeper implementation, schemas, templates, or application behavior.Evidence
Included in the result folder:
Focused verification performed before commit:
FAILresult and no-product-change statementFull build and test suites were not run because this PR adds documentation and captured benchmark data only.
Checklist
npm run buildpasses — not run; no implementation changes.npm run typecheckpasses — not run; no TypeScript changes.npm testpasses with no hidden skips — not run; evidence-only change.npm run package:smokepasses — not run; package contents are unchanged.Compatibility and recovery
No runtime, platform, diagnostic, schema, hook, or package behavior changes. Rollback is removal or revert of the single evidence commit; no manual recovery is required.