ref shape as schema + pointed rejections - #16
Merged
Conversation
…errors Live observation (first night of the R4 gate): the ear twice passed timestamp- and channel-shaped strings as refs before self-correcting to the [rN] tag — one wasted call per pass. The ref fields on reply/react/ step_back/verdict now carry pattern ^r\d+$ in their schemas (models read schemas), descriptions lead with the anti-examples (never a timestamp, channel id, or thread id — labels, not addresses), and the rejection quotes the bad value back with the shape to copy. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
1 participant
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.
Live-fire tuning from the first night: pattern-constrain ref fields, lead descriptions with anti-examples, quote bad values back in rejections.
🤖 Generated with Claude Code