@cosyte/x12 0.0.1 → 0.0.3

package/CHANGELOG.md

@@ -7,50 +7,201 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+### Added
+
+- **Brand lockup on the README, following the reader's colour scheme (ASSETS-P8).** The README now
+  opens with the shared Cosyte lockup, above the `# @cosyte/x12` heading. It is a `<picture>`
+  element: a `<source>` carrying the on-dark cut for `prefers-color-scheme: dark`
+  (`https://cosyte.com/tile/cosyte-lockup-tile-on-dark-1200x300.png`) and an `<img>` carrying the
+  on-light cut as the fallback (`https://cosyte.com/tile/cosyte-lockup-tile-on-light-1200x300.png`).
+  Both were verified `200` / `image/png` before landing. On GitHub a dark-mode reader gets the dark
+  cut; on npm the `<img>` is lifted out of the `<picture>` by the surrounding anchor so the light cut
+  renders, which is correct there because npmjs.com has no dark mode. The heading and the blockquote
+  under it are unchanged: the lockup reads "Cosyte" while the heading reads `@cosyte/x12`, so the two
+  strings do not collide and nothing is duplicated. The alt text describes the artwork rather than
+  the package, since that is what a screen reader announces on the npm page and what a reader gets if
+  the image fails to load.
+
+  **Recorded because it changed inside the unreleased window rather than after it.** This entry first
+  landed describing a _per-package_ banner (`cosyte-banner-x12-1200x300.png`), which baked the
+  package name and the tagline into pixels and duplicated the two lines beneath it. It explicitly
+  chose a plain markdown image over an `<img>` or a `<picture>` pair, on the ground that whether
+  npm's markdown sanitizer preserves `<picture>` was unverified. That was an accurate statement of
+  what was known at the time. It has since been measured on a published package page: the sanitizer
+  keeps the `<picture>`, and the anchor wrapper hoists the `<img>` out of it, so the light cut
+  renders. The per-package banner was replaced before any release carried it, so no published
+  version of this package ever had it, and this is written as one change rather than an addition
+  followed by a replacement. The superseded reason is kept here rather than removed, because a
+  record that quietly flips a stated reason is worse than one that shows the correction.
+
 ### Fixed
 
+- **Stale version claim removed from five public pages (ASSETS-P8).** `README.md`,
+  `KNOWN-LIMITATIONS.md`, `docs-content/intro.md`, `docs-content/installation.md`, and
+  `docs-content/troubleshooting.md` all asserted the package was "published on npm at `0.0.1`". The registry says
+  `0.0.2`. The literal was pinned by a previous docs sweep and went stale on the very next release,
+  so it is now removed rather than re-pinned: the npm badge renders the live version on the README,
+  and each page points at `npm view @cosyte/x12 version` as the source of truth. Docs only, no
+  runtime or public-API change.
+- **Scope claim corrected: the 270 and 276 inquiries have no typed model (ASSETS-P8).** The README
+  status line and "What's inside" list, and `docs-content/intro.md`, claimed "the full v1 read scope
+  (270/271, 276/277/277CA, …) and emit scope … are complete". There is no `get270` / `get276` reader
+  and no `build270` / `build276` builder, and no 270 or 276 dispatch anywhere in `src/`;
+  `get271Eligibility` and `get277Status` return `undefined` for any other `ST-01`. The inquiry
+  directions parse into segments and dot-paths like any other X12 input but decode into no typed
+  model. The claim is now stated per transaction on every page that made it: the README status line
+  and "What's inside" list, `docs-content/intro.md` (both the status block **and** the "transaction
+  sets it covers" list under it), `docs-content/spec-notes-transaction-sets.md` (the lead-in and the
+  `270 / 271` + `276 / 277` rows of the reader/builder map), and `docs-content/cookbook.md`, which
+  said the 270 was "a read-only surface" when it has no reader either. The gap is recorded in
+  `KNOWN-LIMITATIONS.md`, `docs-content/troubleshooting.md`, and this repo's `CLAUDE.md`. Docs only,
+  no runtime or public-API change.
+- **Serializer description corrected to its actual defaults (ASSETS-P8).** The README described "a
+  strict, spec-clean serializer with recomputed envelope counts", which reads as default behaviour,
+  and `CLAUDE.md` said the serializer "always emits spec-clean X12". `serializeX12` is byte-faithful
+  by default; `{ specClean: true }` reconciles the envelope, and the corrected counts need
+  `{ specClean: true, recomputeCounts: true }` together, because `recomputeCounts` is inert on its
+  own (`const recompute = specClean && opts.recomputeCounts === true`). A mismatch is always warned
+  and never silently corrected. Docs only, no runtime or public-API change.
+- **PHI claim narrowed to what the library actually guarantees (ASSETS-P8).** The README said
+  "warnings/errors that carry codes and positions but never patient data". Warning messages and
+  builder refusals are PHI-free by construction, but `X12ParseError.snippet` is a bounded (≤ 64
+  character) copy of the offending input, so on real traffic it can carry PHI, and the library does
+  not redact it. That was documented in the source JSDoc and nowhere a consumer reads. The README now
+  states the exception, and it is written up in `KNOWN-LIMITATIONS.md` and
+  `docs-content/troubleshooting.md`. Docs only, no runtime or public-API change.
+- **Developer-docs publish status corrected to the published reality (README-ORG-SWEEP).** The
+  docs.cosyte.com pages (`docs-content/intro.md`, `installation.md`, `troubleshooting.md`) and
+  `KNOWN-LIMITATIONS.md` still said "not yet published to npm" / "gated on the coordinated public
+  launch" (and `KNOWN-LIMITATIONS.md` still read `0.0.0`), contradicting the live `npm install`
+  command already documented. Rewritten to state the package is published at `0.0.1`, public, still
+  pre-alpha on the `0.0.x`-until-first-alpha ladder; the install command is now described as live
+  rather than aspirational. Docs only, no runtime or public-API change.
+- **README status line corrected to the published reality (README-ORG-SWEEP).** The status line still
+  read "pre-alpha (`0.0.x`, not yet published to npm) … the first npm publish is gated on the
+  coordinated public launch," which contradicted the npm-version badge and the `pnpm add @cosyte/x12`
+  install line already in the same README. The package is published on npm at `0.0.1` from a public
+  repo. Rewritten to state that it is published at `0.0.1`, in a public repo, still pre-alpha on the
+  `0.0.x`-until-first-alpha ladder; the read/emit scope claim is unchanged. Docs only, no runtime or
+  public-API change.
+
+### Added
+
+- **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
+  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:
+  all 264 tracked files decode as us-ascii or utf-8 and none holds a NUL byte, measured byte-level
+  2026-07-27) and wires it to a dedicated workflow that checks **both** the tracked files and the
+  **PR title, body, and branch commit messages**, the last of these on the non-default `edited`
+  activity type so a description retitled after the final push is re-checked before a squash merge
+  turns it into the commit message. It is a separate workflow rather than a job in `ci.yml` because
+  `ci.yml` calls the shared reusable pipeline (which runs no arbitrary repo script) and its triggers
+  drive the Node 22 + 24 matrix plus the `release-dry-run` job. x12 was already clean (0 of 21
+  markdown files carried an em dash), so **no content changed**: this is regression prevention only.
+  Dev tooling, no change to the published package surface, parser behavior, or warning codes.
+  **Two limits stated rather than claimed away.** The new check is not yet one of the org ruleset's
+  required contexts (`parser-ci-required-checks` requires `ci / verify (22|24, ubuntu-latest)` and
+  `ci / actionlint`), so today it reds visibly but does not itself block a merge; making it required
+  is an org-level change outside this repo. And a tracked text file holding a NUL byte **and a
+  pattern match** fails this shape closed: grep 3.8 reports `binary file matches` on stderr and the
+  scan refuses. The NUL alone does not trigger it, and the red is remediable by the same rewrite
+  the brand rule already demands. x12 has no NUL-bearing tracked file at all today (zero of 264,
+  measured byte-level).
+- **`docs-content/` now ships the full canonical Diátaxis spine (DOCS-CONTENT-P4).** The sidebar was
+  Overview-only, with `cookbook.md` authored but orphaned (invisible to every reader). This wires the
+  cookbook into **Guides** and adds the rest of the spine every `@cosyte/*` package shares: four new
+  **Core Concepts** pages (the envelope/loop model; the 80/20 transaction sets, mapping each shipped
+  set to its reader/builder pair and the field it preserves verbatim; the tolerance tiers +
+  warning-code model; and decimal-exact money via `X12Decimal`), **Installation** and **Quickstart**
+  tutorials (parse an 835 and post the cash), and a **Troubleshooting & known limitations** page (the
+  fatal-vs-warn model, a symptom→cause table, PHI-in-logs discipline, and the v1 non-goals). Depth is
+  gated to the shipped surface: no unshipped API is documented. Synthetic-only fixtures throughout.
+  Docs only, no runtime or public-API change.
+
+### Fixed
+
+- **`scripts/sync-version.mjs` hardened against two latent defects, and gated in CI
+  (SYNC-VERSION-HARDENING).** Follow-up hardening on the VERSION-SYNC script; ported byte-identically
+  across `hl7`, `x12`, and `mllp`. (1) The version was spliced into `src/index.ts` via
+  `String.prototype.replace` with a _replacement string_, which interprets `$&`, `$1`, `` $` ``, etc.,
+  so a version like `1.2.3-$&x` would inject the matched text and corrupt the `VERSION` constant while
+  exiting 0. The replacement is now a replacer _function_, whose return value is inserted literally.
+  (2) The declaration regex was non-global, so `.replace` silently rewrote the _first_ match; a
+  column-0 decoy (e.g. inside a comment) ahead of the real declaration could be edited instead. The
+  script now matches globally, asserts exactly one declaration, and exits non-zero loudly otherwise.
+  Neither defect is reachable through Changesets today and both previously failed loud rather than
+  shipping a lying `VERSION`, so this is hardening, not a fix for an observed break. The
+  `format`/`format:check` globs now cover `scripts/**/*.mjs` so the script is prettier-gated in CI
+  (the `.mjs` scripts were matched by no format glob before; `scripts/**/*.ts` was already gated).
+  Build tooling only, no runtime or public-API change.
+- **The `intro.md` status/roadmap section was stale**. It described Phase 1/2 as the frontier and
+  listed the now-shipped read + emit + profile surfaces as "coming in later phases." Refreshed to the
+  current shipped reality with an honest pre-alpha status banner.
+- **A latent malformed-ISA fixture in `cookbook.md`.** The self-contained 835 example's ISA padded
+  the sender/receiver IDs to 16 bytes instead of the fixed 15, so the 106-byte ISA was misaligned and
+  delimiter detection would reject it. It went unnoticed because the cookbook block was illustrative,
+  never executed; making the examples runnable under the doc/code-agreement harness surfaced it.
+
+### Changed
+
+- **Every runnable docs snippet is gated by the shared doc/code-agreement harness.**
+  `test/docs-content.test.ts` runs `docSnippetSuite()` (from `@cosyte/vitest-config/snippets`) over
+  `docs-content/`, extracting each ` ```ts runnable ` block, compiling it, executing it against the
+  **built** ESM artifact, and asserting its inline `// =>` results, so a documented example can never
+  silently drift from the shipped code. Bumps the `@cosyte/vitest-config` devDependency to `^0.0.2`
+  for its `/snippets` export.
+
 - **The Release workflow can actually start.** `.github/workflows/release.yml` calls the shared
   `cosyte/.github` pipeline, which requests `contents`/`id-token`/`pull-requests: write`, but declared
