Repository navigation
Write Cosyte with a capital C; bring the docs status blocks current for 0.1 - #144
Merged
Merged
Conversation
Five prose lines named the brand in lowercase: the README's archetype heading, its table-of-contents entry and paragraph, docs-content/intro.md and docs-content/spec-notes-tolerance.md. The README anchor #the-cosyte-parser-archetype is unchanged, since GitHub lowercases it. The operator, in their own words: "Uppercased C on Cosyte everywhere. Fix any location that has it as lowercase" The launch-ready name search now gives its cli-subcommand exclusion a word boundary, so prose such as "cosyte parser" no longer passes as the cli binary. Identifiers are unchanged: the @cosyte scope, cosyte/<repo> paths, heading anchors and URLs. Claude-Session: https://claude.ai/code/session_011dC8vE9axM3hqC8rNEX3W9
docs-content/intro.md, installation.md and troubleshooting.md still said the package was "pre-alpha on the Cosyte 0.0.x version ladder". It is on npm at 0.1.0 (npm view @cosyte/ccda version), and npm install @cosyte/ccda installs in a fresh directory. Each block now states 0.1 and the policy the README states: the exported names, options, return shapes and warning codes are the surface we keep stable, and below 1.0 a breaking change bumps the minor version and is called out in the changelog with its migration. Claude-Session: https://claude.ai/code/session_011dC8vE9axM3hqC8rNEX3W9
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.
Write Cosyte with a capital C in the parser archetype prose
Five prose lines named the brand in lowercase: the README's archetype heading, its table-of-contents entry and paragraph, docs-content/intro.md and docs-content/spec-notes-tolerance.md. The README anchor #the-cosyte-parser-archetype is unchanged, since GitHub lowercases it.
The operator, in their own words: "Uppercased C on Cosyte everywhere. Fix any location that has it as lowercase"
The launch-ready name search now gives its cli-subcommand exclusion a word
boundary, so prose such as "cosyte parser" no longer passes as the cli
binary. Identifiers are unchanged: the @cosyte scope, cosyte/ paths,
heading anchors and URLs.
Bring the docs status blocks current for 0.1
docs-content/intro.md, installation.md and troubleshooting.md still said
the package was "pre-alpha on the Cosyte 0.0.x version ladder". It is on
npm at 0.1.0 (npm view @cosyte/ccda version), and npm install @cosyte/ccda
installs in a fresh directory. Each block now states 0.1 and the policy the
README states: the exported names, options, return shapes and warning
codes are the surface we keep stable, and below 1.0 a breaking change bumps
the minor version and is called out in the changelog with its migration.
https://claude.ai/code/session_011dC8vE9axM3hqC8rNEX3W9