docs: capitalize Cosyte in prose

.changeset/README.md

@@ -14,4 +14,4 @@ pnpm changeset
 ```
 
 During pre-alpha, pick **patch**: that keeps the package on the `0.0.x` ladder until its first
-alpha. See the cosyte version ladder in the meta-repo's `documentation/conventions.md`.
+alpha. See the Cosyte version ladder in the meta-repo's `documentation/conventions.md`.

CHANGELOG.md

@@ -1039,7 +1039,7 @@ section stubs that existed to receive the next hand-written entry. No entry was
 
 The entries below follow [Keep a Changelog](https://keepachangelog.com/en/1.1.0/); the generated
 sections above use the format Changesets writes, which is a version heading and a list of the
-changes that release consumed. Versions follow the cosyte pre-alpha ladder, `0.0.x` until first
+changes that release consumed. Versions follow the Cosyte pre-alpha ladder, `0.0.x` until first
 alpha, rather than [Semantic Versioning](https://semver.org/spec/v2.0.0.html) alone.
 
 ### Fixed
@@ -1599,7 +1599,7 @@ commit` refuses an unmerged path BEFORE it runs the pre-commit hook (the hook do
   carries the non-default `edited` pull-request activity type, so retitling a PR re-checks it, which
   matters because this repo allows only squash merge and takes its subject from the PR title
   (`squash_merge_commit_title: COMMIT_OR_PR_TITLE`). The body that lands is the branch commit
-  messages (`COMMIT_MESSAGES`), not the PR body; the PR body is scanned anyway, as a cosyte surface
+  messages (`COMMIT_MESSAGES`), not the PR body; the PR body is scanned anyway, as a Cosyte surface
   in its own right. Its own workflow rather than a job in `ci.yml`, so a PR-description typo does
   not re-run the Node 22 + 24 matrix. **It reports; it does not yet block.** The job is not a
   required status check: `cosyte/ccda` is governed by org-level rulesets whose required contexts are
@@ -1782,14 +1782,14 @@ commit` refuses an unmerged path BEFORE it runs the pre-commit hook (the hook do
   and the builder is through Phase 7 (`buildCcda` emits a CCD **or** Referral Note, `editCcda` edits a
   parsed document, and a bring-your-own terminology adapter validates coded values). The status banners
   in `intro.md` / `installation.md` and the "Scope (non-goals)" note in `troubleshooting.md` now state
-  published on npm at `0.0.1`, public, still pre-alpha on the cosyte `0.0.x` ladder; the install command
+  published on npm at `0.0.1`, public, still pre-alpha on the Cosyte `0.0.x` ladder; the install command
   is live; and `intro.md`'s builder capability now mirrors the corrected README. No code, public-API, or
   warning-code change.
 - **README status banner refreshed to current reality (README-ORG-SWEEP).** The banner still read
   "pre-alpha (`0.0.x`), not yet published to npm. Through **Phase 5b** the parser ships …". Both halves
   stale: `@cosyte/ccda` is **published on npm at `0.0.1`** and **public**, and the package is well past
   Phase 5b (the Phase 7 builder / editor / terminology-adapter surface the same paragraph already
-  describes). The banner now states published on npm at `0.0.1`, public, still pre-alpha on the cosyte
+  describes). The banner now states published on npm at `0.0.1`, public, still pre-alpha on the Cosyte
   `0.0.x` ladder, with the parse → serialize → build → edit → BYO-terminology capability intact. No code,
   public-API, or warning-code change.
 - **`docs-content/` now ships the full canonical Diátaxis spine (DOCS-CONTENT-P5), gated hard to the

docs-content/installation.md

@@ -12,7 +12,7 @@ per-condition type declarations, so it works from either module system without c
 has a **single** exact-pinned runtime dependency: the hardened W3C-DOM substrate `@xmldom/xmldom`
 (C-CDA is XML, so a DOM is unavoidable).
 
-> **Status:** **published on npm** and **public**, still pre-alpha on the cosyte `0.0.x`
+> **Status:** **published on npm** and **public**, still pre-alpha on the Cosyte `0.0.x`
 > version ladder (`0.0.x` until first alpha). This page names no version number: run
 > `npm view @cosyte/ccda version` for the current one. The install command below is live.
 

docs-content/intro.md

@@ -14,7 +14,7 @@ spec-clean, round-trip serializer. It mirrors the API shape of the reference par
 Its single runtime dependency is the hardened W3C-DOM substrate `@xmldom/xmldom` (exact-pinned),
 configured XXE-safe.
 
-> **Status:** **published on npm** and **public**, still pre-alpha on the cosyte `0.0.x`
+> **Status:** **published on npm** and **public**, still pre-alpha on the Cosyte `0.0.x`
 > version ladder (`0.0.x` until first alpha). This page names no version number: run
 > `npm view @cosyte/ccda version` for the current one, which is the only answer that cannot go
 > stale between releases. The parser ships

documentation/agent-notes.md

@@ -2541,7 +2541,7 @@ deleted; the imperative as it stood is reproduced here verbatim.
   assumed: only squash merge is allowed, with `squash_merge_commit_title: COMMIT_OR_PR_TITLE` and
   `squash_merge_commit_message: COMMIT_MESSAGES`, so the subject comes from the PR title and the
   body comes from the branch commit messages. **The PR body does not land**; it is scanned anyway,
-  because it is a cosyte surface in its own right. When the gate goes red the fix is never to
+  because it is a Cosyte surface in its own right. When the gate goes red the fix is never to
   re-encode the character: rewrite with a period, colon, comma, or parentheses.
   - **It is the text-only script variant, and dropping `grep -I` is the load-bearing part here.**
     `src/profiles/merge.ts` uses two raw NULs as the separator in `toleranceKey`'s composite key.
@@ -3212,7 +3212,7 @@ lessons is not a substitute for it. `scripts/check-agent-notes-contract.mjs` and
 overclaim.** The split landed across the fleet, but the contract did not: measured over the
 meta-repo's submodules on 2026-08-06, **`config`, `hl7` and `workflow` have no
 `documentation/agent-notes.md` at all** (nor do the non-package repos `crew` and `knowledgebase`).
-A gate asserting "every cosyte repo carries one" is a universal that three package repos already
+A gate asserting "every Cosyte repo carries one" is a universal that three package repos already
 break. What this one asserts is what `ccda` itself promises, which is also why it lives in this
 repo's CI and costs the meta-repo's capped automation plane nothing. **Do not promote it to an
 umbrella script**, and do not restate it as a fleet rule.