-  no `permissions:` of its own — so it inherited the repo default of `contents: read`. A called
+  no `permissions:` of its own, so it inherited the repo default of `contents: read`. A called
   workflow may only downgrade the caller's `GITHUB_TOKEN`, never escalate it, so GitHub rejected the
   workflow at startup (~1s, no jobs, no logs). Every Release run from June 2026 until now failed this
   way, unnoticed, because a `startup_failure` produces no logs to read. The caller job now declares
-  the three scopes explicitly. CI-only — no runtime or API change.
+  the three scopes explicitly. CI-only, no runtime or API change.
 
 - **The `VERSION` export now tracks `package.json`, and the missing `version`
   script is restored (VERSION-SYNC).** Two latent release bugs, both of which
   would have bitten at the first publish. (1) `VERSION` was hardcoded `"0.0.0"`
   in `src/index.ts` while `changeset version` bumps only `package.json`, so a
-  published `0.0.1` would have shipped an export reading `"0.0.0"` — every
+  published `0.0.1` would have shipped an export reading `"0.0.0"`. Every
   consumer asserting on or logging `VERSION` told the wrong version of the
   parser they were running. New `scripts/sync-version.mjs` rewrites the constant
   from `package.json` (idempotent; exits non-zero if the declaration is renamed
-  rather than silently no-op'ing). (2) **No `version` script existed at all** —
-  the shared `cosyte/.github` release workflow drives Changesets with
+  rather than silently no-op'ing). (2) **No `version` script existed at all**.
+  The shared `cosyte/.github` release workflow drives Changesets with
   `version: pnpm run version`, which would have failed with `ERR_PNPM_NO_SCRIPT`,
   so the "Version Packages" PR could never have been opened. The guard in
   `test/sanity.test.ts` was **inverted**: it asserted
-  `expect(VERSION).toBe("0.0.0")` — literal against literal — which stays green
+  `expect(VERSION).toBe("0.0.0")` (literal against literal) which stays green
   through exactly this drift and goes red on a _correct_ bump. It now compares
   `VERSION` against `package.json` at test time. Ported from `@cosyte/mllp`
   (MLLP-10), in the canonical form `@cosyte/hl7` carries. No version bumped,
-  nothing published — still `0.0.0`.
+  nothing published, still `0.0.0`.
 
 ### Added
 
-- **Phase 10 — release hardening.** The v1 close-out; no new parser
+- **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
+  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.
+
+- **Phase 10: release hardening.** The v1 close-out; no new parser
   surface, just the gates, tooling, and docs that make the package
   trustworthy to publish.
   - **Publish-pipeline proof.** A new `release-dry-run` CI job proves a
     real release would succeed without burning a version or needing
-    registry auth — `pnpm publish --dry-run` exercises the publish command
+    registry auth: `pnpm publish --dry-run` exercises the publish command
     path and `npm pack --dry-run` asserts the publishable tarball assembles
     with the right `files` set + built `dist/`. The real provenance publish
     stays gated on the public launch.
   - **Nightly amplified fuzz** (`.github/workflows/fuzz.yml`). Re-runs the
     byte-flip / never-throw property targets at a higher iteration count
-    (`X12_FUZZ_RUNS`) with a rotating seed (`X12_FUZZ_SEED`) — the deep
-    search that would slow the per-commit run — and opens/auto-closes a
+    (`X12_FUZZ_RUNS`) with a rotating seed (`X12_FUZZ_SEED`), the deep
+    search that would slow the per-commit run, and opens/auto-closes a
     sticky issue on failure. The per-commit suite is unchanged (pinned
     seed, base counts, coverage-stable); a finding is replayable via the
     printed seed. New test helper `fuzzRuns()` scales only the true fuzz
@@ -70,20 +221,20 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
     `RELEASE_CHAR`).
   - **Known limitation carried forward:** an external-oracle differential
     corpus (vs CMS Medicare 835) is not yet wired, pending a
-    redistribution-terms review — see `KNOWN-LIMITATIONS.md`.
+    redistribution-terms review. See `KNOWN-LIMITATIONS.md`.
 
 ### Security
 
-- **Dev-dependency advisory remediation (no runtime impact —
+- **Dev-dependency advisory remediation (no runtime impact:
   `@cosyte/x12` ships zero runtime dependencies).** Added scoped
   `pnpm.overrides` pinning two transitive **dev/build-time** packages to
   their patched releases: `esbuild` (`>=0.27.3 <0.28.1` → `0.28.1`,
-  GHSA dev-server path-traversal — unreachable here: a library build
+  GHSA dev-server path-traversal, unreachable here: a library build
   via `tsup`/`vitest`, never `esbuild serve`) and the
   `@changesets/parse` copy of `js-yaml` (`>=4.0.0 <4.2.0` → `4.2.0`,
   GHSA-h67p-54hq-rp68 merge-key DoS). The `js-yaml@3.14.2` pulled by
   `read-yaml-file@1.1.0` (via `@manypkg/get-packages` →
-  `@changesets/cli`) is **intentionally left** — it calls
+  `@changesets/cli`) is **intentionally left**. It calls
   `yaml.safeLoad`, removed/throwing in js-yaml 4, so it cannot be
   force-upgraded without breaking the release tooling; it only parses
   trusted local repo YAML at release time. Verify gate green on the
@@ -93,8 +244,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 - **Segment splitting now honours the `?`-release-escaped terminator.**
   `splitSegments` (the envelope tokenizer) used a naive `indexOf` for the
