@cosyte/x12 0.1.1 → 0.1.2

package/CHANGELOG.md

@@ -1952,7 +1952,7 @@ required control number and this builder never invents one, so nothing is emitte
   composite. Escaping against a guessed delimiter set is a value corruption rather than a safe
   default: `unescapeRelease` preserves `?X` verbatim for any `X` outside the reader's declared set,
   so a value released against the wrong delimiter comes back carrying a stray `?`. The defaults are
-  unchanged and are the cosyte archetype, which this function cannot verify, so state the separators
+  unchanged and are the Cosyte archetype, which this function cannot verify, so state the separators
   if you embed a TA1 in an envelope that declares different ones.
 
   **A non-string element now refuses** with `AckBuildError` and the existing `X12_ACK_INVALID_SPEC`
@@ -3043,7 +3043,7 @@ string, …` - which `esc` cannot, being unary.
 
 - **Em-dash brand gate in CI (`scripts/check-no-emdash.sh`, `pnpm check:no-emdash`,
   `.github/workflows/no-emdash.yml`; `EMDASH-CONFORMANCE`).** The founder directive of 2026-07-24
-  (`knowledgebase/06-brand/voice-and-tone.md`) bans `U+2014` outright across every cosyte surface
+  (`knowledgebase/06-brand/voice-and-tone.md`) bans `U+2014` outright across every Cosyte surface
   and names commit messages explicitly, and the meta-repo's `documentation/conventions.md` has
   described the rule as CI-gated; x12 was one of the repos where it was not. This ports
   `knowledgebase`'s scanner (the text-only variant, correct here because x12 tracks no binaries:
@@ -3138,7 +3138,7 @@ string, …` - which `esc` cannot, being unary.
 ### 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.
@@ -3792,7 +3792,7 @@ EV/SS`), and HL-04 has-child flag from the nested input tree, so an
     helper). The `X12ClaimNote` JSDoc explicitly flags NTE-02 as
     PHI-bearing (provider-supplied free text). Every Phase 5 fixture
     is synthetic (test names `TEST PATIENT` / `SUB LAST` / `PATIENT
-CHILD`; sequential member IDs `MEMBER001`–`MEMBER011` etc.; NPI-
+CHILD`; sequential member IDs `MEMBER001` to `MEMBER011` etc.; NPI-
     shaped sequential numbers; obvious test addresses) and matches
     the established 835 fixture conventions.
   - **Known limitations after this phase** (deliberate v1 scope; none
@@ -3980,7 +3980,7 @@ refresh:code-lists` arrives in Phase 10); no per-payer profile
 
 - **Phase 3: 999 + TA1 acknowledgments (TR3 005010X231A1).** Two
   pure-function ack surfaces ship side-by-side; neither auto-sends, opens
-  a socket, or touches the filesystem. The cosyte ack archetype: the
+  a socket, or touches the filesystem. The Cosyte ack archetype: the
   library MECHANICALLY builds the disposition it is told and REFUSES to
   fabricate an Accept against a non-empty error list. Mirrors hl7's
   upcoming `buildAck` boundary and mllp's commit-contract pattern.
@@ -4001,7 +4001,7 @@ refresh:code-lists` arrives in Phase 10); no per-payer profile
     a TA1 inside an open functional group is still flagged as unexpected
     (non-spec). `parseTA1(interchange)` returns the typed `X12AckTA1`
     for the first captured TA1 (or `undefined`). `buildTA1(spec)` emits
-    a fixed-position 5-element `Ta1Segment` (`TA101`–`TA105`). Caller
+    a fixed-position 5-element `Ta1Segment` (`TA101` to `TA105`). Caller
     wraps it in their preferred envelope. Both standalone TA1-only
     interchanges (ISA → TA1 → IEA, no GS) and embedded TA1s round-trip.
   - **Safety guards (refused via `AckBuildError`):** `build999` refuses
@@ -4020,7 +4020,7 @@ refresh:code-lists` arrives in Phase 10); no per-payer profile
     `IK3_SYNTAX_ERROR_CODES` (code list 716, 13 codes),
     `IK4_SYNTAX_ERROR_CODES` (code list 723, 18 codes),
     `TA1_ACK_CODES` (code list I13: `A`/`E`/`R`),
-    `TA1_NOTE_CODES` (code list I18: `000`–`028`). String-literal
+    `TA1_NOTE_CODES` (code list I18: `000` to `028`). String-literal
     unions are exported for exhaustive narrowing. The helper
     `isAcceptDisposition(code)` returns true for `A`/`E`/`P` and false
     for the four reject codes.
@@ -4165,7 +4165,7 @@ safety` test blocks assert no SSN / ISO-date / long-digit-run
 
 ### Changed
 
-- Migrated onto the shared cosyte engineering standard (Phase E). The toolchain
+- Migrated onto the shared Cosyte engineering standard (Phase E). The toolchain
   is now inherited from the published `@cosyte/*` config packages instead of
   per-repo copies: `tsup.config.ts` uses `cosyteTsup`, `vitest.config.ts` uses
   `cosyteVitest`, and `eslint.config.js` is the three-line `cosyte` wrapper.

package/KNOWN-LIMITATIONS.md

