feat(retrieval): add RAG eval improvement loop#47
Merged
Conversation
tangletools
approved these changes
Jul 7, 2026
tangletools
left a comment
Contributor
There was a problem hiding this comment.
✅ Auto-approved drewstone PR — 3b3c4a9c
This PR was opened by the trusted drewstone account.
The full PR reviewer audit still runs separately and will publish findings if it detects issues.
tangletools · auto-approval · reason: drewstone_author · 2026-07-07T20:05:50Z
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.
What changed
runRetrievalImprovementLoop()for one-call RAG/retrieval config optimization on top ofagent-eval.agent-knowledgeas a knowledge-base construction and retrieval/RAG eval package.Validation
pnpm exec tsc --noEmitpnpm exec vitest run tests/retrieval-eval.test.tspnpm exec tsupgit merge-tree --write-tree origin/main HEADNotes
This PR was cut from a clean worktree based on
origin/mainbecause the original working branch had unrelated staged memory-holdout work and a pre-existing merge conflict against main.