-  segment terminator, so a value carrying a literal terminator byte —
-  emitted by `escapeRelease` as `?~` — was split mid-value: the segment
+  segment terminator, so a value carrying a literal terminator byte (emitted by `escapeRelease` as `?~`) was split mid-value: the segment
   was truncated at the `?`, a phantom empty segment was injected, and the
   round-trip silently corrupted the value (the element splitter
   `splitWithRelease` had always been release-aware; only the segment
@@ -108,13 +258,13 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ### Added
 
-- **Profile system — descriptive, fixture-grounded clearinghouse / payer
+- **Profile system: descriptive, fixture-grounded clearinghouse / payer
   companion-guide quirk attribution.** A `defineProfile()` API mirroring
   the sibling `@cosyte/hl7` profile shape, plus a `profiles` namespace of
   built-ins. The parser is already lenient and lossless, so a **v1 profile
   is DESCRIPTIVE**: it attaches attribution metadata to the returned
   `X12Interchange` (`ix.profile`) and powers `partitionWarnings`, but
-  NEVER alters the parse — `groups`, `warnings`, and `isa` are
+  NEVER alters the parse: `groups`, `warnings`, and `isa` are
   byte-identical with and without a profile (proven by a divergence test).
   - **`defineProfile(spec)`** validates the spec (fail-fast on name, then
     Levenshtein "did you mean?" hints on unknown option keys, then the
@@ -123,21 +273,21 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
     position; scalar `description` last-wins), re-validates the composed
     set, and returns a frozen `X12Profile` whose `describe()` yields a
     structured `X12ProfileDescription` bucketed by effect
-    (`relaxes` / `adds` / `requires`) — structured DATA, not hl7's
+    (`relaxes` / `adds` / `requires`): structured DATA, not hl7's
     formatted string, so consumers can program against it.
-  - **The locked HARD RULE — no invented quirks.** Every quirk MUST cite a
+  - **The locked HARD RULE: no invented quirks.** Every quirk MUST cite a
     `fixture` (a relative path under `test/fixtures/`) that actually
     EXHIBITS the deviation; the field is required at the type level and
     enforced in `defineProfile()`. The accuracy suite goes further: a
     per-quirk DEMONSTRATOR registry asserts each cited fixture exhibits its
     claimed deviation, and a shipped quirk with no demonstrator FAILS the
-    suite — so a real-but-irrelevant fixture cannot slip past.
+    suite, so a real-but-irrelevant fixture cannot slip past.
   - **`setDefaultProfile()` / `getDefaultProfile()`** set a process-scoped
     default applied when a `parseX12` call passes no `profile`. An explicit
     `{ profile }` wins; `{ profile: null }` opts out of the default for
     that call. `partitionWarnings(warnings, profile)` splits a parse's
     warnings into `{ expected, unexpected }` on the union of the profile's
-    quirk `expectedWarnings` — the one behavioural hook a v1 profile
+    quirk `expectedWarnings`, the one behavioural hook a v1 profile
     offers.
   - **Built-ins ship ONLY where a Tier-2 fixture grounds them:**
     `profiles.availity` (payer-loop `REF*2U` + service-line `REF*F8`
@@ -145,7 +295,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
     `profiles.bcbsCommon` (backslash component separator, grounded in
     `envelope/bcbs-subelement.edi`). Profiles whose only "deviation" would
     be a canonical `:` baseline (e.g. a generic Medicare FFS profile) are
-    deliberately DEFERRED rather than invented — shipping them would
+    deliberately DEFERRED rather than invented. Shipping them would
     violate the hard rule. Built-ins are reachable only through the
     `profiles` namespace, never the top-level export (mirrors hl7).
   - **API divergence from `@cosyte/hl7`, by design:** `describe()` returns
@@ -157,11 +307,11 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
     and the `X12Profile` / `X12ProfileSpec` / `X12ProfileQuirk` /
     `X12ProfileDescription` / `X12ProfileEffect` / `X12WarningPartition`
     type tree.
-- **Domain builders — `build820` (005010X218 Premium Payment) and
+- **Domain builders: `build820` (005010X218 Premium Payment) and
   `build834` (005010X220A1 Benefit Enrollment and Maintenance).** The emit
   counterparts to `get820Payments` and `get834Header` /
   `get834Enrollments`, layered on the Phase 8 general builder and
-  mirroring the pure-function `build835` pattern — they NEVER auto-send,
+  mirroring the pure-function `build835` pattern. They NEVER auto-send,
   open a socket, or touch the filesystem, and return a frozen
   `X12Interchange`. Completes the v1 emit scope: every v1 transaction now
   has a domain builder.
@@ -175,7 +325,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
     spec is reproduced field-for-field. **The 820 carries no TR3 balance
     equation** (BPR-02 is not required to equal Σ of the RMR open items),
     so the builder emits all monetary amounts VERBATIM and never raises a
-    balance-mismatch refusal — a deliberate contrast with `build835`.
+    balance-mismatch refusal, a deliberate contrast with `build835`.
   - **`build834(spec)`** assembles a complete interchange (one GS..GE
     group, GS-01 `BE`; one ST..SE 834, ST-03 `005010X220A1`) from a typed
     `Build834Spec` (envelope + BGN header + sponsor `N1*P5` / payer
@@ -185,7 +335,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
     the first HD so the read side binds them to the member, not the
     coverage loop. The output round-trips through `get834Header` /
     `get834Enrollments` field-for-field.
-  - **Maintenance type is the 834's safety primitive — emit verbatim,
+  - **Maintenance type is the 834's safety primitive: emit verbatim,
     refuse the unknown.** The builder places the caller-supplied INS-03 /
     HD-01 code (X12 Code Source 875) into the segment VERBATIM and NEVER
     infers or normalizes it; where the lenient read side only WARNS on an
@@ -196,15 +346,15 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
     outside the validated subset is refused.
   - **Refusal, not silent corruption.** `build820` REFUSES a structurally
     impossible spec via a typed `Premium820BuildError`
-    (`X12_820_BUILD_INVALID_SPEC` — no TRN trace, no remittance, a
+    (`X12_820_BUILD_INVALID_SPEC`: no TRN trace, no remittance, a
     remittance with neither an `ENT` nor an `NM1` to open its loop, a
     remittance with no `RMR` open item, an open item with no identity, an
     over-long control number). `build834` REFUSES via a typed
     `Enrollment834BuildError`
-    (`X12_834_BUILD_UNKNOWN_MAINTENANCE_TYPE` — an INS-03 / HD-01 code
-    outside the X12 875 subset; `X12_834_BUILD_INVALID_SPEC` — no member
+    (`X12_834_BUILD_UNKNOWN_MAINTENANCE_TYPE`: an INS-03 / HD-01 code
+    outside the X12 875 subset; `X12_834_BUILD_INVALID_SPEC`: no member
     loop, an empty required INS-03, an over-long control number). Both
-    messages carry structural indices / counts only — `build834`
+    messages carry structural indices / counts only. `build834`
     additionally names the offending maintenance code (an X12 control
     code, never PHI), but never a member id or name (PHI discipline).
   - New public exports: `build820`, `Premium820BuildError`,
@@ -212,11 +362,11 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
     `Build820Spec` type tree; `build834`, `Enrollment834BuildError`,
     `ENROLLMENT_834_BUILD_ERROR_CODES`, `Enrollment834BuildErrorCode`, and
     the `Build834Spec` type tree.
-- **Domain builders — `build278Request` (005010X217 Health Care Services
-  Review — Request for Review) and `build278Response` (005010X216 Services
-  Review — Response).** The emit counterparts to `get278Request` /
+- **Domain builders: `build278Request` (005010X217 Health Care Services
+  Review: Request for Review) and `build278Response` (005010X216 Services
+  Review: Response).** The emit counterparts to `get278Request` /
   `get278Response`, layered on the Phase 8 general builder and mirroring
-  the pure-function `build277` / `build277CA` pattern — they NEVER
+  the pure-function `build277` / `build277CA` pattern. They NEVER
   auto-send, open a socket, or touch the filesystem, and return a frozen
   `X12Interchange`.
   - **`build278Request(spec)` / `build278Response(spec)`** share one
@@ -234,7 +384,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
     surface.** `build278Response` places the caller-supplied HCR-01
     `actionCode` (`A1` certified / `A3` not-certified / `A4` pended / `A6`
     modified / …) into the segment VERBATIM and NEVER infers, normalizes,
-    or upgrades it — the round-tripped `decision.actionCode` is
+    or upgrades it. The round-tripped `decision.actionCode` is
     byte-for-byte the input. `build278Request` REFUSES a review carrying a
     decision (HCR is response-only); `build278Response` refuses a decision
     with an empty action code.
@@ -245,22 +395,22 @@ EV/SS`), and HL-04 has-child flag from the nested input tree, so an
     construction.
   - **Refusal, not silent corruption.** The builder REFUSES a
     structurally impossible spec via a typed `ServicesReview278BuildError`
-    (`X12_278_BUILD_INVALID_HIERARCHY` — a subscriber with neither a
+    (`X12_278_BUILD_INVALID_HIERARCHY`: a subscriber with neither a
     review nor a dependent, a dependent with no review;
-    `X12_278_BUILD_INVALID_SPEC` — a review with no request category code,
+    `X12_278_BUILD_INVALID_SPEC`: a review with no request category code,
     a request review carrying an HCR decision, a response decision with an
     empty action code, an over-long control number). The message carries
-    structural locators only (`subscriber.review[0]`, level codes) — never
+    structural locators only (`subscriber.review[0]`, level codes), never
     a member name, member id, trace, or diagnosis code (PHI discipline).
   - New public exports: `build278Request`, `build278Response`,
     `ServicesReview278BuildError`, `AUTH_278_BUILD_ERROR_CODES`,
     `ServicesReview278BuildErrorCode`, and the `Build278Spec` type tree.
-- **Domain builders — `build271` (005010X279A1 Eligibility Benefit
+- **Domain builders: `build271` (005010X279A1 Eligibility Benefit
   Response) and `build277` / `build277CA` (005010X212 Claim Status
   Response / 005010X214 Claim Acknowledgment).** The response-side emit
   counterparts to `get271Eligibility` / `get277Status` /
   `get277CADisposition`, layered on the Phase 8 general builder and
-  mirroring the pure-function `build835` / `build837` pattern — they
+  mirroring the pure-function `build835` / `build837` pattern. They
   NEVER auto-send, open a socket, or touch the filesystem, and return a
   frozen `X12Interchange`.
   - **`build271(spec)`** assembles a complete interchange (one GS..GE
@@ -277,7 +427,7 @@ EV/SS`), and HL-04 has-child flag from the nested input tree, so an
     through `parseX12` so a well-formed spec is reproduced field-for-field.
   - **TRN echo is the safety-critical reassociation invariant.** The
     builder places the caller-supplied trace into TRN-02 verbatim and
-    NEVER fabricates, normalizes, or mutates it — a build-side property
+    NEVER fabricates, normalizes, or mutates it. A build-side property
     test feeds random trace tokens through all three builders and asserts
     the round-tripped `referenceId` is byte-for-byte the input.
   - **The HL spine is computed, never caller-supplied.** The builder
@@ -287,26 +437,26 @@ EV/SS`), and HL-04 has-child flag from the nested input tree, so an
     hierarchy is unrepresentable and SE-01 is correct by construction.
   - **Refusal, not silent corruption.** The builder REFUSES a
     structurally impossible spec via a typed `Eligibility271BuildError`
-    (`X12_271_BUILD_INVALID_HIERARCHY` — no source / a childless source /
-    a childless receiver; `X12_271_BUILD_INVALID_SPEC` — over-long control
+    (`X12_271_BUILD_INVALID_HIERARCHY`: no source / a childless source /
+    a childless receiver; `X12_271_BUILD_INVALID_SPEC`: over-long control
     number) or `ClaimStatus277BuildError`
-    (`X12_277_BUILD_INVALID_HIERARCHY` — no source / a childless source /
+    (`X12_277_BUILD_INVALID_HIERARCHY`: no source / a childless source /
     receiver / provider / a subscriber with neither claim nor dependent /
-    a childless dependent; `X12_277_BUILD_INVALID_SPEC` — a claim with no
+    a childless dependent; `X12_277_BUILD_INVALID_SPEC`: a claim with no
     trace / status / service line, an STC with no category code, an
     over-long control number). The message carries structural locators
     only (`source[0].receiver[0].provider[0].subscriber[0]`, level codes,
-    counts) — never a member name, member id, or trace (PHI discipline).
+    counts), never a member name, member id, or trace (PHI discipline).
   - New public exports: `build271`, `Eligibility271BuildError`,
     `ELIGIBILITY_271_BUILD_ERROR_CODES`, `Eligibility271BuildErrorCode`,
     the `Build271Spec` type tree; `build277`, `build277CA`,
     `ClaimStatus277BuildError`, `CLAIM_STATUS_277_BUILD_ERROR_CODES`,
     `ClaimStatus277BuildErrorCode`, and the `Build277Spec` type tree.
-- **Domain builders — `build837P` / `build837I` / `build837D` (005010
+- **Domain builders: `build837P` / `build837I` / `build837D` (005010
   837 Health Care Claim: Professional `X222A2`, Institutional `X223A3`,
   Dental `X224A2`).** The claim-submission emit counterpart to
   `get837Claims`, layered on the Phase 8 general builder and mirroring
-  the pure-function `build835` pattern — they NEVER auto-send, open a
+  the pure-function `build835` pattern. They NEVER auto-send, open a
   socket, or touch the filesystem.
   - **`build837P/I/D(spec)`** each assemble a complete `X12Interchange`
     (one GS..GE group, GS-01 `HC`; one ST..SE 837, ST-03 per variant)
@@ -334,17 +484,17 @@ EV/SS`), and HL-04 has-child flag from the nested input tree, so an
     line whose `variant` mismatches the builder, an empty procedure /
     revenue code, an over-long control number). The message carries
     structural locators only (`billing[0].subscriber[0].claim[0]`, level
-    codes, counts) — never the `claimId` or a member id (PHI discipline).
+    codes, counts), never the `claimId` or a member id (PHI discipline).
   - New public exports: `build837P`, `build837I`, `build837D`,
     `Claim837BuildError`, `CLAIM_837_BUILD_ERROR_CODES`,
     `Claim837BuildErrorCode`, and the `Build837Spec` type tree.
   - Known limitation: claim-/line-level provider addresses (Loop
-    2310/2420 N3/N4) are a documented read-side limitation — the NM1
+    2310/2420 N3/N4) are a documented read-side limitation: the NM1
     fields round-trip, the address does not.
