@cosyte/astm 0.1.0 → 0.1.1

package/CHANGELOG.md

@@ -53,6 +53,9 @@ exists for.
 
 ### Changed
 
+- **Published through npm trusted publishing, with provenance.** The code, API and behavior are
+  unchanged from 0.1.0. Only the README and some doc comments differ: a few doc comments now write
+  number ranges with "to".
 - **Every published release now carries a machine-readable dependency inventory as a downloadable
   asset.** No published value, type, warning code or emitted byte moves: this entry is release
   infrastructure only, and nothing under `src/` is touched. The inventory is a CycloneDX document
@@ -387,7 +390,7 @@ exists for.
   adding a workflow that would have to be made a required context separately. It asserts that every
   pointer resolves, that no section a pointer reaches is empty, that the record stays reachable from
   the always-read file, and that the always-read file still links the record by path. It asserts
-  **no** ecosystem-wide contract: several cosyte repos carry no such record at all, and a gate
+  **no** ecosystem-wide contract: several Cosyte repos carry no such record at all, and a gate
   phrased as though every repo did would be an overclaim.
   - **The matcher was re-derived against this tree rather than ported, and that was the whole job.**
     Both sibling spellings score **zero** here: the path-qualified form used by `ccda` and `mllp`,
@@ -1430,7 +1433,7 @@ exists for.
   **The refusal removes no capability.** `composeAstmFrames` already accepted `Uint8Array`, so a
   consumer who knows their instrument's code page encodes with their own encoder and passes bytes,
   which are written through untouched. A stream whose every character is Latin-1 is byte-identical
-  to before, the full `0x00`–`0xFF` range included. The **record** layer is deliberately unchanged:
+  to before, the full `0x00` to `0xFF` range included. The **record** layer is deliberately unchanged:
   `serializeAstmRecords` returns a `string`, which is not yet bytes, so the caller keeps the choice.
 
   **Stated no wider than it was measured.** This closes the string-to-bytes step only. It is not a
@@ -1907,7 +1910,7 @@ phase 8` passes while `Phase 8` reds). An arm keyed on a following digit was wri
   acceptance under a tolerating profile) is _measured_, on the tree before and after the change.
 
 - **The em dash (U+2014) is gone from every tracked file, and a CI gate keeps it out**
-  (`EMDASH-CONFORMANCE`). The brand rule bans the character outright across every cosyte surface
+  (`EMDASH-CONFORMANCE`). The brand rule bans the character outright across every Cosyte surface
   and names commit messages explicitly; this package was the last one it had not reached, and the
   only one where it did not arrive on a clean tree. **1,129 occurrences across 108 of the 142
   tracked files** were rewritten with a comma, a colon, or a period. The sweep and the gate are one
@@ -2371,7 +2374,7 @@ phase 8` passes while `Phase 8` reds). An arm keyed on a following digit was wri
 
 ## [0.0.1] - 2026-07-22
 
-The first pre-alpha release. The package begins its public history at `0.0.x`, per the cosyte version
+The first pre-alpha release. The package begins its public history at `0.0.x`, per the Cosyte version
 ladder (`0.0.x` until first alpha).
 
 ### Added
@@ -2499,7 +2502,7 @@ warnings: readonly AstmFrameWarning[] }`. A frame is `<STX> FN text <ETB|ETX> CS
   - **Modulo-256 checksum** over the bytes after `STX` up to and **including** the `ETB`/`ETX`
     terminator, two hex chars: **verified on decode, emitted uppercase, accepted lowercase** (a real
     vendor quirk). `computeChecksum` / `toChecksumHex` / `parseChecksumHex` exported.
-  - **Frame-number `0`–`7` sequencing** (rolls over `7 → 0 → 1`, starts at `1`) and **multi-frame record
+  - **Frame-number `0` to `7` sequencing** (rolls over `7 → 0 → 1`, starts at `1`) and **multi-frame record
     reassembly**: text is capped at **240 bytes** (the seven control bytes are **not** counted), `ETB`
     is intermediate / `ETX` final. `parseFramedAstm(bytes, opts?)` composes the framing and record layers
     at the edge (decode → reassemble trusted records → `parseAstmRecords`).
@@ -2535,7 +2538,7 @@ defaulted: boolean; warnings }`. A leading `STX`/`ENQ` ⇒ **framed** (serial, a
     by `ltpInitialState()`. Events are the four LTP control signals (`enq`/`ack`/`nak`/`eot`) plus a
     codec-decoded `frame`; actions are `sendAck` / `sendNak` / `sendEot` / `deliverRecord`. It models
     the LIS01-A2 establishment → transfer → termination phases as `neutral ⇄ transfer`, reassembling
-    `ETB…ETX` runs into delivered records and tracking the `0`–`7` frame sequence.
+    `ETB…ETX` runs into delivered records and tracking the `0` to `7` frame sequence.
   - **ACK-failsafe (safety-critical, borrowed from `mllp`).** A frame the codec did not vouch for (a
     **bad checksum**, an **unterminated** frame, or one **out of sequence**) is answered with `NAK`,
     **never** a fabricated positive `ACK`, and its bytes are **never** appended to a record or
@@ -2572,7 +2575,7 @@ EOT` session **reassembles exactly the source records**; a **raw-TCP stream equa
     counters, the `L` terminator) is **computed, not guessed** (a sequence number may be overridden).
   - **Frame encoder.** `composeAstmFrames(records, opts?)` is the exact inverse of `decodeAstmFrames`:
     it wraps reassembled record bytes into `<STX> FN text <ETB|ETX> CS <CR><LF>` frames with the
-    modulo-256 **checksum** and the `0`–`7` **frame number** **computed** (never accepted-as-given or
+    modulo-256 **checksum** and the `0` to `7` **frame number** **computed** (never accepted-as-given or
     faked; emitted uppercase), numbered continuously across the stream (start `1`, roll over `7 → 0`),
     and every record over **240** text bytes **split** `ETB…ETX` (the seven control bytes never counted).
     `serializeFramedAstm(msg | records)` composes both emit layers at the edge: the mirror of

package/README.md

@@ -105,7 +105,7 @@ ASTM instrument traffic carries PHI. This section says what the library does wit
 
 ## API
 
-`@cosyte/astm` is a zero-dependency TypeScript toolkit that follows the cosyte parser archetype: a lenient
+`@cosyte/astm` is a zero-dependency TypeScript toolkit that follows the Cosyte parser archetype: a lenient
 parser that turns real-world, vendor-quirky input into **warnings** rather than failures, paired with
 a serializer that always emits spec-clean output (Postel's Law). It mirrors the API shape of the
 reference parser, [`@cosyte/hl7`](https://github.com/cosyte/hl7).
@@ -529,7 +529,7 @@ An HL7 v2 `DTM` can state its own offset and an ASTM timestamp never can, so the
 differently on purpose: `hl7ToISO` may end in `Z` or `+HH:MM`, `astmToISO` never does. That
 difference is the standards', not the API's.
 
-### The cosyte parser archetype
+### The Cosyte parser archetype
 
 - **Postel's Law**: liberal parser (lenient default + warnings), conservative serializer (always
   spec-clean), so quirks don't propagate downstream on round-trip.

package/dist/index.cjs

@@ -3144,7 +3144,7 @@ function concatBytes3(chunks) {
 }
 
 // src/index.ts
-var VERSION = "0.1.0";
+var VERSION = "0.1.1";
 
 exports.ABNORMAL_FLAG_CODES = ABNORMAL_FLAG_CODES;
 exports.ABNORMAL_FLAG_VOCABULARY = ABNORMAL_FLAG_VOCABULARY;