docs: rename assert → assertions across all documentation#644
Merged
Conversation
Aligns documentation with the assert: → assertions: YAML key rename completed in PR #604. Updates prose references, YAML examples, table entries, SDK code samples, skill docs, and agent prompts across 17 files. Co-Authored-By: Claude Opus 4.6 <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.
Summary
assert:→assertions:YAML key rename from PR refactor: rename assert: to assertions: in EVAL.yaml schema (#603) #604assertfield →assertionsfield), YAML examples, table entries, code samples all updatedRisk
Low — documentation-only changes, no code behavior change. All pre-push hooks (build, typecheck, lint, test) pass.