Skip to content

docs: drop \= OR operator from ai.txt, canonical is |#203

Merged
danieljohnmorris merged 1 commit into
mainfrom
fix/or-operator-spec
May 12, 2026
Merged

docs: drop \= OR operator from ai.txt, canonical is |#203
danieljohnmorris merged 1 commit into
mainfrom
fix/or-operator-spec

Conversation

@danieljohnmorris
Copy link
Copy Markdown
Collaborator

The agent-facing spec had two spellings for boolean OR (= and |) which leaked into agent-generated code as a coin flip.

Implementation:

  • doc-only change to ai.txt
  • canonical OR is |, which is what the lexer and parser accept
  • = was never supported by the implementation, the spec was wrong

No tests, no code, no example file - docs only.

@codecov
Copy link
Copy Markdown

codecov Bot commented May 12, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.

📢 Thoughts on this report? Let us know!

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.
@danieljohnmorris danieljohnmorris merged commit 5c9e611 into main May 12, 2026
5 checks passed
@danieljohnmorris danieljohnmorris deleted the fix/or-operator-spec branch May 12, 2026 21:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant