Fix/prompt updates#2
Merged
Merged
Conversation
…ate prompts, and enhance test coverage.
…on, correctness, and feedback, and clarify `context`/`answer` fields
peterbjohnson
approved these changes
Jul 13, 2026
peterbjohnson
left a comment
Member
There was a problem hiding this comment.
Looks fine. I've commented on some minor things.
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.
Problem
The evaluation function made a single combined LLM call that packed moderation, correctness, and feedback into one prompt and one JSON schema. This meant:
sensible.
Solution
Split the single call into three sequential, single-purpose LLM calls (moderation → correctness → feedback), short-circuiting as soon as one fails, and gave every non-essential
param a reasonable default so a minimal {model, context}-less request still works. Renamed params for clarity and brought docs/tests in line with the new behaviour.
Changes
parse-failure handling (_request_json, _failure_result).
default_correctness_decision() that picks between DEFAULT_CORRECTNESS_DECISION_WITH_CONTEXT / ..._NO_CONTEXT depending on whether context was supplied (avoids a dangling "to the
following question:" when it's missing).
(folded into the fixed JSON-output instructions each call appends).
correctness/feedback prompts when omitted, the context-free correctness default, moderation short-circuiting, and per-step parse-failure handling.