-- **Domain builder — `build835` (005010X221A1 ERA).** The first
+- **Domain builder: `build835` (005010X221A1 ERA).** The first
   per-transaction emit helper layers the safety-critical TR3 invariants
   on top of the Phase 8 general builder, mirroring the pure-function
-  `build999` / `buildTA1` pattern — it NEVER auto-sends, opens a socket,
+  `build999` / `buildTA1` pattern. It NEVER auto-sends, opens a socket,
   or touches the filesystem.
   - **`build835(spec)`** assembles a complete `X12Interchange` (one
     GS..GE group, GS-01 `HP`; one ST..SE 835, ST-03 `005010X221A1`) from
@@ -354,7 +504,7 @@ EV/SS`), and HL-04 has-child flag from the nested input tree, so an
     claims → Loop 2110 service lines → PLB) and the output round-trips
     through `parseX12` so a balanced spec is reproduced by `get835`
     field-for-field. Composites (CLP-08, SVC-01, SVC-06, PLB) escape
-    each component then join with the raw component separator — the
+    each component then join with the raw component separator. The
     envelope is emitted inline (not via `buildInterchange`) to avoid
     double-escaping a pre-composed element. Same-group CAS and
     same-provider/period PLB adjustments pack into one segment (≤ 6
@@ -366,10 +516,10 @@ EV/SS`), and HL-04 has-child flag from the nested input tree, so an
     (`checkServiceLineBalance` / `checkClaimBalance` /
     `checkRemitTotalBalance`) against a materialized read model so emit
     guard and parse warning share one source of truth. Codes:
-    `X12_835_BUILD_BALANCE_MISMATCH` (any §1.10.2 invariant — line,
+    `X12_835_BUILD_BALANCE_MISMATCH` (any §1.10.2 invariant: line,
     claim, or top-of-remit) and `X12_835_BUILD_INVALID_SPEC` (no TRN
     trace, an empty CLP-01, an over-long ISA-13). The thrown message
-    carries numeric totals only — never a patient-control number or
+    carries numeric totals only, never a patient-control number or
     member id (PHI discipline).
   - **New exports.** `build835`, `Remit835BuildError`,
     `REMIT_835_BUILD_ERROR_CODES`, `Remit835BuildErrorCode`, and the
@@ -383,14 +533,14 @@ EV/SS`), and HL-04 has-child flag from the nested input tree, so an
     `build820` / `build834`) layer on the same general surface and are
     NOT in this change.
 
-- **Phase 8 — spec-clean serializer + general interchange builder (the
+- **Phase 8: spec-clean serializer + general interchange builder (the
   emit half lands).** Two new public surfaces close the read↔write loop.
   - **`serializeX12(interchange, opts?)`** turns any parsed
     `X12Interchange` back into an X12 byte stream. Default mode is
-    byte-faithful — reconstructed purely from the verbatim `.raw`
+    byte-faithful: reconstructed purely from the verbatim `.raw`
     strings the parser preserved (ISA + terminator, then each
     TA1 / GS / segment / GE / IEA terminator-joined, then any
-    `trailingBytes`) — so for a Tier-1 input it reproduces the source
+    `trailingBytes`), so for a Tier-1 input it reproduces the source
     bytes exactly: the idempotency fixed point
     `serialize(parse(s)) === s`. With `{ specClean: true }` it ALSO
     reconciles the envelope (SE-01 / GE-01 / IEA-01 counts + the
@@ -406,7 +556,7 @@ EV/SS`), and HL-04 has-child flag from the nested input tree, so an
     body values via the `?` release char, and round-trips its output
     back through `parseX12` so the returned interchange is bit-identical
     to the parsed form. Structurally impossible specs are REFUSED with a
-    typed `X12BuildError` (`X12_BUILD_INVALID_SPEC`) — an over-long
+    typed `X12BuildError` (`X12_BUILD_INVALID_SPEC`): an over-long
     ISA-13, a body segment with no id.
   - **New warning + exports.** `X12_SEGMENT_COUNT_MISMATCH` is a
     serializer-only diagnostic (the parser never validated SE-01);
@@ -428,14 +578,14 @@ EV/SS`), and HL-04 has-child flag from the nested input tree, so an
     validated (it checks GE-01 / IEA-01 / control pairs but not SE-01):
     SE-01 miscounts in `837i-canonical` (30→33), `837d-canonical`
     (25→26), `999-accept` (5→6), and a GS-06/GE-02 mismatch in
-    `278-response` (GS-06 2→1) — an accuracy-gate win.
+    `278-response` (GS-06 2→1), an accuracy-gate win.
   - **Known limitation (deferred).** Domain per-transaction builders
     (`build835` / `build837P/I/D` / `build271` / …, the safety-critical
     emit code enforcing per-TR3 balance + certification invariants) are
     NOT in this phase; the general envelope surface they layer on top of
     is.
 
-- **Phase 7 — 278 services review + 834 enrollment + 820 premium
+- **Phase 7: 278 services review + 834 enrollment + 820 premium
   payment (the v1 transaction scope rounds out).** Four new read-side
   helpers: `get278Request` / `get278Response` (TR3 `005010X217` /
   `005010X216`), `get820Payments` (TR3 `005010X218`), and the streaming
@@ -444,13 +594,13 @@ EV/SS`), and HL-04 has-child flag from the nested input tree, so an
     278 response `HCR-01` certification action (certified /
     not-certified / pended / modified) is captured as-is on each event /
     service review; the 834 `INS-03` / `HD-01` maintenance type (X12 0875) is preserved and an unknown code raises
