docs(spec): correct six claims about behaviour the code does not have - #4
Merged
Merged
Conversation
SPEC.md is the normative document, so a claim in it that the implementations do not honour is worse than the same claim anywhere else. An adversarial audit read every clause against the three codebases and six did not hold. The examples README's two-terminal recipe did not run as written, which matters more than it looks: that recipe is how a stranger checks their own client, so a broken one turns the conformance story into a claim again. Corrections are recorded in the document rather than applied silently, which is this specification's convention for anything it previously got wrong. Co-Authored-By: Claude Opus 5 (1M context) <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.
SPEC.md is the normative document, so a clause the implementations do not honour is worse there than anywhere else. An adversarial audit read every clause against the three codebases; six did not hold.
The
examples/README.mdtwo-terminal recipe also did not run as written. That matters more than it looks: the recipe is how a stranger grades their own client, so a broken one turns the conformance story back into a claim.Corrections are recorded in the document rather than applied silently, which is this specification's convention for anything it previously got wrong.
🤖 Generated with Claude Code