docs: capitalize Cosyte in prose

.changeset/README.md

@@ -22,4 +22,4 @@ Pick the bump type from what the change does to the published package. On the `0
   and the break has to be spelled out in the summary, because the number alone tells a consumer on
   a `0.x` release nothing.
 
-See the cosyte version ladder in the meta-repo's `documentation/conventions.md`.
+See the Cosyte version ladder in the meta-repo's `documentation/conventions.md`.

CHANGELOG.md

@@ -421,7 +421,7 @@ paragraphs. No entry was reworded.
 
 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, so the API can
 change with no deprecation cycle. **No version literal is written in this preamble, on purpose**:
 what is published is a fact about the registry (`npm view @cosyte/mllp version`) and about
@@ -793,7 +793,7 @@ what is published is a fact about the registry (`npm view @cosyte/mllp version`)
 - **`docs-content/installation.md` publish-status note corrected (README-ORG-SWEEP).** The Status
   callout said the package was "not yet published to npm" and that the install command was "the shape
   it will take at first publish": stale now that `@cosyte/mllp` is published on npm at `0.0.1` and
-  public. Rewritten to state it is published and public, still pre-alpha on the cosyte
+  public. Rewritten to state it is published and public, still pre-alpha on the Cosyte
   `0.0.x`-until-first-alpha ladder (no API-stability promise), and that `npm install @cosyte/mllp` is
   live. Docs only: no runtime or public-API change.
 
@@ -1212,8 +1212,8 @@ what is published is a fact about the registry (`npm view @cosyte/mllp version`)
   *bounds*. Fixed: the scan is now `readMshSegment`, which bounds the MSH at its terminator before
   reading any field out of it. A field that does not exist reads as **absent**, never as the next
   segment's contents.
-- **`ack-from-hl7` could not echo a control ID verbatim, so a cosyte client could not correlate a
-  cosyte server's ACK (MLLP-ACK-UTF8).** `buildMllpAck` decoded the inbound through the peer
+- **`ack-from-hl7` could not echo a control ID verbatim, so a Cosyte client could not correlate a
+  Cosyte server's ACK (MLLP-ACK-UTF8).** `buildMllpAck` decoded the inbound through the peer
   parser's charset machinery and re-encoded the ACK through a hardcoded **`utf8`**. The two are not
   inverses. A control-ID byte `0x8B` (legal under an `MSH-18` of `8859/1`, and the exact case
   `MLLP-CORRELATOR-ASCII` had just fixed on the client) came back out of MSA-2 as the **two** bytes
@@ -1420,7 +1420,7 @@ what is published is a fact about the registry (`npm view @cosyte/mllp version`)
 ### Added
 
 - **Trademark notice (`TRADEMARKS.md`).** This package names third-party systems to describe what it
-  interoperates with; the notice records that cosyte is not affiliated with, endorsed by, or
+  interoperates with; the notice records that Cosyte is not affiliated with, endorsed by, or
   sponsored by any of them, that every reference is descriptive, and that the built-in profiles are
   authored from public sources only. Added to `files` so it ships inside the published tarball, not
   just on GitHub. Documentation only: no runtime or API change.

CLAUDE.md

@@ -182,7 +182,7 @@ Inherited by depending on the published `@cosyte/*` config packages, never by co
 
 ## Standing disciplines (every change)
 
-These bind every change in this repo (mirrored from the cosyte meta-repo's `documentation/conventions.md`):
+These bind every change in this repo (mirrored from the Cosyte meta-repo's `documentation/conventions.md`):
 
 1. **Documentation follows code.** A public-surface / stack / status change isn't done until its docs are: this package's own docs (`docs-content/` + JSDoc), and (in the meta-repo) its
    `documentation/repos/<repo>.md` and the `ecosystem-map.md` status table.

README.md

@@ -350,7 +350,7 @@ commit and is deliberately hard to bypass.
 ## Trademarks
 
 Epic, Cerner, Mirth Connect, NextGen, and Google Cloud Healthcare are trademarks of their respective
-owners. cosyte is not affiliated with, endorsed by, or sponsored by any of them. The names identify
+owners. Cosyte is not affiliated with, endorsed by, or sponsored by any of them. The names identify
 the engines this package is tested against, and those it is not. See
 [TRADEMARKS.md](./TRADEMARKS.md).
 

TRADEMARKS.md

@@ -1,6 +1,6 @@
 # Trademarks
 
-`@cosyte/mllp` is an independent open-source project. cosyte is **not affiliated with, endorsed by,
+`@cosyte/mllp` is an independent open-source project. Cosyte is **not affiliated with, endorsed by,
 or sponsored by** any company named in this repository or its documentation.
 
 ## Why these names appear

documentation/agent-notes.md

@@ -910,7 +910,7 @@ section is emptied to its heading, or an anchor is edited on one side of the pai
 other. Twenty repos took the same split. None of them had a check for any of it.
 
 **▶ IT IS NAMED FOR WHAT IT CHECKS AND IT IS NOT A UNIVERSAL, AND THAT IS THE DECISION IN THIS
-SECTION.** The tempting framing is "every cosyte repo has a `CLAUDE.md` plus an
+SECTION.** The tempting framing is "every Cosyte repo has a `CLAUDE.md` plus an
 `agent-notes.md`, so gate the contract". **Measured 2026-08-06 on the umbrella's own checkout:
 `config`, `hl7` and `workflow` have no `documentation/agent-notes.md` at all.** So the
 ecosystem-wide contract is either not universal or is broken in three places, and a gate written

documentation/release-0.1.0-readiness.md

@@ -27,7 +27,7 @@ Two files in this checkout carried the guidance, and both said the same thing be
 `.changeset/README.md`, as it stood before this change:
 
 > 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`.
 
 Both defer to a file that is not in this checkout and was not read for this record. What is in the
 checkout is the instruction to pick `patch` unconditionally, and that instruction is what produced a