-    `X12_834_UNKNOWN_MAINTENANCE_TYPE` on the affected member only — no
+    `X12_834_UNKNOWN_MAINTENANCE_TYPE` on the affected member only. No
     action is ever synthesized.
   - **834 streaming.** `get834Enrollments` is an
     `AsyncIterable<X12Enrollment>` yielding one member per `INS` loop;
     a streaming property test drives a 10MB+ synthetic roster with
     early-break. (Honest limitation: v1 still parses into `tx.segments`
-    up front — a true file→iterator source is a v2 item.)
+    up front. A true file→iterator source is a v2 item.)
   - **278 HL spine** `20 → 21 → 22 → 23` validated via the shared
     `validateHl`; the `EV` / `SS` event + service levels are
     deliberately tolerant (omitted from the expected-parent map).
@@ -466,7 +616,7 @@ EV/SS`), and HL-04 has-child flag from the nested input tree, so an
     (H-PHI invariant). Synthetic fixtures across all three surfaces,
     unit tests, and the 834 streaming property. Serialization is
     Phase 8.
-- **PHI commit-gate — a zero-dependency, X12-shape-aware PHI scanner
+- **PHI commit-gate: a zero-dependency, X12-shape-aware PHI scanner
   (`scripts/phi-scan.ts`, run via `pnpm phi-scan`).** Guards the
   synthetic fixture corpus: it refuses any test fixture or `src/` file
   carrying real-PHI-shaped tokens so a developer cannot commit a
@@ -476,7 +626,7 @@ EV/SS`), and HL-04 has-child flag from the nested input tree, so an
   `scripts/verify.sh` summary from `phi-scan SKIP` to `phi-scan ✓`.
   - **Synthetic allow-list, not an inline header.** X12 `.edi` is
     byte-strict (ISA must start at byte 0), so an inline
-    `# synthetic: true` marker is impossible — it would break every
+    `# synthetic: true` marker is impossible. It would break every
     parser test. Same constraint DICOM hits with binary `.dcm`, so the
     same proven solution: `scripts/phi-allow-list.txt` positively
     declares which names / dates-of-birth / ids / email-domains are
@@ -491,17 +641,17 @@ EV/SS`), and HL-04 has-child flag from the nested input tree, so an
   - **Audited bypass.** A whole-file `--allow-fixture <path>` is
     rejected unless `phi-scan-overrides.md` carries a matching
     `### <path>` entry, so a silenced file is always a recorded act.
-    Every subprocess is `git` via `execFileSync` array args — no shell
+    Every subprocess is `git` via `execFileSync` array args, no shell
     form. Unit tests cover the clean interchange, each violator class,
     the plain-text pass, and both arms of the override gate.
 
-- **Phase 6 — 271 Eligibility Benefit Response + 277 / 277CA Claim
-  Status — TR3s `005010X279A1` (270/271), `005010X212` (276/277),
+- **Phase 6: 271 Eligibility Benefit Response + 277 / 277CA Claim
+  Status, TR3s `005010X279A1` (270/271), `005010X212` (276/277),
   `005010X214` (277CA).** Three new public walkers:
   `get271Eligibility(delimiters, tx)`, `get277Status(delimiters, tx)`,
   and `get277CADisposition(delimiters, tx)`. 277 and 277CA share one
   internal walk disambiguated by the `ST-03` implementation-convention
-  reference — `get277CADisposition` admits only `005010X214`;
+  reference: `get277CADisposition` admits only `005010X214`;
   `get277Status` admits either. Each returns `undefined` only on a
   mis-routed call (wrong `ST-01`); every recoverable deviation is a
   warning, never a throw.
@@ -509,7 +659,7 @@ EV/SS`), and HL-04 has-child flag from the nested input tree, so an
     requesting 270's `TRN-02` trace verbatim onto its enclosing
     subscriber / dependent, and a 277 echoes the 276's onto its claim,
     so the provider can re-associate the answer with the request it
-    sent — the walkers NEVER mutate, normalize, or drop the trace. A
+    sent. The walkers NEVER mutate, normalize, or drop the trace. A
     round-trip property test asserts byte-for-byte echo across an
     arbitrary trace grammar.
   - **Status-code fidelity (277 family).** Each STC composite
@@ -521,7 +671,7 @@ EV/SS`), and HL-04 has-child flag from the nested input tree, so an
     `X12_UNKNOWN_CLAIM_STATUS`. A 277CA provider-level batch
     acknowledgment opens a claim on a standalone STC (no TRN).
   - **HL parent-pointer integrity.** Enforced through the shared
-    `validateHl` primitive — 271 spine `20 → 21 → 22 → 23`; 277 / 277CA
+    `validateHl` primitive: 271 spine `20 → 21 → 22 → 23`; 277 / 277CA
     spine `20 → 21 → 19 → 22 → 23`. A dangling or mis-levelled parent
     emits `X12_HL_PARENT_MISMATCH` / `X12_HL_PARENT_LEVEL_INVALID`; the
     walker NEVER silently re-numbers and the verbatim declared parent id
@@ -545,16 +695,16 @@ EV/SS`), and HL-04 has-child flag from the nested input tree, so an
     HSD detail, and III / LS / LE markers in the 271, plus QTY / AMT
     claim-summary roll-ups in a 277CA Loop 2200, are preserved on
     `tx.segments` verbatim but not yet typed onto the model.
-- **Phase 5 — 837 Healthcare Claim — TR3s `005010X222A2` (Professional),
+- **Phase 5: 837 Healthcare Claim, TR3s `005010X222A2` (Professional),
   `005010X223A3` (Institutional), `005010X224A2` (Dental).** The
-  claim-creation surface — the volume side of HIPAA EDI traffic.
+  claim-creation surface: the volume side of HIPAA EDI traffic.
   `get837Claims(delimiters, tx, opts?)` walks a parsed 837 transaction
   set into the typed `X12_837Submission` model: variant detection (from
   ST-03 implementation-convention reference, falling back to SVx
   segment id, then to `"unknown"` with `X12_837_UNKNOWN_VARIANT`),
   submitter (Loop 1000A NM1\*41) + receiver (Loop 1000B NM1\*40), the
   full HL hierarchy (Loops 2000A / 2000B / 2000C), every claim header
-  (Loop 2300 — CLM with patient account number, total charge,
+  (Loop 2300: CLM with patient account number, total charge,
   composite POS / facility-code-qualifier / claim-frequency-code,
   signature / assignment / benefits / release-of-information
   indicators), and every service line typed by variant (`SV1` →
@@ -562,18 +712,18 @@ EV/SS`), and HL-04 has-child flag from the nested input tree, so an
   - **HL parent-pointer integrity.** The 837 family's safety primitive
     is the HL hierarchy (`HL-01` own id, `HL-02` parent id, `HL-03`
     level code: `20` Information Source / `22` Subscriber / `23`
-    Dependent). An off-by-one in `HL-02` is THE #1 837 bug — the
+    Dependent). An off-by-one in `HL-02` is THE #1 837 bug. The
     walker validates that every non-top-level HL's `HL-02` references
     an earlier-emitted `HL-01` AND that the parent's level matches the
     TR3-required parent for this level (`22` → parent `20`; `23` →
     parent `22`). Violations emit `X12_HL_PARENT_MISMATCH` or
-    `X12_HL_PARENT_LEVEL_INVALID` — the parser NEVER silently
+    `X12_HL_PARENT_LEVEL_INVALID`. The parser NEVER silently
     re-numbers. The verbatim declared parent id stays on the
     `X12HierarchicalLevel` entry.
   - **HI qualifier → code-system provenance.** `HI` carries
     diagnoses, principal procedures, external cause of injury,
     condition codes, occurrence codes, value codes, and DRG / PR
-    groupings under one segment id — with the qualifier (first
+    groupings under one segment id, with the qualifier (first
     component) governing the code system. The new
     `src/code-lists/hi-qualifiers.ts` ships a frozen `HI_QUALIFIERS`
     registry covering the qualifiers cited across the three TR3s
@@ -605,16 +755,16 @@ EV/SS`), and HL-04 has-child flag from the nested input tree, so an
     re-parsing the literal.
   - **Variant-specific service-line types.** The
     {@link X12_837ServiceLine} discriminated union holds three shapes:
-    - `X12_837ServiceLineProfessional` — `procedureQualifier` /
+    - `X12_837ServiceLineProfessional`: `procedureQualifier` /
       `procedureCode` / `modifiers` from SV1-01 composite; 1-4
       `diagnosisPointers` from SV1-07; emergency / EPSDT / family-
       planning indicators; optional `drug` (Loop 2410 LIN + CTP NDC +
       UCUM unit).
-    - `X12_837ServiceLineInstitutional` — `revenueCode` (NUBC 4-digit
+    - `X12_837ServiceLineInstitutional`: `revenueCode` (NUBC 4-digit
       from SV2-01); optional procedure / modifiers from SV2-02
       composite; `serviceLineRate` (SV2-06); `nonCoveredCharge`
       (SV2-07).
-    - `X12_837ServiceLineDental` — ADA CDT `procedureCode` from
+    - `X12_837ServiceLineDental`: ADA CDT `procedureCode` from
       SV3-01; `oralCavityArea` composite from SV3-04; per-line
       `toothInformation` from `TOO*JP` (Universal Tooth Numbering)
       with surface codes from TOO-03's composite components;
@@ -623,7 +773,7 @@ EV/SS`), and HL-04 has-child flag from the nested input tree, so an
     `serviceLine.adjudications` as `X12LineAdjudication[]`. Each
     adjudication ships the other-payer id (SVD-01), amount paid as
     `X12Decimal` (SVD-02), the other payer's procedure code, paid
