Repository navigation
Rename the brand name to Cosyte, capital C, in prose - #117
Merged
Merged
Conversation
Founder decision, in the founder's own words: "Uppercased C on Cosyte
everywhere. Fix any location that has it as lowercase."
Renamed as ordinary prose across root docs (README.md, CHANGELOG.md,
RELEASING.md, drift-manifest.json, drift-manifest.schema.json,
documentation/, .github/credential-surface.json, the no-emdash
workflow), every published package's README.md and CHANGELOG.md,
scripts/check-no-emdash.sh (comments and messages, same pattern as the
other repos' copies), scripts/changeset-guard.mjs and
scripts/release-notes.mjs (em-dash-gate messages), and
scripts/parser-template/'s own CHANGELOG, changeset README and
src/index.ts comment.
The "`@cosyte/X` is on the cosyte 0.1.x line / 0.0.x ladder: the public
API is..." sentence that scripts/readme-check.mjs's statusSentence()
requires every package README to open its Status section with is
renamed at its one source (readme-check.mjs) and in every README and
test fixture that states or exercises it (test/configs.test.ts,
test/readme-check.test.ts, test/release-0-1-0-plan.test.ts), kept
consistent because all of them moved together in this same change.
Left lowercase: the four `import cosyte from "@cosyte/eslint-config"` /
`"@cosyte/prettier-config"` code examples (packages/eslint-config/README.md,
packages/prettier-config/README.md, scripts/parser-template/eslint.config.js,
and the code span in root README.md's package table). The first is
inside a ` ```ts runnable ` fence that test/doc-snippets.test.ts
actually executes; renaming the binding there breaks the snippet
(`cosyte` becomes a ReferenceError). All four are a JS binding the same
way pathways' eslint.config.js's is: a default import, which the
conductor's pattern does not cover in its documented JS-binding
exclusions (only `{ `, `const ` and `let `). Left as the real
identifiers they are and reported to the conductor; renamed the one
piece of surrounding prose on the root README.md table row ("cosyte
rules" -> "Cosyte rules") without touching the code span beside it.
Verified locally: `pnpm run format:check`, `pnpm run typecheck` (8
packages), `pnpm run lint` (8 packages), and `pnpm run check:no-emdash`
all pass on this branch. `pnpm run test` (1045 tests) has the same 13
pre-existing failures a clean checkout of main has, confirmed by
running it there first: 11 are `install-hardening.test.ts` /
`npm-config-allow.test.ts` cases that require the exact pinned
pnpm@10.34.5 CLI behavior, which this sandbox's pnpm@12.5.1 does not
reproduce; none touch anything this change renamed.
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.
Founder decision, in the founder's own words: "Uppercased C on Cosyte
everywhere. Fix any location that has it as lowercase."
Renamed
Ordinary prose across root docs (
README.md,CHANGELOG.md,RELEASING.md,drift-manifest.json,drift-manifest.schema.json,documentation/,.github/credential-surface.json, the no-emdashworkflow), every published package's
README.mdandCHANGELOG.md,scripts/check-no-emdash.sh(comments and messages, same pattern as theother repos' copies),
scripts/changeset-guard.mjsandscripts/release-notes.mjs(em-dash-gate messages), andscripts/parser-template/'s own CHANGELOG, changeset README andsrc/index.tscomment.The
`@cosyte/X` is on the cosyte 0.1.x line / 0.0.x ladder: the public API is...sentence thatscripts/readme-check.mjs'sstatusSentence()requires every package README to open its Status section with is renamed
at its one source (
readme-check.mjs) and in every README and testfixture that states or exercises it (
test/configs.test.ts,test/readme-check.test.ts,test/release-0-1-0-plan.test.ts), keptconsistent because all of them moved together in this same change.
Left lowercase
The four
import cosyte from "@cosyte/eslint-config"/"@cosyte/prettier-config"code examples (packages/eslint-config/README.md,packages/prettier-config/README.md,scripts/parser-template/eslint.config.js,and the code span in root
README.md's package table). The first isinside a
```ts runnablefence thattest/doc-snippets.test.tsactually executes; renaming the binding there breaks the snippet
(
cosytebecomes aReferenceError). All four are a JS binding the sameway pathways'
eslint.config.js's is: a default import, which theconductor's pattern does not cover in its documented JS-binding
exclusions (only
{,constandlet). Left as the real identifiersthey are and reported to the conductor; renamed the one piece of
surrounding prose on the root
README.mdtable row ("cosyte rules" ->"Cosyte rules") without touching the code span beside it.
Verified locally
pnpm run format:check,pnpm run typecheck(8 packages),pnpm run lint(8 packages), andpnpm run check:no-emdashall pass on thisbranch.
pnpm run test(1045 tests) has the same 13 pre-existingfailures a clean checkout of main has, confirmed by running it there
first: 11 are
install-hardening.test.ts/npm-config-allow.test.tscases that require the exact pinned pnpm@10.34.5 CLI behavior, which
this sandbox's pnpm@12.5.1 does not reproduce; none touch anything this
change renamed.
Name search
4 lines remain on this branch: the four code-identifier lines above.
https://claude.ai/code/session_011dC8vE9axM3hqC8rNEX3W9