@cosyte/cli 0.1.0 → 0.1.1

package/CHANGELOG.md

@@ -18,7 +18,7 @@ still do. Each entry was assigned to the release whose tag first contains it, re
 **What 0.1 means for you.** This is the first release whose commands, output and exit codes we treat
 as settled: command names, flags, the JSON output shapes, the exit-code contract (`0`, `1`, `2`,
 `65`, `66`, `69`, `70`, `74`) and the diagnostic codes are the surface we keep stable. It covers the
-`cosyte` command over all eight cosyte formats (`parse`, `validate`, `inspect`, `fmt`, `convert`,
+`cosyte` command over all eight Cosyte formats (`parse`, `validate`, `inspect`, `fmt`, `convert`,
 `map-codes`, `redact` / `deid`, `completion`), value-free diagnostics with `--unsafe-show-values` as
 the one opt-in, the `cosyte-mcp` stdio server and the programmatic `core` API. While the package is
 below 1.0, a breaking change bumps the minor version and is called out here; a fix that changes no
@@ -85,7 +85,7 @@ it out.
   - No dependency was added, no manifest field moved, and nothing a consumer receives changed.
 
 - **Every MCP tool now publishes an `outputSchema`, and every tool result conforms to it.** An agent
-  calling a cosyte tool used to receive `structuredContent: { exit, ok }` with no schema to check it
+  calling a Cosyte tool used to receive `structuredContent: { exit, ok }` with no schema to check it
   against, so deciding whether a result held data or a diagnostic meant pattern-matching a text blob.
   Each of the four tools now advertises an output schema and a `title` on `tools/list`, and every
   dispatch path (success, negative verdict, hard failure, usage error, internal error) returns
@@ -217,6 +217,8 @@ it out.
 
 ### Changed
 
+- **Published through npm trusted publishing, with provenance.** The code is unchanged from 0.1.0:
+  the commands, flags, output, exit codes and diagnostic codes are the same. Only the README differs.
 - **The CLI now runs on the 0.1 releases of every `@cosyte` library it uses except `@cosyte/deid`.**
   The two required dependencies, `@cosyte/hl7` and `@cosyte/terminology`, and the optional
   `@cosyte/astm`, `@cosyte/ccda`, `@cosyte/dicom`, `@cosyte/mllp`, `@cosyte/ncpdp`,
@@ -795,7 +797,7 @@ node_modules/@cosyte/cli/vendor/cosyte-fhir-0.0.0.tgz`. The siblings are now rea
     provenance/OIDC, the vendored-`file:`→npm dep swap, and the two standing founder stops).
 
 - **Phase 6: six more formats + streaming + shell completion (ADR 0025).** The `cosyte` CLI now wraps
-  **all eight cosyte formats**, routed through a single lazy **per-format adapter registry**
+  **all eight Cosyte formats**, routed through a single lazy **per-format adapter registry**
   (`src/core/parsers.ts`) that replaces the old per-command `hl7 ? : fhir` branches and makes support
   **per (format, operation)**. An unsupported (format, op) is a value-free `CLI_FORMAT_UNSUPPORTED`,
   never a fake (ADR 0018).
@@ -978,7 +980,7 @@ parse` invocation never loads it; the core works with the SDK absent (`--omit=op
   repo for this character, find the places it is a value rather than punctuation and convert those by
   hand, to a word, first.
 
-- **No cosyte surface in this repo uses an em dash any more, and a CI gate keeps it that way.** The
+- **No Cosyte surface in this repo uses an em dash any more, and a CI gate keeps it that way.** The
   brand rule (`knowledgebase/06-brand/voice-and-tone.md`, "No em dashes. Ever.") bans `U+2014`
   outright and names commit messages explicitly. Measured byte-level over **all 124 tracked files**,
   not over markdown alone: **659 occurrences across 87 files**, all as the literal character and none

package/README.md

@@ -7,12 +7,11 @@
 
 # @cosyte/cli
 
-> The **cosyte CLI**: a PHI-safe developer front door over the `@cosyte/*` healthcare parsers.
+> The **Cosyte CLI**: a PHI-safe developer front door over the `@cosyte/*` healthcare parsers.
 
 `@cosyte/cli` is a **`bin` package**: its primary artifact is the `cosyte` command on your `PATH`. Pipe
 a raw message from a hospital feed into the terminal and get typed, structured JSON back in one line,
-without writing code, without reading the spec, and **without ever being handed a confident wrong value
-or a silent success on a malformed message**.
+without writing code and without reading the spec.
 
 ```bash
 cat adt.hl7 | cosyte parse -
@@ -51,15 +50,16 @@ outside this repository and exercised, which is the check a `npm publish --dry-r
 **FHIR support arrives through a peer, not a declared dependency.** `@cosyte/fhir` is not in this
 package's manifest. `npm install` brings it in as the peer dependency of `@cosyte/transform`, one of
 this package's optional dependencies, and the FHIR `parse` / `inspect` / `fmt` / `validate` commands
-and `convert` use that copy. If your package manager skips optional dependencies or does not install
-peers, a command whose library is missing reports a value-free `CLI_PARSER_UNAVAILABLE` and exits
-`69`: it never guesses, and it never blames your input. HL7 v2 and `map-codes` run on the two hard
-dependencies, `@cosyte/hl7` and `@cosyte/terminology`, and always work.
+and `convert` use that copy. Install with optional dependencies, as `npm install` does by default. If
+a library a command needs is still missing, for example a peer your package manager did not install,
+the command reports a value-free `CLI_PARSER_UNAVAILABLE` and exits `69`: it never guesses, and it
+never blames your input. HL7 v2 and `map-codes` run on the two hard dependencies, `@cosyte/hl7` and
+`@cosyte/terminology`.
 
 > **Status:** `0.1`. While the package is below 1.0, a breaking change ships in a minor version and is
 > called out in the changelog. `0.0.1` and `0.0.2` are on npm and **cannot be installed** (see above);
 > every later version installs. The `cosyte` command wraps **all eight
-> cosyte formats** (**HL7 v2**, **FHIR R4**, **X12**, **ASTM**, **NCPDP SCRIPT**, **C-CDA**, **DICOM**,
+> Cosyte formats** (**HL7 v2**, **FHIR R4**, **X12**, **ASTM**, **NCPDP SCRIPT**, **C-CDA**, **DICOM**,
 > and **MLLP**) plus the `@cosyte/transform` and `@cosyte/terminology` higher-layer libraries, with
 > conservative content-format autodetection and a documented exit-code contract:
 >
@@ -365,8 +365,7 @@ subprocess**, not a hosted endpoint. Register it in an MCP client's config:
 > **`--package` is required, and the shorter `["-y", "@cosyte/cli", "mcp"]` does not work**: it fails
 > with `could not determine executable to run`, for the `npx` executable-selection reason described
 > under [Run it](#run-it) above. This also needs a version that can be installed at all, so not
-> `0.0.1` or `0.0.2`. The `convert` tool reports `CLI_PARSER_UNAVAILABLE` from an npm install, because
-> the FHIR library is not on the registry.
+> `0.0.1` or `0.0.2`.
 
 `cosyte mcp` and the standalone `cosyte-mcp` bin both start the stdio server. It exposes four tools
 (`parse`, `validate`, `inspect`, `convert`), each calling the same command the terminal runs, so the CLI
@@ -382,8 +381,8 @@ text content block carries the serialized JSON of that same structured result. S
 per-tool payload shapes.
 
 The MCP SDK (`@modelcontextprotocol/sdk`) is the CLI's only third-party runtime dependency; it is
-declared **optional** and loaded only on the MCP path, so a `cosyte parse` invocation never pulls it and
-the core works with the SDK absent. The server surface is importable via the `@cosyte/cli/mcp` subpath
+declared **optional**, and the programmatic core (the `.` subpath) loads with the SDK absent. The server
+surface is importable via the `@cosyte/cli/mcp` subpath
 (`createMcpServer`, `startStdioServer`, `dispatchTool`, `TOOL_DEFS`).
 
 ## Programmatic API

package/dist/bin/cosyte-mcp.cjs

@@ -114,7 +114,7 @@ function toCliError(err) {
 }
 
 // src/core/version.ts
-var VERSION = "0.1.0";
+var VERSION = "0.1.1";
 
 // src/core/format.ts
 var DETECT_PREFIX_BYTES = 512;