-    units, and any CAS adjustments — re-using `X12RemitAdjustment` /
+    units, and any CAS adjustments, re-using `X12RemitAdjustment` /
     `lookupCarc` from the 835 helper since CAS semantics are
     identical.
   - **Loop 2320 Other Subscriber (COB).** Captured at the surface
@@ -631,9 +781,9 @@ EV/SS`), and HL-04 has-child flag from the nested input tree, so an
     individual relationship, claim filing indicator, and the
     other-subscriber + other-payer NM1 entities. Detailed CAS / OI /
     MOA breakdown inside Loop 2320 is deferred to Phase 9 (companion-
-    guide tolerance) — verbatim segments remain on `tx.segments`.
+    guide tolerance). Verbatim segments remain on `tx.segments`.
   - **Eleven dogfooded `LoopSpec` artifacts** ship through the public
-    `defineLoopSpec()` API — the dogfooding gate locked in Phase 2.
+    `defineLoopSpec()` API, the dogfooding gate locked in Phase 2.
     `CLAIM_837_LOOP_1000A` / `_1000B` (submitter / receiver),
     `CLAIM_837_LOOP_2010AA` (billing provider name), `_2010BA`
     (subscriber name), `_2010BB` (payer name), `_2010CA` (patient
@@ -642,7 +792,7 @@ EV/SS`), and HL-04 has-child flag from the nested input tree, so an
     `CLAIM_837{P,I,D}_LOOP_2000A` / `_2300` / `_2400` trees.
   - **Bundled HI qualifier registry under
     `src/code-lists/hi-qualifiers.ts`** alongside the existing CARC /
-    RARC / CLP_STATUS / CAGC snapshots — formally part of the
+    RARC / CLP_STATUS / CAGC snapshots, formally part of the
     code-list family, not a transaction-local table.
   - **Two new exported constants for safety + ergonomics:**
     `HL_LEVEL_CODES` (`INFORMATION_SOURCE` `"20"` / `INFORMATION_RECEIVER`
@@ -650,21 +800,21 @@ EV/SS`), and HL-04 has-child flag from the nested input tree, so an
     `NM1_QUALIFIERS` (`SUBMITTER` `"41"` / `RECEIVER` `"40"` /
     `BILLING_PROVIDER` `"85"` / `PAY_TO_ADDRESS` `"87"` /
     `PAY_TO_PLAN` `"PE"` / `SUBSCRIBER` `"IL"` / `PAYER` `"PR"` /
-    `PATIENT` `"QC"`) — so the walker (and any consumer Phase 8
+    `PATIENT` `"QC"`), so the walker (and any consumer Phase 8
     builder) never has to magic-string the safety-critical
     discriminators.
-  - **Six new shared element-read helpers in `parser/segment.ts`** —
+  - **Six new shared element-read helpers in `parser/segment.ts`**:
     `elementValue` / `elementOptional` / `componentOptional` /
-    `elementDecimal` / `elementDecimalOrZero` / `collectElementValues`
-    — extracted out of the 835 and 837 walkers (both walkers had
+    `elementDecimal` / `elementDecimalOrZero` / `collectElementValues`,
+    extracted out of the 835 and 837 walkers (both walkers had
     byte-identical copies). New transaction walkers (Phase 6+ 270/271,
-    277, 834) inherit them. Public surface — exported via
+    277, 834) inherit them. Public surface: exported via
     `@cosyte/x12`.
   - **Public-surface additions** to the warning stability snapshot:
     `X12_HL_PARENT_MISMATCH`, `X12_HL_PARENT_LEVEL_INVALID`,
     `X12_UNKNOWN_HI_QUALIFIER`, `X12_MISSING_REQUIRED_LOOP`,
-    `X12_837_UNKNOWN_VARIANT` (13 → 18 Tier-2 codes; additions-only
-    — fatal registry stays at 4). All new warning factories
+    `X12_837_UNKNOWN_VARIANT` (13 → 18 Tier-2 codes; additions-only,
+    fatal registry stays at 4). All new warning factories
     (`hlParentMismatch` / `hlParentLevelInvalid` /
     `unknownHiQualifier` / `missingRequiredLoop` /
     `unknown837Variant`) shape-validate echoed values through
@@ -672,11 +822,11 @@ EV/SS`), and HL-04 has-child flag from the nested input tree, so an
     `/^[0-9]{2}$/u` for level codes, `/^[A-Z][A-Z0-9]{1,2}$/u` for HI
     qualifiers, `/^[0-9A-Z]{3,6}$/u` for loop ids,
     `/^[0-9A-Z]{3,16}$/u` for ICR) and substitute `(non-spec)` for
-    hostile inputs — the H-PHI invariant from `@cosyte/hl7`.
+    hostile inputs, the H-PHI invariant from `@cosyte/hl7`.
   - **PHI discipline.** Warnings NEVER echo field VALUES; the
     `missingRequiredLoop` rationale strings are hard-coded literals
     (no element interpolation). Patient names / member IDs / NPIs /
-    claim numbers are surfaced verbatim on the typed model only — the
+    claim numbers are surfaced verbatim on the typed model only, the
     documented consumer-redaction boundary (mirrors hl7 + the 835
     helper). The `X12ClaimNote` JSDoc explicitly flags NTE-02 as
     PHI-bearing (provider-supplied free text). Every Phase 5 fixture
@@ -685,10 +835,10 @@ CHILD`; sequential member IDs `MEMBER001`–`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
-    silent — verbatim segments remain on `tx.segments` for raw
+    silent, verbatim segments remain on `tx.segments` for raw
     access):
     - Loop 2320/2330 Other Subscriber / Other Payer captured at the
-      surface level only — detailed CAS / OI / MOA inside Loop 2320
+      surface level only. Detailed CAS / OI / MOA inside Loop 2320
       deferred to Phase 9 (companion-guide profile system).
     - Loop 2420 service-line provider names captured verbatim on
       `serviceLine.providers`; per-provider PRV + address not yet
@@ -723,7 +873,7 @@ CHILD`; sequential member IDs `MEMBER001`–`MEMBER011` etc.; NPI-
     coverage (96.91% stmts / 90.61% branches / 97.67% funcs / 98.49%
     lines globally; per-dir ≥90 on `parser/` + `loops/` +
     `transactions/` + `code-lists/`) + build + attw + verify:exports.
-  - **`phi-scan` SKIP** — unchanged from Phase 4. The runtime H-PHI
+  - **`phi-scan` SKIP**, unchanged from Phase 4. The runtime H-PHI
     invariant is necessary but not sufficient; static fixture
     scanning is tracked as the `X12-PHI-SCAN` backlog follow-up.
 
@@ -733,7 +883,7 @@ CHILD`; sequential member IDs `MEMBER001`–`MEMBER011` etc.; NPI-
   `elementValue` / `elementOptional` / `componentOptional` /
   `elementDecimal` / `elementDecimalOrZero` / `collectElementValues`.
   Re-used by the 835 helper (`get835`) and the new 837 helper
-  (`get837Claims`) — both walkers previously defined byte-identical
+  (`get837Claims`). Both walkers previously defined byte-identical
   copies of these inline. Additive; no breaking change.
 
 - **`src/code-lists/` gains `hi-qualifiers.ts`** with `HI_QUALIFIERS`
@@ -741,26 +891,26 @@ CHILD`; sequential member IDs `MEMBER001`–`MEMBER011` etc.; NPI-
   `isProcedureQualifier` and the `X12HiCategory` / `X12HiCodeSystem`
   / `X12HiQualifier` types. Re-exported from `@cosyte/x12` root.
 
-- **Phase 4 — 835 Healthcare Claim Payment/Advice (ERA) — TR3
-  `005010X221A1`.** The cash-posting surface — money, the consultant ask.
+- **Phase 4: 835 Healthcare Claim Payment/Advice (ERA), TR3
+  `005010X221A1`.** The cash-posting surface: money, the consultant ask.
   `get835(delimiters, tx)` walks a parsed 835 transaction set into the
   typed `X12Remittance` model: payment header (BPR), trace numbers (TRN),
   payer / payee parties (Loops 1000A / 1000B with address / contact /
-  additional identifiers), every claim payment (Loop 2100 — CLP plus
+  additional identifiers), every claim payment (Loop 2100: CLP plus
   patient / subscriber / service-provider NM1s, statement-period DTMs,
   CAS adjustments at both claim and service-line scope, MIA / MOA / LQ
   remarks, REF / AMT supplemental amounts), every service line (Loop
-  2110 — SVC with HCPCS / CPT / NDC / revenue-code / modifier
+  2110: SVC with HCPCS / CPT / NDC / revenue-code / modifier
   destructuring, service-date DTMs, line-level CAS / REF / AMT / LQ),
   and provider-level adjustments (PLB with multi-pair flattening). The
   loop hierarchy ships as three frozen `LoopSpec` artifacts
   (`REMIT_835_LOOP_2000`, `REMIT_835_LOOP_2100`, `REMIT_835_LOOP_2110`)
-  authored through the public `defineLoopSpec()` API — the **dogfooding
+  authored through the public `defineLoopSpec()` API, the **dogfooding
   gate** locked in Phase 2. Two payer-side loop specs (1000A / 1000B)
   also ship as introspection artifacts.
   - **Money discipline.** All monetary fields decode as the new
     `X12Decimal` (`src/decimal.ts`): a string-backed decimal type with
-    `BigInt`-exact arithmetic. **NEVER `parseFloat`** — float
+    `BigInt`-exact arithmetic. **NEVER `parseFloat`**: float
     representation silently destroys cents at scale; on an 835 a dropped
     decimal is the wrong dollar amount in someone's cash post.
     `X12Decimal` preserves the inbound lexical form for byte-exact
@@ -771,29 +921,29 @@ CHILD`; sequential member IDs `MEMBER001`–`MEMBER011` etc.; NPI-
     `toNumber()` whose JSDoc warns about precision loss. `fromBigInt(value,
 scale)` renders canonically with zero-padded fractions; the canonical
     `X12Decimal.ZERO` is the additive identity. Empty inbound element →
