Repository navigation
Record a geoword buzz when check-answer gives a final verdict - #626
Merged
Merged
Conversation
The server now saves the buzz itself on an accept or reject, with isCorrect from its own verdict, instead of trusting a separate record-buzz request. A prompt records nothing; the earlier prompts are sent with the final answer. The /record-buzz route is removed. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
geoffrey-wu
added this pull request to stack #627
October 21, 2026 04:15
geoffrey-wu
marked this pull request as ready for review
October 21, 2026 04: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.
Stacked on #625: the base is its branch, so the diff shows only this change. Retarget to
mainonce #625 merges.check-answernow saves the buzz itself on anacceptorreject, withisCorrecttaken from the server's verdict, instead of trusting a separate/record-buzzrequest from the client. Apromptverdict records nothing; the client sends its earlier prompts and the celerity along with each check, and the buzz is written once, with the final answer. The response gains asavedflag, and Next enables only when it is true. The/record-buzzroute is removed.Still client-supplied: celerity and the prompts list. Once play logging is in, the prompts could be read back from
play-logsinstead.🤖 Generated with Claude Code