docs: drop \= OR operator from ai.txt, canonical is |#203
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
a0837a9 to
0dcf16c
Compare
The agent-facing spec had two spellings for boolean OR (\= and |) which leaked into agent-generated code as a coin flip. | is what the lexer and parser actually accept. \= is removed from ai.txt so prompts stop emitting the dead form. Behaviour-only doc change. No code path was supporting \= - the spec was wrong, not the implementation.
0dcf16c to
83187aa
Compare
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.
The agent-facing spec had two spellings for boolean OR (= and |) which leaked into agent-generated code as a coin flip.
Implementation:
No tests, no code, no example file - docs only.