-    `undefined` (not zero) — "not supplied" and "zero dollars" are
+    `undefined` (not zero): "not supplied" and "zero dollars" are
     spec-distinct.
-  - **Balance invariants (per TR3 X221A1 §1.10.2 — "Balancing the 835").**
+  - **Balance invariants (per TR3 X221A1 §1.10.2: "Balancing the 835").**
     Three checks run after the walk and emit
-    `X12_835_REMIT_BALANCE_MISMATCH` on mismatch — the model is **NEVER
+    `X12_835_REMIT_BALANCE_MISMATCH` on mismatch. The model is **NEVER
     silently rebalanced**: 1. Line: `SVC-02 === SVC-03 + Σ(line CAS)` per Loop 2110. 2. Claim: `CLP-03 === CLP-04 + Σ(all CAS in claim, claim AND line
-level)` — the X12 spec balance. CLP-05 (patient responsibility)
+level)`, the X12 spec balance. CLP-05 (patient responsibility)
     is informational, NOT part of the balance equation. The
     implementation matches the TR3 §1.10.2 text directly; an earlier
     roadmap sketch (`operations/roadmaps/x12.md` §4) used a slightly
-    different decomposition — `src/transactions/remit/balance.ts`
+    different decomposition. `src/transactions/remit/balance.ts`
     documents the divergence so the contract stays consistent. 3. Top-of-remit: `BPR-02 === Σ(CLP-04) - Σ(PLB amounts)`. PLB
     amounts are stored with the **raw EDI sign** (positive = take-back
     from provider; negative = credit to provider), so the equation
     _subtracts_ PLB to balance.
     Warning messages echo only the invariant label and `X12Decimal`
-    decimal text — never patient identifiers, member ids, or account
+    decimal text, never patient identifiers, member ids, or account
     numbers (H-PHI invariant).
   - **CAS triple flattening.** A single CAS segment can carry up to 6
     `(reason, amount, quantity)` triples under one `CAS-01` group code;
     the walker flattens them into individual `X12RemitAdjustment`
     entries. Different group codes (CO / PR / OA / PI) require separate
-    CAS segments — they cannot mix inside one — and the decoder honors
+    CAS segments (they cannot mix inside one) and the decoder honors
     that contract.
   - **Bundled WPC + X12-internal code-list snapshots** (initial
     subsets, pre-launch). Versioned data artifacts at
@@ -805,24 +955,24 @@ level)` — the X12 spec balance. CLP-05 (patient responsibility)
     `lookupRarc(code)` / `lookupClpStatus(code)` return `{ code,
 description }` for known codes, `undefined` otherwise; unknown
     codes preserve the verbatim value on the parsed adjustment AND
-    emit `X12_UNKNOWN_CARC` / `X12_UNKNOWN_RARC`. - `CARC` (Claim Adjustment Reason Codes) — ~30 most commonly
-    observed codes (WPC, snapshotDate 2026-06-27). - `RARC` (Remittance Advice Remark Codes) — ~15 most commonly
+    emit `X12_UNKNOWN_CARC` / `X12_UNKNOWN_RARC`. - `CARC` (Claim Adjustment Reason Codes): ~30 most commonly
+    observed codes (WPC, snapshotDate 2026-06-27). - `RARC` (Remittance Advice Remark Codes): ~15 most commonly
     observed codes covering both `M`- and `N`-prefix conventions
-    (WPC, snapshotDate 2026-06-27). - `CLP_STATUS` (CLP-02 Claim Status Code, X12 Code Source 65) —
+    (WPC, snapshotDate 2026-06-27). - `CLP_STATUS` (CLP-02 Claim Status Code, X12 Code Source 65):
     10 dispositions (1 Processed as Primary, 4 Denied, 22 Reversal,
-    …). X12-internal list, stable. - `CLAIM_ADJUSTMENT_GROUP_CODES` — the spec-fixed 4 values
+    …). X12-internal list, stable. - `CLAIM_ADJUSTMENT_GROUP_CODES`: the spec-fixed 4 values
     (`CO` / `PR` / `OA` / `PI`) as a frozen literal-union map,
     not a snapshot (this list never grows). `isClaimAdjustmentGroupCode`
     narrows inbound strings.
   - **Public-surface additions** to the warning / fatal stability
     snapshot: `X12_835_REMIT_BALANCE_MISMATCH`,
     `X12_UNKNOWN_CARC`, `X12_UNKNOWN_RARC` (10 → 13 Tier-2 codes;
-    additions-only — fatal registry stays at 4). New warning factories
+    additions-only, fatal registry stays at 4). New warning factories
     `remitBalanceMismatch` / `unknownCarc` / `unknownRarc` carry the
     shape-validated echo discipline (CARC / RARC echoes pass
     `/^[A-Z0-9]{1,5}$/u` or collapse to `(non-spec)`).
   - **PHI discipline (H-PHI invariant holds suite-wide).** Warning
-    messages never echo field VALUES — only positional context, the
+    messages never echo field VALUES, only positional context, the
     invariant label, the shape-validated CARC / RARC code, or numeric
     X12Decimal text. Patient names, member ids, NPIs, payer claim
     control numbers, and account numbers are held verbatim on the
@@ -834,7 +984,7 @@ description }` for known codes, `undefined` otherwise; unknown
     synthetic spec-clean (`835-medicare-canonical.edi`,
     `835-multi-claim.edi`, `835-with-plb.edi`,
     `835-carc-rarc-mix.edi`, `835-imbalance.edi`) and one Tier-2
-    synthetic quirk shape (`835-availity-quirk.edi` — REF*2U + REF*F8
+    synthetic quirk shape (`835-availity-quirk.edi`: REF*2U + REF*F8
     placements). The imbalance fixture is deliberately off-by-$10 to
     prove the balance warning fires and the model preserves the
     verbatim amounts.
@@ -846,7 +996,7 @@ description }` for known codes, `undefined` otherwise; unknown
     the balance warning fires iff out of balance (100 + 50 runs).
     `remit-835-fuzz.property.test.ts` byte-flips every committed
     fixture 300 times per fixture and asserts `get835` never throws
-    outside the 4 Tier-3 fatals — the byte-level fuzz target the
+    outside the 4 Tier-3 fatals, the byte-level fuzz target the
     roadmap calls for.
   - **Coverage gates expanded** to per-directory ≥90 on `parser/`,
     `loops/`, `transactions/`, `code-lists/`. Phase 4 lands the gate
@@ -856,24 +1006,24 @@ description }` for known codes, `undefined` otherwise; unknown
     Code Source 65 for CLP-02; WPC public-domain lists for CARC / RARC;
     X12 Data Element 1033 for the Claim Adjustment Group Code.
   - **Known limitations after Phase 4:** no 835 _building_ yet (that's
-    Phase 8 — round-trip + spec-clean serializer + builder); the
+    Phase 8: round-trip + spec-clean serializer + builder); the
     bundled CARC / RARC are an **initial subset** (`pnpm
 refresh:code-lists` arrives in Phase 10); no per-payer profile
     yet (Phase 9); CPT / ICD-10 / NDC descriptions are deliberately
-    NOT bundled (license-gated — see `operations/roadmaps/x12.md` §5);
+    NOT bundled (license-gated, see `operations/roadmaps/x12.md` §5);
     `X12Decimal` does not yet expose multiply / divide (no balance
     invariant needs them in v1). `phi-scan` script not yet wired for
-    x12 — the H-PHI property tests provide runtime coverage; an
+    x12. The H-PHI property tests provide runtime coverage; an
     explicit pre-commit phi-scan ships in a future slice (tracked in
     `operations/prompts/x12-phi-scan.md`).
 
-- **Phase 3 — 999 + TA1 acknowledgments (TR3 005010X231A1).** Two
+- **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
   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.
-  - **999 (Implementation Acknowledgment) — TR3 005010X231A1.**
+  - **999 (Implementation Acknowledgment): TR3 005010X231A1.**
     `parse999(raw, opts?)` decodes the AK1 → AK2 → (IK3 [→ CTX] (IK4 [→
     CTX])\*)\* → IK5 → AK9 hierarchy into the typed `X12Ack999`. Standard
     X12 / pre-X231A1 legacy senders that emit `AK3`/`AK4`/`AK5` instead
@@ -882,15 +1032,15 @@ refresh:code-lists` arrives in Phase 10); no per-payer profile
     X231A1 names. `build999(spec)` assembles a complete `X12Interchange`
     wrapping a single ISA → GS → ST..SE → GE → IEA with one 999 inside,
     spec-clean and round-trippable through `parseX12`.
