@cosyte/synth 0.0.7 → 0.0.9

package/CHANGELOG.md

@@ -1,16 +1,154 @@
 # Changelog
 
-All notable changes to this project will be documented in this file.
-
-The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
-and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
-Versions and publishing are managed with [Changesets](https://github.com/changesets/changesets);
-this file is maintained by hand (Changesets handles the version bump and publish only).
-
-## [Unreleased]
-
-The first pre-alpha release (`0.0.1`) will ship the initial public API surface. The package begins
-its public history at `0.0.x`, per the cosyte version ladder (`0.0.x` until first alpha).
+## 0.0.9
+
+### Patch Changes
+
+- b19fa4e: PHI scan: all-mode now reads every tracked file, not only the three scan roots, and a scan root of the wrong kind refuses instead of exiting 0 or 1.
+
+  On the base of this change, `pnpm phi-scan` read 176 of 225 tracked files: everything outside `src/`, `test/` and `scripts/` was opened by neither route, so `package.json`, `pnpm-lock.yaml`, every workflow and every root config file were scanned by nothing, and a repo-root file carrying a name, an SSN and an email exited 0 on both routes. All-mode now reconciles what it walked against `git ls-files` and reads every tracked file the walk did not reach: 198 of 225, with only markdown and the vendored archives left out, the archives named one literal path at a time.
+
+  The widening is a union with the walk and never a replacement of it, and the pre-commit route enumerates exactly what it always did: it still narrows to the three roots, deliberately, because the widening needs a corpus exemption and an exemption on the commit-blocking route is exactly what has subtracted a real detection elsewhere. One thing does change on every route, and it is stated rather than glossed: the publisher contact address in `package.json`, which the previous scope had never opened, is now declared in the allow-list, and an allow-list entry clears its value wherever it appears. That is one literal address, an organization's published contact rather than a person's, and the suite now pins both that it is cleared and that any other address at the same domain still fails.
+
+  Two walk-root defects close with it, both measured on this package rather than assumed from a sibling. A scan root that is a regular file threw `ENOTDIR` past the scanner's catch and exited 1, the code the contract reserves for "hits found"; a root symlinked at another root reported `OK, no hits` and exited 0 with the whole test corpus absent from disk. Both now refuse with 2, through an `lstat` on each root before the walk, because `existsSync` follows a link. The reconciliation also closes two states the per-root observation rule could not see: an absent directory inside a root, and a root emptied down to a single file, both of which used to report a clean sweep under a plausible denominator.
+
+  The one finding from reading the newly-opened files by hand was that publisher contact address, declared as an exact address rather than removed: it is the only email in any of them and there is no SSN shape in any of them.
+
+## 0.0.8
+
+### Patch Changes
+
+- c63e3f0: `CHANGELOG.md`, which ships inside the tarball, is now written by the release instead of by hand, so it stops describing already-published code as unreleased.
+
+  `.changeset/config.json` set `"changelog": false`, so no release ever wrote a version heading
+  into `CHANGELOG.md` and nothing ever rolled `[Unreleased]` over. Every published version of this
+  package therefore carried a changelog with **no version headings at all**: one `[Unreleased]`
+  heading over the whole history, and a preamble stating that the first pre-alpha release "will
+  ship" the initial public API surface listed below it. That promise was already in the future tense
+  in the very tarball that fulfilled it, and it stayed in the future tense through every release
+  after. `CHANGELOG.md` is listed in `package.json` `files`, so this was text on the disk of everyone
+  who installed the package, not internal bookkeeping.
+
+  **The flag is what changed, not the prose.** Correcting the sentence by hand would have left the
+  mechanism that wrote it in place, and the next release would have drifted the same way.
+  `changelog` now names the generator that ships with Changesets, so a release writes its own
+  version heading and its own entry from the changesets it consumed, and **the changeset summary is
+  now the changelog entry**. Nothing new is depended on: the generator is an entry point of
+  `@changesets/cli`, which was already a dev dependency.
+
+  **The file's shape changed with it, deliberately.** Changesets prepends a release by replacing the
+  first newline in the file, so exactly one line can sit above generated output. The hand-written
+  preamble sat on line 3, which means a release would have inserted itself between the heading and
+  the preamble and split the header in two. The hand-maintained history has therefore moved under a
+  `## Released before this file was generated` heading, with the false preamble replaced by an
+  accurate one. Three pieces of hand-workflow scaffolding were dropped and no entry was reworded:
+  the `[Unreleased]` heading, its link definition at the foot of the file, and the two empty section
+  stubs (`### Deprecated` and `### Removed`) waiting for the next hand-written entry. The history
+  itself is left as it was written rather than re-sorted into version sections, because the file
+  never recorded which release each entry went out in and the text is already on disk in published
+  copies.
+
+  **Changesets' Prettier pass is deliberately left ON here, and that was derived from this repo
+  rather than copied from a sibling.** This repo has no `.prettierignore` at all and its
+  `format:check` globs root markdown, so `CHANGELOG.md` is inside the repo's own formatting gate and
+  its archived history is already Prettier-canonical. Both directions were measured. With the pass
+  on, the archived history comes through a release byte identical, so leaving it on costs nothing.
+  With the pass off, what `changeset version` itself writes is no longer Prettier-canonical even for
+  the simplest possible summary, because it writes the version heading and `### Patch Changes` on
+  adjacent lines with no blank line between them. **A sentence a sibling carries is false here and
+  is deliberately not repeated**: this repo's `version` script also runs `prettier --write` over
+  `CHANGELOG.md` one link after `changeset version`, where a sibling's covers only `package.json`
+  and `src/index.ts`, so turning the pass off here would not open the Version PR red and would not
+  keep Prettier away from the archived history either. It would only leave the tool's own output
+  failing the gate that covers the file it wrote, which buys nothing. A sibling whose
+  `.prettierignore` lists `*.md` needs the opposite setting, and resyncing the value between repos is
+  how a release starts rewriting already-published text.
+
+  Pinned by `test/scripts/changelog-generation.test.ts`, which runs the real `changeset version`
+  against the real `CHANGELOG.md` and the real config in a throwaway package rather than
+  reimplementing where the tool inserts text. Nine of its fifteen cases are red against the previous
+  state, measured on the tree this change was written against rather than recalled. The throwaway
+  package is a real git repository, because the generator prefixes each entry with the short commit
+  sha that added the changeset and a tree with no history would exercise a line shape no release
+  writes. **The rule it enforces is that nothing but the H1 sits above the first heading, and it is
+  asserted on the released document as well as the committed one**: a rule phrased as "the archive
+  heading comes second" holds only until the first release writes its own version heading there,
+  which would have redded the first Version PR this configuration ever opened. Every version-heading
+  comparison is a whole-heading match rather than a substring, demonstrated on real generator output,
+  because this package sits past the point where `## 0.0.1` is a prefix of a heading it does not
+  have. Three further controls: the same inputs with `"changelog": false` must write no version
+  heading at all, so the flag is proved load-bearing rather than incidental; the same inputs with the
+  Prettier pass off must produce a document this repo's own formatting gate rejects; and the old file
+  shape must reproduce the split header, so the shape rule is demonstrated rather than asserted.
+
+  One upstream behaviour is worth knowing before debugging a release, and is recorded in that file:
+  Changesets wraps the changelog write in a try/catch that only warns. A tree whose declared Prettier
+  config cannot be resolved bumps the version, consumes the changeset, and writes no changelog at all.
+  A release that publishes with an unchanged changelog is that failure, not a setting that quietly
+  reverted.
+
+  `.changeset/README.md` and `CLAUDE.md` said to add the entry to `CHANGELOG.md` by hand and now say
+  to write it in the changeset. No runtime code, no public API, no warning code, no generated byte and
+  no synthetic-safety behaviour changed.
+
+- da7cbdb: The package description, the README, the documentation pages and the exported quirk-registry prose no longer use the em dash, matching the cosyte house voice.
+
+  **Nothing about generation changed.** No export was added, removed or renamed, no warning or fatal
+  code moved, and a given seed still produces byte-identical output for every format. The rewrite is
+  punctuation in prose: an em dash became a colon or a comma in almost every case, and elsewhere a
+  period, a semicolon, a pair of parentheses, a connecting word, or nothing at all, whichever the
+  sentence wanted. Every value this package emits is still drawn from the same reserved
+  and synthetic sources it always was, and no fixture byte moved.
+
+  Two of those surfaces are worth naming because they are read outside the repository.
+  `package.json`'s `description` is what npm shows on the package page and in every search result,
+  and the fourteen pages under `docs-content/` are what ships to the documentation site. The two
+  runtime-visible strings are the `grounding` notes on the HL7 v2 and ASTM quirk descriptors, which
+  are frozen registry text a consumer can read but which nothing is keyed on.
+
+  The hand-maintained changelog history below `## Released before this file was generated` is
+  deliberately untouched. Those entries were accurate when they were written, and a dated record is
+  corrected above itself rather than edited.
+
+- a18b96d: The README lockup now links to cosyte.com (`ASSETS`).
+
+  The `<picture>` block above the H1 is wrapped in an anchor to https://cosyte.com, per the founder
+  requirement of 2026-08-06. Nothing inside the block moved: the `<source>`, the `<img>`, the alt text
+  and both tile URLs are byte-identical.
+
+  What the anchor does was measured on both surfaces by `fhir`, not assumed, because fourteen READMEs
+  carry this shape. On GitHub the anchor works and the colour-scheme switch keeps working, because the
+  `<img>` stays a direct child of `<picture>`, which is the condition the HTML spec puts on `<source>`
+  applying at all. On an npm package page the anchor is lost: npm wraps a README image in its own
+  anchor to the image file, a nested anchor is not representable, so the parser closes ours early and
+  the image ends up linked to the image file rather than to cosyte.com. Shipped anyway by founder
+  decision of 2026-08-07: on npm that is no worse than the unlinked lockup it replaces, and GitHub is
+  where these READMEs are read.
+
+## Released before this file was generated
+
+Every release section above this heading is written by
+[Changesets](https://github.com/changesets/changesets) from the changesets in `.changeset/`, newest
+release first. The release writes its own version heading, so nothing above this line is maintained
+by hand: a change is recorded by adding a changeset, and that changeset's summary is the entry a
+reader sees here.
+
+Everything below this heading was maintained by hand. It sat under a single `[Unreleased]` heading
+that no release ever rolled over, and `CHANGELOG.md` is listed in `package.json` `files`, so every
+published tarball of this package described its own already-shipped contents as unreleased, under a
+preamble promising that a first pre-alpha release would ship the API surface listed under it. That
+promise was already in the future tense in the very tarball that fulfilled it, and it stayed in the
+future tense through every release after. The history is left exactly as it was written rather than re-sorted into
+version sections: the file never recorded which release any entry went out in, and this is the text
+that installed copies already carry on disk. Only three things were dropped, all of them scaffolding
+for the hand-written workflow that no longer runs: the `[Unreleased]` heading itself, its link
+definition at the foot of the file, and the two empty section stubs (`### Deprecated` and
+`### Removed`) that were waiting to receive the next hand-written entry. No entry was reworded.
+
+The entries below follow [Keep a Changelog](https://keepachangelog.com/en/1.1.0/); the generated
+sections above use the format Changesets writes, which is a version heading and a list of the
+changesets that release consumed. This package is on the pre-alpha `0.0.x` ladder and adheres to
+[Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
 ### Added
 
@@ -541,10 +679,6 @@ its public history at `0.0.x`, per the cosyte version ladder (`0.0.x` until firs
   a frozen exported constant, so a consumer asserting them verbatim is affected. The `format` values and
   the shape of the constant are unchanged, and no generated byte changes.
 
-### Deprecated
-
-### Removed
-
 ### Fixed
 
 - **`pnpm phi-scan` could print `OK` and exit 0 over a whole scan root it never opened, because the
@@ -1016,5 +1150,3 @@ attw` and `find dist -name '*.d.*ts' -delete && pnpm attw` printed the sentence
   of the positions that have been checked. That wording is now in the test file's own header, in
   `docs-content/limitations.md` and in `CLAUDE.md`, so the next person to add a position adds a slot
   rather than trusting a count.
-
-[Unreleased]: https://github.com/cosyte/synth/commits/main

package/README.md

@@ -1,11 +1,13 @@
-<picture>
-  <source media="(prefers-color-scheme: dark)" srcset="https://cosyte.com/tile/cosyte-lockup-tile-on-dark-1200x300.png">
-  <img alt="Cosyte: a plus mark set in two overlapping rounded squares, one solid and one outlined, beside the Cosyte wordmark" src="https://cosyte.com/tile/cosyte-lockup-tile-on-light-1200x300.png">
-</picture>
+<a href="https://cosyte.com">
+  <picture>
+    <source media="(prefers-color-scheme: dark)" srcset="https://cosyte.com/tile/cosyte-lockup-tile-on-dark-1200x300.png">
+    <img alt="Cosyte: a plus mark set in two overlapping rounded squares, one solid and one outlined, beside the Cosyte wordmark" src="https://cosyte.com/tile/cosyte-lockup-tile-on-light-1200x300.png">
+  </picture>
+</a>
 
 # @cosyte/synth
 
-> Deterministic, seedable **synthetic healthcare-fixture generator** for Node.js and TypeScript —
+> Deterministic, seedable **synthetic healthcare-fixture generator** for Node.js and TypeScript:
 > spec-clean by construction, and **never real PHI**.
 
 `@cosyte/synth` generates reproducible synthetic test corpora across the six cosyte formats (HL7 v2,
@@ -13,19 +15,19 @@ FHIR R4 / US Core, C-CDA, X12, NCPDP, and ASTM). It is a **consumer** of the
 cosyte parsers, not a parser: it builds each artifact **through the parser's own builder/serializer**
 (so the output is spec-clean by the same mechanism the parser proves) and draws every identifier, name,
 date, phone, and address from a **guaranteed-non-colliding synthetic source**. It is a
-**format/conformance generator, not a clinical simulator** — it does not model disease progression
+**format/conformance generator, not a clinical simulator**: it does not model disease progression
 (that is Synthea).
 
 > **Status:** pre-alpha (`0.0.x`), published to npm. The version shown on the npm package page is the
 > one that is live; this page never repeats it. The generator is **feature-complete**: the
 > seeded-PRNG core, the synthetic-safety providers, and the round-trip harness; **spec-clean generation
-> across all six formats** — HL7 v2 (`ADT`/`ORU`/`ORM`/`SIU`/`VXU`), FHIR R4 / US Core (the full clinical
+> across all six formats**, HL7 v2 (`ADT`/`ORU`/`ORM`/`SIU`/`VXU`), FHIR R4 / US Core (the full clinical
 > set + `collection`/`transaction`/`document` Bundles), C-CDA R2.1 (CCD + Referral Note), X12 005010
 > (837P/I/D, 835, 271), NCPDP (SCRIPT NewRx / RxRenewal / RxChange + Telecom B1/B2/B3), and ASTM (E1394
 > record reports + E1381 framing), each built **through its parser's own builder/serializer**; **vendor-quirk
-> mode** — profile-driven off-spec fixtures for the three richest profile systems (**HL7 v2, C-CDA, ASTM**),
+> mode**, profile-driven off-spec fixtures for the three richest profile systems (**HL7 v2, C-CDA, ASTM**),
 > each round-tripping to exactly the intended parser warning (the intended-warning contract); and the
-> **`@cosyte/deid` pairing loop** — a closed-loop co-validation harness that de-identifies generated output
+> **`@cosyte/deid` pairing loop**, a closed-loop co-validation harness that de-identifies generated output
 > and proves every planted synthetic PHI sentinel is removed.
 >
 > **Deferred (honestly out of scope for now):** quirk recipes for **FHIR / X12 / NCPDP** (and any quirk
@@ -42,13 +44,13 @@ npm install @cosyte/synth @cosyte/hl7 @cosyte/fhir @cosyte/ccda @cosyte/x12 @cos
 `@cosyte/hl7`, `@cosyte/fhir`, `@cosyte/ccda`, `@cosyte/x12`, `@cosyte/ncpdp`, `@cosyte/astm`, and
 `@cosyte/deid` are **optional peer dependencies**, each needed only for its subpath (`@cosyte/synth/hl7`,
 `@cosyte/synth/fhir`, `@cosyte/synth/ccda`, `@cosyte/synth/x12`, `@cosyte/synth/ncpdp`,
-`@cosyte/synth/astm`, and `@cosyte/synth/deid` — the last needs `@cosyte/deid` **plus** the parsers for
-the formats it pairs) — install only the packages whose fixtures you generate. The package core has
+`@cosyte/synth/astm`, and `@cosyte/synth/deid`: the last needs `@cosyte/deid` **plus** the parsers for
+the formats it pairs): install only the packages whose fixtures you generate. The package core has
 **zero third-party runtime dependencies**.
 
 ## Generate a spec-clean HL7 v2 message
 
-The HL7 v2 set covers `ADT` (`A01`/`A04`/`A08`), `ORU^R01`, `ORM^O01`, `SIU^S12`, and `VXU^V04` —
+The HL7 v2 set covers `ADT` (`A01`/`A04`/`A08`), `ORU^R01`, `ORM^O01`, `SIU^S12`, and `VXU^V04`:
 each built through `@cosyte/hl7`'s `buildMessage`, so it is spec-clean by construction.
 
 ```ts
@@ -64,7 +66,7 @@ roundTrip(oru).specClean; // true
 
 // Or generate a reproducible mixed corpus across every family:
 const corpus = hl7Corpus({ seed: 42, count: 7 }); // one of each family, cycled
-corpus.artifacts.every((a) => a.warnings.length === 0); // true — all spec-clean
+corpus.artifacts.every((a) => a.warnings.length === 0); // true, all spec-clean
 
 // Dispatch by kind when the message type is data:
 generateHl7("VXU^V04", 12345);
@@ -73,8 +75,8 @@ generateHl7("VXU^V04", 12345);
 ## Generate a spec-clean FHIR R4 / US Core resource
 
 The `@cosyte/synth/fhir` subpath builds resources **through `@cosyte/fhir`'s model constructors**, so
-they are spec-clean by construction — validating under `validateResource` and, against the **real US
-Core 6.1.0 profiles** (bring your own `StructureDefinition`s — none is bundled), conformant to US Core.
+they are spec-clean by construction: validating under `validateResource` and, against the **real US
+Core 6.1.0 profiles** (bring your own `StructureDefinition`s, none is bundled), conformant to US Core.
 The clinical set covers `Patient` (base + US Core), `Condition`, `Observation` (US Core Laboratory
 Result + Vital Signs), `MedicationRequest`, `Encounter`, `DiagnosticReport`, `Immunization`,
 `AllergyIntolerance`, and `Procedure`, assembled into a `collection`, `transaction`, or `document`
@@ -83,7 +85,7 @@ Result + Vital Signs), `MedicationRequest`, `Encounter`, `DiagnosticReport`, `Im
 ```ts
 import { generatePatient, generateBundle, fhirCorpus, roundTrip } from "@cosyte/synth/fhir";
 
-// A US Core Patient — same seed → byte-identical resource, anywhere.
+// A US Core Patient: same seed → byte-identical resource, anywhere.
 const patient = generatePatient({ seed: 12345, profile: "us-core" });
 
 // Spec-clean by construction: it round-trips through @cosyte/fhir with zero errors, byte-stable.
@@ -94,7 +96,7 @@ const bundle = generateBundle({ seed: 42, type: "transaction" });
 
 // Or a reproducible mixed corpus across the whole spine:
 const corpus = fhirCorpus({ seed: 2026, count: 6 });
-corpus.artifacts.every((a) => a.warnings.length === 0); // true — all spec-clean
+corpus.artifacts.every((a) => a.warnings.length === 0); // true, all spec-clean
 ```
 
 `@cosyte/fhir` is an **optional peer dependency**, needed only for the `@cosyte/synth/fhir` subpath.
@@ -103,7 +105,7 @@ corpus.artifacts.every((a) => a.warnings.length === 0); // true — all spec-cle
 
 The `@cosyte/synth/ccda` subpath builds Consolidated CDA R2.1 documents **through `@cosyte/ccda`'s
 `buildCcda`**, so template IDs, LOINC section codes, and structured/narrative agreement are the
-builder's own — the document round-trips through `parseCcda` with **zero warnings**. It emits a
+builder's own: the document round-trips through `parseCcda` with **zero warnings**. It emits a
 **CCD** (`generateCcd`) or a **Referral Note** (`generateReferralNote`), each with the CCD sections
 (Problems, Allergies, Medications, Results, Vital Signs, Immunizations, Procedures, Social History)
 populated from the reused, license-clean example-code pools.
@@ -123,7 +125,7 @@ roundTrip(generateReferralNote({ seed: 12345 })).specClean; // true
 
 // Or a reproducible mixed corpus (CCD + Referral Note, cycled):
 const corpus = ccdaCorpus({ seed: 42, count: 4 });
-corpus.artifacts.every((a) => a.warnings.length === 0); // true — all spec-clean
+corpus.artifacts.every((a) => a.warnings.length === 0); // true, all spec-clean
 ```
 
 `@cosyte/ccda` is an **optional peer dependency**, needed only for the `@cosyte/synth/ccda` subpath.
@@ -132,7 +134,7 @@ corpus.artifacts.every((a) => a.warnings.length === 0); // true — all spec-cle
 
 The `@cosyte/synth/x12` subpath builds HIPAA **005010** transactions **through `@cosyte/x12`'s domain
 builders** (`build837P/I/D`, `build835`, `build271`), so the ISA/GS/ST…SE/GE/IEA envelope, the
-computed HL spine, the control numbers, and every segment are the builder's own — each transaction
+computed HL spine, the control numbers, and every segment are the builder's own: each transaction
 round-trips through `@cosyte/x12` with **zero warnings**. It emits **837** professional / institutional
 / dental claims, the **835** remittance (balance-checked by construction), and the **271** eligibility
 response.
@@ -145,13 +147,13 @@ import { generate837P, generate835, generate271, x12Corpus, roundTrip } from "@c
 // never be a NPPES-issued NPI), the provider tax id is an SSA never-issued 900-range SSN, member ids
 // live under a synthetic assigning authority, and names come from the shipped fake-name pool.
 const claim = generate837P({ seed: 12345 });
-roundTrip(claim).specClean; // true — re-parses through @cosyte/x12 with zero warnings, byte-stable
+roundTrip(claim).specClean; // true, re-parses through @cosyte/x12 with zero warnings, byte-stable
 roundTrip(generate835({ seed: 7 })).specClean; // true
 roundTrip(generate271({ seed: 3 })).specClean; // true
 
 // Or a reproducible mixed corpus (837P/I/D + 835 + 271):
 const corpus = x12Corpus({ seed: 42 });
-corpus.artifacts.every((a) => a.warnings.length === 0); // true — all spec-clean
+corpus.artifacts.every((a) => a.warnings.length === 0); // true, all spec-clean
 ```
 
 `@cosyte/x12` is an **optional peer dependency**, needed only for the `@cosyte/synth/x12` subpath.
@@ -180,12 +182,12 @@ import {
 // has a deliberately-INVALID Luhn check digit and the prescriber DEA a deliberately-INVALID checksum
 // (so neither can denote a real provider); patient/cardholder ids live under a synthetic assigning
 // authority, phones are reserved 555-01xx, and names come from the shipped fake-name pool.
-scriptRoundTrip(generateNewRx({ seed: 12345 })).specClean; // true — zero warnings, byte-stable
+scriptRoundTrip(generateNewRx({ seed: 12345 })).specClean; // true, zero warnings, byte-stable
 telecomRoundTrip(generateB1({ seed: 777 })).specClean; // true
 
 // Or a reproducible mixed corpus (NewRx + RxRenewal + RxChange + B1 + B2 + B3):
 const corpus = ncpdpCorpus({ seed: 42 });
-corpus.artifacts.every((a) => a.warnings.length === 0); // true — all spec-clean
+corpus.artifacts.every((a) => a.warnings.length === 0); // true, all spec-clean
 ```
 
 `@cosyte/ncpdp` is an **optional peer dependency**, needed only for the `@cosyte/synth/ncpdp` subpath.
@@ -196,8 +198,8 @@ renewal/change _responses_ land as `@cosyte/ncpdp` grows builders.
 ## Generate a spec-clean ASTM message
 
 The `@cosyte/synth/astm` subpath builds ASTM laboratory messages **through `@cosyte/astm`'s own emit
-surface** — `buildAstmMessage` for the E1394 record layer, `composeAstmFrames` for the E1381 frame
-layer — so each message round-trips through the parser with **zero warnings**. It emits the
+surface**: `buildAstmMessage` for the E1394 record layer, `composeAstmFrames` for the E1381 frame
+layer, so each message round-trips through the parser with **zero warnings**. It emits the
 `H`/`P`/`O`/`R`…/`C`/`L` **result report** (`generateAstmResult`), the `H`/`P`/`O`/`L` **order**
 (`generateAstmOrder`), and the **framed** twin (`generateAstmResultFramed`).
 
@@ -211,17 +213,17 @@ import {
 } from "@cosyte/synth/astm";
 
 // Same seed → byte-identical output. The P (patient) record carries the name, birthdate, and the
-// practice- and laboratory-assigned patient ids — all synthetic-by-construction: names from the shipped
+// practice- and laboratory-assigned patient ids, all synthetic-by-construction: names from the shipped
 // fake-name pool, DOB seeded, and the two ids minted independently under a synthetic assigning authority
 // (so they stay DISTINCT, exactly as @cosyte/astm keeps them on parse).
-astmRoundTrip(generateAstmResult({ seed: 12345 })).specClean; // true — zero warnings, byte-stable
+astmRoundTrip(generateAstmResult({ seed: 12345 })).specClean; // true, zero warnings, byte-stable
 
 // The E1381-framed twin: the modulo-256 checksum and 0–7 frame numbers are computed by @cosyte/astm.
 astmFramedRoundTrip(generateAstmResultFramed({ seed: 12345 })).specClean; // true
 
 // Or a reproducible mixed corpus (a result report + an order):
 const corpus = astmCorpus({ seed: 42 });
-corpus.artifacts.every((a) => a.warnings.length === 0); // true — all spec-clean
+corpus.artifacts.every((a) => a.warnings.length === 0); // true, all spec-clean
 ```
 
 `@cosyte/astm` is an **optional peer dependency**, needed only for the `@cosyte/synth/astm` subpath.
@@ -229,14 +231,14 @@ corpus.artifacts.every((a) => a.warnings.length === 0); // true — all spec-cle
 ## Generate a vendor-quirk fixture
 
 Spec-clean fixtures test that a parser reads a _correct_ message; **quirk mode** tests that it tolerates
-the realistic vendor deviations real traffic carries — and surfaces exactly the right diagnostic. The
+the realistic vendor deviations real traffic carries, and surfaces exactly the right diagnostic. The
 quirk vocabulary **is the parsers' own profile systems**: a quirk deviates the message _structure_ so it
 round-trips to **exactly one intended, stable warning code** (the **intended-warning contract**), and
 where a built-in **public** parser profile claims the deviation, it round-trips cleanly under it
-(suppressed, or re-badged to `PROFILE_QUIRK_APPLIED`). A quirk never introduces a real-looking value —
+(suppressed, or re-badged to `PROFILE_QUIRK_APPLIED`). A quirk never introduces a real-looking value:
 it changes shape, never provenance, so the synthetic-safety gate still passes.
 
-Quirks ship for the three richest profile systems — **HL7 v2, C-CDA, and ASTM**:
+Quirks ship for the three richest profile systems, **HL7 v2, C-CDA, and ASTM**:
 
 ```ts
 import { generateHl7Quirk, hl7QuirkRoundTrip } from "@cosyte/synth/hl7";
@@ -255,7 +257,7 @@ astmQuirkRoundTrip(generateAstmQuirk({ seed: 1, quirk: "unknown-escape" })).inte
 ```
 
 A quirk a format's profile system does not support fails closed with a stable `SYNTH_UNSUPPORTED_QUIRK`
-diagnostic — never a silently-wrong fixture — and so do the other selectors: a message kind, a
+diagnostic, never a silently-wrong fixture, and so do the other selectors: a message kind, a
 document type, a corpus mix entry, an `837` variant, a Bundle type. Each is checked against its own set
 before anything is generated, so an unrecognised one is a fatal `SYNTH_UNSUPPORTED_KIND` rather than a
 mislabelled corpus. Every refusal carries a code and a fixed message from a frozen table, and quotes
@@ -285,8 +287,8 @@ import {
 
 const r = hl7DeidLoop({ seed: 42, kind: "ORU^R01" });
 r.pass; // true
-r.survivors; // []  — every planted synthetic PHI sentinel was removed
-r.clinicalScrubbed; // []  — no clinical value was over-scrubbed
+r.survivors; // [], every planted synthetic PHI sentinel was removed
+r.clinicalScrubbed; // [], no clinical value was over-scrubbed
 
 const summary = summarizeDeidCoverage([
   hl7DeidLoop({ seed: 1 }),
@@ -295,11 +297,11 @@ const summary = summarizeDeidCoverage([
   ncpdpTelecomDeidLoop({ seed: 1, transaction: "B1" }),
   ccdaDeidLoop({ seed: 1 }),
 ]);
-summary.allPass; // true — zero survivors, zero over-scrub, per format
+summary.allPass; // true, zero survivors, zero over-scrub, per format
 ```
 
 This is a **co-validation harness, not an independent audit** of `@cosyte/deid` against real-world
-data — it proves the pair works on `synth`'s own output. The removal check is **locus-scoped**: it
+data: it proves the pair works on `synth`'s own output. The removal check is **locus-scoped**: it
 sweeps only the de-identified values remaining at the former PHI loci, so provider/organization
 identity a de-identifier legitimately retains never reads as a false survivor. `@cosyte/deid` is an
 **optional peer dependency**, needed only for this subpath. **Skipped and named** (`DEID_LOOP_SKIPPED`):
@@ -311,22 +313,22 @@ NCPDP **SCRIPT** and **ASTM** (no `@cosyte/deid` adapter) and **DICOM** (not gen
 import { createRng, safe, isSyntheticSsn, isSyntheticNpi } from "@cosyte/synth";
 
 const rng = createRng(42);
-isSyntheticSsn(safe.ssn(rng)); // true — always an SSA never-issued SSN
-isSyntheticNpi(safe.npi(rng)); // true — always a deliberately-invalid-Luhn NPI (never a real NPI)
+isSyntheticSsn(safe.ssn(rng)); // true, always an SSA never-issued SSN
+isSyntheticNpi(safe.npi(rng)); // true, always a deliberately-invalid-Luhn NPI (never a real NPI)
 ```
 
 ## What makes it trustworthy
 
-- **Synthetic-by-construction** — no code path emits a value not drawn from a reserved range or the
+- **Synthetic-by-construction**, no code path emits a value not drawn from a reserved range or the
   shipped fake-name pool (SSA never-issued SSNs, NANP `555-01xx` phones, RFC 2606/6761 `example.*`
   domains, RFC 5737/3849 TEST-NET IPs, a synthetic assigning authority for MRNs). A CI gate proves it.
   **No generated value can be real or plausibly-real PHI.**
-- **Spec-clean by the parser's own judgment** — built through the parser's conservative serializer, and
+- **Spec-clean by the parser's own judgment**, built through the parser's conservative serializer, and
   checked by feeding the artifact straight back in: a spec-clean artifact re-parses with zero warnings.
-- **Deterministic** — a hand-rolled seeded PRNG (`sfc32`/`splitmix32`); `Math.random` is lint-banned.
-  A seed, and only the seed, determines the output — byte-for-byte, anywhere.
-- **Immutable** — generated artifacts and the `Corpus` result are deep-frozen.
-- **Zero third-party runtime dependencies** — the parser peers are first-party cosyte packages,
+- **Deterministic**, a hand-rolled seeded PRNG (`sfc32`/`splitmix32`); `Math.random` is lint-banned.
+  A seed, and only the seed, determines the output, byte-for-byte, anywhere.
+- **Immutable**, generated artifacts and the `Corpus` result are deep-frozen.
+- **Zero third-party runtime dependencies**, the parser peers are first-party cosyte packages,
   vendored for dev/test; dual ESM + CJS, validated with `attw`.
 
 ## License

package/dist/astm/index.cjs

@@ -34,30 +34,30 @@ function sfc32Next(s) {
 // src/codes.ts
 var SYNTH_FATAL_CODES = {
   /**
-   * A vendor quirk was requested that the target format's profile system does not support. Fatal —
+   * A vendor quirk was requested that the target format's profile system does not support. Fatal,
    * never a silent no-op and never a fabricated quirk.
    */
   SYNTH_UNSUPPORTED_QUIRK: "SYNTH_UNSUPPORTED_QUIRK",
   /**
    * A quirk transform found no structural anchor to mutate, so the fixture would not carry the
-   * deviation it is labelled with. Fatal — a golden file that lies about its parser verdict is worse
+   * deviation it is labelled with. Fatal: a golden file that lies about its parser verdict is worse
    * than no golden file.
    */
   SYNTH_QUIRK_ANCHOR_ABSENT: "SYNTH_QUIRK_ANCHOR_ABSENT",
   /**
    * A bare parse of a freshly-generated quirk artifact did not produce exactly the declared intended
-   * warning code(s). Fatal — never emit a mislabeled fixture.
+   * warning code(s). Fatal, never emit a mislabeled fixture.
    */
   SYNTH_INTENDED_WARNING_MISMATCH: "SYNTH_INTENDED_WARNING_MISMATCH",
   /** An integer range was requested with its maximum below its minimum. Fatal. */
   SYNTH_INVALID_RANGE: "SYNTH_INVALID_RANGE",
-  /** A value was drawn from an empty pool. Fatal — never a fabricated substitute. */
+  /** A value was drawn from an empty pool. Fatal, never a fabricated substitute. */
   SYNTH_EMPTY_POOL: "SYNTH_EMPTY_POOL",
   /** A `defineSynthProfile` spec was not usable (a missing or blank `name`). Fatal. */
   SYNTH_INVALID_PROFILE: "SYNTH_INVALID_PROFILE",
   /**
    * A caller-supplied selector (a message kind, a document type, a corpus mix entry, a claim
-   * variant, a Bundle type, a resource profile) is not in the closed set that governs it. Fatal —
+   * variant, a Bundle type, a resource profile) is not in the closed set that governs it. Fatal:
    * see `resolveKind`: a selector union is erased at run time, and a selector that falls through
    * either mislabels the fixture or hands the value to a peer builder that quotes it back.
    */
@@ -151,7 +151,7 @@ function makeCorpus(seed, artifacts, quirks = []) {
 var SYNTHETIC_ASSIGNING_AUTHORITY = Object.freeze({
   /** The human-readable assigning-authority namespace id (HL7 HD.1). */
   namespaceId: "COSYTE-SYNTH",
-  /** The universal id — an OID under HL7's example arc `2.16.840.1.113883.19` (HD.2). */
+  /** The universal id, an OID under HL7's example arc `2.16.840.1.113883.19` (HD.2). */
   universalId: "2.16.840.1.113883.19.999",
   /** The universal id type (HD.3). */
   universalIdType: "ISO"
@@ -722,7 +722,7 @@ var ASTM_QUIRKS = Object.freeze({
     name: "unknown-record-type",
     format: "astm",
     intendedWarnings: Object.freeze(["ASTM_RECORD_UNKNOWN_TYPE"]),
-    grounding: "ASTM E1394 permits manufacturer/site-defined record types; a Z record is surfaced as unsupported. A tolerable code (in the parser's defineAstmProfile allow-list) \u2014 a consumer authors a profile to re-badge it; no built-in public profile does.",
+    grounding: "ASTM E1394 permits manufacturer/site-defined record types; a Z record is surfaced as unsupported. A tolerable code (in the parser's defineAstmProfile allow-list): a consumer authors a profile to re-badge it; no built-in public profile does.",
     disposition: "bare"
   })
 });