@@ -672,7 +672,7 @@ model.
     nothing else - `buildTA1` still emits no terminator. Escaping against a guessed set is a value
     corruption rather than a safe default: `unescapeRelease` preserves `?X` verbatim for any `X`
     outside the declared set, so a value released against the wrong delimiter comes back carrying a
-    stray `?`. **The defaults are the cosyte archetype and this function cannot verify them** - if
+    stray `?`. **The defaults are the Cosyte archetype and this function cannot verify them** - if
     you embed a TA1 in an envelope that declares different separators, state them.
   - **A non-string element now REFUSES** with `AckBuildError` / `X12_ACK_INVALID_SPEC`, and that is a
     prerequisite rather than a bonus. Releasing a value means routing it through the escape helper,
@@ -1555,7 +1555,7 @@ N-char spec limit` refusal, one per emitting module, where the branch fires **be
   2. **Whether an `X12Decimal` carries the SCALE you meant.** `fromString("0.3")` and
      `fromString("0.30")` are both accepted and both emit verbatim. That choice is yours.
   3. **The delimiter set `buildTA1` releases against**, per the paragraph above. It defaults to the
-     cosyte archetype and the function cannot verify it; state the separators on `BuildTA1Options`
+     Cosyte archetype and the function cannot verify it; state the separators on `BuildTA1Options`
      if you embed a TA1 in an envelope that declares different ones.
   4. **`build835`'s balance-equation amounts, which refuse UNTYPED.** `build835` runs its balance
      guard before it builds the escape helper, and that guard calls `X12Decimal` methods on your
@@ -1874,10 +1874,10 @@ N-char spec limit` refusal, one per emitting module, where the branch fires **be
     applied and this package applies none.
 - **No transport.** AS2, SFTP, and MLLP-style delivery are out of scope. This is a parser/serializer,
   not a communications stack.
-- **Published, still pre-alpha.** The package is published on npm as `@cosyte/x12` from a public
-  repo, but it stays on the `0.0.x`-until-first-alpha ladder. `npm view @cosyte/x12 version` is the
-  only source of truth for the current version, so this page does not restate one. Treat the API as
-  pre-alpha and pin the exact version until the first alpha.
+- **Below 1.0.** The package is published on npm as `@cosyte/x12` from a public repo, at `0.1`. Its
+  exported readers, builders, types and warning codes are the surface we keep stable, and below 1.0
+  a breaking change bumps the minor version and is called out in the changelog with its migration.
+  `npm view @cosyte/x12 version` is the only source of truth for the current version.
 - **A 276 hierarchical level whose declared parent does not resolve is left off the returned tree.**
   The 276 reader attaches a level by its own HL-02 and by nothing else, so a pointer naming a level
   that is not present, a pointer naming a level of the wrong kind, and a parent chain that returns

package/README.md

@@ -31,7 +31,7 @@ a stable code instead of failing or guessing.
 
 ## Status
 
-**Version 0.1.1**, published on npm from a public repository.
+**Version 0.1.2**, published on npm from a public repository.
 
 From `0.1.0` the public API is settled and safe to depend on: the exported readers, builders,
 types and warning codes are the surface we keep stable, and the warning registry only ever gains
@@ -179,8 +179,7 @@ Everything ships from one entry point; there are no subpath imports.
   transaction set into a typed one (`get835`, `get837Claims`, `get270Inquiry`, `get271Eligibility`,
   `get276StatusInquiry`, `parse999`, `parseTA1`, and the rest).
 - **Emit.** `serializeX12` and `buildInterchange` are the general path, and every transaction set
-  with a reader also has a domain builder (`build835`, `build837P`, `build271`, and the rest) that
-  layers that guide's own invariants on top.
+  with a reader also has a domain builder (`build835`, `build837P`, `build271`, and the rest).
 - **Errors and warnings.** Parsing is lenient, and only **four** structural failures are ever fatal
   (`X12_NO_ISA_HEADER`, `X12_ISA_TOO_SHORT`, `X12_INVALID_DELIMITERS`, `X12_EMPTY_INPUT`).
   Everything else arrives on `ix.warnings` as a stable code with positional context, so a tolerated
@@ -295,7 +294,7 @@ must be synthetic: never open a pull request carrying a real patient's data.
 
 ## Trademarks
 
-Availity and Blue Cross Blue Shield are trademarks of their respective owners. cosyte is not
+Availity and Blue Cross Blue Shield are trademarks of their respective owners. Cosyte is not
 affiliated with, endorsed by, or sponsored by any of them. The names identify the trading partners
 whose companion-guide deviations the built-in profiles accommodate. See
 [TRADEMARKS.md](./TRADEMARKS.md).

package/TRADEMARKS.md

@@ -1,6 +1,6 @@
 # Trademarks
 
-`@cosyte/x12` is an independent open-source project. cosyte is **not affiliated with, endorsed by,
+`@cosyte/x12` 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

package/dist/index.cjs

@@ -15395,7 +15395,7 @@ var profiles = Object.freeze({
 });
 
 // src/index.ts
-var VERSION = "0.1.1";
+var VERSION = "0.1.2";
 
 exports.AAA_CONDITION_LEVELS = AAA_CONDITION_LEVELS;
 exports.AAA_FOLLOW_UP_ACTION_CODES = AAA_FOLLOW_UP_ACTION_CODES;