-  - **TA1 (Interchange Acknowledgment) — ASC X12 standard, envelope
+  - **TA1 (Interchange Acknowledgment): ASC X12 standard, envelope
     level.** The Phase 1 envelope walker now captures envelope-level
-    TA1 segments verbatim onto `X12Interchange.ta1Segments` — TA1
+    TA1 segments verbatim onto `X12Interchange.ta1Segments`. TA1
     between ISA and the first GS (the canonical position) is recognized
     as spec-conformant and NO `X12_UNEXPECTED_SEGMENT` warning fires;
     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`–`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
@@ -916,13 +1066,13 @@ refresh:code-lists` arrives in Phase 10); no per-payer profile
   - **PHI discipline (acks are structurally PHI-free by design):**
     Control numbers, segment IDs, position counters, and structural
     error codes ONLY. The one variable-shape surface that COULD carry
-    PHI — `IK4-04` (`copyOfBadDataElement`) — is documented on both the
+    PHI, `IK4-04` (`copyOfBadDataElement`), is documented on both the
     parsed-model type AND the build-spec type as a caller-supplied
     field that callers SHOULD omit when the offending bytes are PHI.
     The library NEVER auto-populates `IK4-04`. Error messages
     interpolate only control numbers, disposition codes, and count
     integers; no PHI-shape paths. The `phi-redaction-review` crew gate
-    passed at commit time; locked `999 — PHI safety` and `TA1 — PHI
+    passed at commit time; locked `999: PHI safety` and `TA1: PHI
 safety` test blocks assert no SSN / ISO-date / long-digit-run
     shapes appear in built output.
   - **Three Tier-1 999 fixtures** (`999-accept.edi`,
@@ -941,20 +1091,20 @@ safety` test blocks assert no SSN / ISO-date / long-digit-run
     `X12Interchange.ta1Segments: readonly Ta1Segment[]` (additive, no
     rename); no new entries to `WARNING_CODES` or `FATAL_CODES`
     (Phase 3 keeps both registries at the Phase-2-locked sizes of 10
-    and 4 — additions-only thereafter).
+    and 4, additions-only thereafter).
   - **Spec traceability:** TR3 `005010X231A1` (999); ASC X12 standard §
     TA1 Interchange Acknowledgment; code lists 715 / 716 / 723 / I13 / I18.
   - **Known limitations after Phase 3:** Acks reference STRUCTURAL
-    errors only — they cannot report semantic / payment errors (those
+    errors only. They cannot report semantic / payment errors (those
     live in `277CA` Phase 6 / `835` Phase 4). No multi-TA1 fan-out
     helper (consumers iterate `ta1Segments` directly when more than
     one inbound interchange is being acknowledged). The 999
     transaction-set surface does not yet expose a public Loop-spec
-    artifact — Phase 3 hand-walks the AK1/AK2/IK3/IK4/IK5/AK9 hierarchy
+    artifact. Phase 3 hand-walks the AK1/AK2/IK3/IK4/IK5/AK9 hierarchy
     in `parse-999.ts`; the dogfooding gate for `defineLoopSpec` lands
     fully with Phase 4's 835 + Phase 5's 837 work.
 
-- **Phase 2 — syntactic core: segment / element / composite / repetition
+- **Phase 2. Syntactic core: segment / element / composite / repetition
   decode + warning registry + `defineLoopSpec`.** Every body segment inside
   a transaction is now decoded into an immutable `X12Segment` carrying its
   id, raw text, and 1-indexed element array. The verbatim source survives
@@ -969,7 +1119,7 @@ safety` test blocks assert no SSN / ISO-date / long-digit-run
     trailing `?` is preserved verbatim AND warned as
     `X12_DANGLING_RELEASE_CHAR`; a `?` followed by a non-delimiter is
     preserved verbatim with no warning (Postel's Law).
-  - **Dot-path traversal** — `getSegmentValue(seg, "03-1")` resolves
+  - **Dot-path traversal**: `getSegmentValue(seg, "03-1")` resolves
     composite sub-element 1 of element 3 (both 1-indexed, matching TR3);
     `"03[2]"` resolves the 3rd repetition (0-indexed); `"03[2]-1"` combines
     them. Returns `undefined` for out-of-range paths, throws `TypeError`
@@ -979,14 +1129,14 @@ safety` test blocks assert no SSN / ISO-date / long-digit-run
     structural validation + a typed `LoopSpecDefinitionError`. Phase 3+
     transaction extractors author their built-in 999 / TA1 / 835 / 837
     loops through the SAME public API consumers use for payer-specific
-    loops — the dogfooding gate locked in `documentation/repos/x12.md`.
+    loops, the dogfooding gate locked in `documentation/repos/x12.md`.
   - **Warning registry expanded 8 → 10** (additions-only):
     `X12_DANGLING_RELEASE_CHAR` (unpaired `?` at element/segment end;
     bytes are preserved on the parent element) and
     `X12_UNEXPECTED_SEGMENT` (a `GE` with no open `GS`, `SE` with no open
-    `ST`, body segment outside any `ST..SE` — cases the Phase 1 walker
+    `ST`, body segment outside any `ST..SE`, cases the Phase 1 walker
     dropped silently). The PUBLIC `WARNING_CODES` snapshot test is the
-    breaking-change tripwire — renaming a code is breaking, additions
+    breaking-change tripwire: renaming a code is breaking, additions
     are not.
   - **PHI discipline (mirrors hl7's H-PHI invariant):**
     `X12_UNEXPECTED_SEGMENT` SHAPE-VALIDATES the echoed segment id
@@ -998,12 +1148,12 @@ safety` test blocks assert no SSN / ISO-date / long-digit-run
   - **Tier-1 fixture** (`syntactic-core-body.edi`) exercises every Phase 2
     surface end-to-end: composites (`HI*ABK:J45.50`), repetitions
     (`EQ*30^35^88`), `?`-release-character escape (`REF*EA*ID?*WITH?*STAR`),
-    and straight-element segments (BHT, NM1). Real-world synthetic — no
+    and straight-element segments (BHT, NM1). Real-world synthetic, no
     PHI. Parses with zero warnings.
   - **Properties:** release-escape round-trip (any value, any delimiters),
     escapeRelease output is fully decodable as `?<reserved>` pairs +
     non-reserved bytes (500 runs each), and a streaming-decode invariant
-    (parser output is independent of input chunking — locks the v2
+    (parser output is independent of input chunking, locks the v2
     streaming surface as a non-breaking future addition).
   - **`X12TransactionSet.segments` shape changed** from
     `readonly string[]` to `readonly X12Segment[]`; the raw form moves to
@@ -1011,10 +1161,10 @@ safety` test blocks assert no SSN / ISO-date / long-digit-run
     migrate.** Library-internal change; no impact on `ix.warnings`,
     `ix.delimiters`, or the envelope-level accessors.
 
-- **Phase 1 — envelope decoder.** `parseX12()` decodes the ISA / GS / GE / IEA
+- **Phase 1: envelope decoder.** `parseX12()` decodes the ISA / GS / GE / IEA
   interchange envelope from a raw `string` or `Buffer`, detecting all four
   delimiters (`element` byte 4, `repetition` ISA-11, `component` ISA-16,
-  `segment` post-ISA-16) from fixed positions inside the ISA itself — the parser
+  `segment` post-ISA-16) from fixed positions inside the ISA itself. The parser
   NEVER assumes a delimiter. Transaction-set bodies inside each ST..SE are kept
   opaque at this phase (raw segment strings, terminator stripped); Phase 2 adds
   segment / element / composite / repetition decode on top.
@@ -1028,8 +1178,8 @@ safety` test blocks assert no SSN / ISO-date / long-digit-run
   - `X12ParseError` carries `code`, `position` (interchange/group/transaction/
     segment/element indices), and a bounded `snippet` (≤ 64 chars) that is the
     documented consumer-redaction boundary. Warning messages NEVER echo field
-    values — they carry positional context plus bounded metadata (counts,
-    control-number pairs) — mirroring the hl7 H-PHI invariant.
+    values. They carry positional context plus bounded metadata (counts,
+    control-number pairs), mirroring the hl7 H-PHI invariant.
   - Strict mode (`parseX12(raw, { strict: true })`) escalates the first Tier-2
     warning into a thrown `X12ParseError` carrying the warning code.
   - 4 Tier-1 envelope fixtures committed under `test/fixtures/envelope/`
@@ -1042,7 +1192,7 @@ safety` test blocks assert no SSN / ISO-date / long-digit-run
 
 ### Changed
 
-- Inherits `@cosyte/test-utils` and `fast-check` as devDependencies — the
+- Inherits `@cosyte/test-utils` and `fast-check` as devDependencies. The
   conformance-kit runners (`lenientNeverThrowsProperty`) and the property/fuzz
   arbitraries land alongside the Phase 1 envelope code.