@cosyte/x12 0.0.17 → 0.0.18

package/dist/index.d.cts

@@ -7,10 +7,10 @@ import { Buffer } from 'node:buffer';
  * warning it emits so messages, payload shape, and positional context stay
  * consistent across stages.
  *
- * The Phase 1 set is intentionally small (8 codes) - every additional code
+ * The envelope set is intentionally small (8 codes) - every additional code
  * is a public-surface addition that needs a snapshot bump
- * (see `test/warning-codes.snapshot.test.ts`). Phase 2+ extends, never
- * renames.
+ * (see `test/warning-codes.snapshot.test.ts`). Later stages extend, never
+ * rename.
  *
  * ## A warning message is built from this registry, never from the document
  *
@@ -299,13 +299,19 @@ interface X12ParseWarning {
  */
 declare function controlNumberMismatch(position: X12Position, pair: X12ControlNumberPair): X12ParseWarning;
 /**
- * Build an `X12_PRE_005010` warning. Emitted when ISA-12 declares any version
- * other than `00501`, the HIPAA-mandated baseline. The code name reads as a
+ * Build an `X12_PRE_005010` warning. Emitted when the twelfth element of the
+ * ISA split does not read `00501`, the HIPAA-mandated baseline interchange
+ * control version number. The code name reads as a
  * "pre-005010" test and the guard is an inequality, so a LATER family
  * (`00602`, `00700`) raises it too. The parser still
  * accepts the input (Postel's Law: lenient on parse) but flags the
  * mismatch so consumers know the input may diverge from 005010 semantics.
- * The declared version stays on `isa.elements[12]`.
+ *
+ * The guard reads that element, so raising this code does NOT establish that
+ * the header split into `ISA` plus 16 elements and does not assert what ISA-12
+ * itself declares. Where `X12_ISA_EXTRA_ELEMENT_SEPARATOR` is also present the
+ * element read may be a displaced one; `isa.raw` carries all 106 bytes and with
+ * the ISA fixed widths is the route back.
  *
  * @example
  * ```ts
@@ -376,8 +382,7 @@ declare function transactionCountMismatch(position: X12Position): X12ParseWarnin
  * segments in the transaction set it closes (ST through SE inclusive).
  * Corrected counts are emitted only on `serializeX12(ix, { specClean: true,
  * recomputeCounts: true })`. The parser does not emit this code (it leaves
- * SE-01 reconciliation to the emit half); it is a Phase-8 serializer
- * diagnostic.
+ * SE-01 reconciliation to the emit half); it is a serializer diagnostic.
  *
  * @example
  * ```ts
@@ -623,7 +628,7 @@ declare function missingRequiredLoop(position: X12Position, loop: X12RequiredLoo
  * `submission.implementationConventionReference` is decoded of any `?` release
  * escape, so on a document that escapes a delimiter inside `ST-03` the two
  * differ and the model field can hold an identifier this code just said was
- * not recognised (`X12-ST03-READ-NOT-RELEASE-AWARE`). A pointer stood here and
+ * not recognised. A pointer stood here and
  * in the message text and is DELETED, not reworded.
  *
  * `get837Claims` anchors this at the **ST**, which is `tx.segments[0]` and
@@ -1013,7 +1018,7 @@ declare function amountRowDropped(position: X12Position): X12ParseWarning;
 declare function statedAmountDiscarded(position: X12Position): X12ParseWarning;
 
 /**
- * Type definitions for the `@cosyte/x12` profile subsystem (Phase 9).
+ * Type definitions for the `@cosyte/x12` profile subsystem.
  *
  * A profile captures **trading-partner / companion-guide deviations** as
  * typed, documented, fixture-grounded data - never silent leniency. It
@@ -1185,7 +1190,7 @@ interface X12ProfileSpec {
  * an 835 claim, a dropped decimal is the wrong dollar amount in someone's
  * cash post. `X12Decimal` preserves the inbound lexical form verbatim for
  * byte-exact round-trip and exposes exact `BigInt`-backed arithmetic for
- * balance invariants (Phase 4 acceptance: CLP-04 + CLP-05 + ΣCAS = CLP-03;
+ * balance invariants (CLP-04 + CLP-05 + ΣCAS = CLP-03;
  * ΣSVC paid + ΣCAS = CLP-04; Σclaim CLP-04 + PLB = BPR-02).
  *
  * Internal representation:
@@ -1407,7 +1412,7 @@ declare class X12Decimal {
 }
 
 /**
- * Segment-level decode for the `@cosyte/x12` parser pipeline. Phase 2's
+ * Segment-level decode for the `@cosyte/x12` parser pipeline. The
  * syntactic core: take a raw segment string (terminator already stripped by
  * the envelope walker) and decode it into an immutable {@link X12Segment}
  * carrying its segment id, raw text, and an element array. Element values
@@ -1428,8 +1433,8 @@ declare class X12Decimal {
  * - `"03[2]-1"` → component 1 of repetition 2 of element 3.
  *
  * The parser deliberately does NOT support cross-segment paths at this
- * phase - `Segment.get` operates inside a single segment. Cross-loop
- * traversal arrives with `defineLoopSpec` in Phase 3+ (which authors the
+ * level - `Segment.get` operates inside a single segment. Cross-loop
+ * traversal arrives with `defineLoopSpec` (which authors the
  * built-in transaction loops through the same public API as consumers -
  * the dogfooding gate).
  */
@@ -1813,13 +1818,13 @@ interface X12ParseOptions {
 }
 /**
  * The four X12 delimiter classes discovered from fixed byte positions inside
- * the ISA envelope. Phase 1 detects all four from the ISA itself - they are
+ * the ISA envelope. The parser detects all four from the ISA itself - they are
  * NEVER assumed (in particular, `component` is rarely `:` outside Medicare).
  *
  * - `element` - ISA byte 4 (1-indexed); separates the 16 ISA elements.
  * - `repetition` - ISA-11 (byte 83, 1-indexed); separates repetitions inside
  *   an element. Carries the legacy Control Standards Identifier
- *   (typically `U`) for pre-005010 inputs; Phase 1 surfaces it verbatim.
+ *   (typically `U`) for pre-005010 inputs; the parser surfaces it verbatim.
  * - `component` - ISA-16 (byte 105, 1-indexed); separates sub-elements of a
  *   composite. Real-world senders use `:`, `\\`, `^`, `|`, and more.
  * - `segment` - the byte immediately after ISA-16 (byte 106, 1-indexed);
@@ -1844,18 +1849,27 @@ interface Delimiters {
     readonly segment: string;
 }
 /**
- * The decoded ISA interchange header. `raw` preserves the exact 106-byte
- * ISA + terminator string from input so round-trip serialization is
- * byte-exact regardless of any lenient normalization downstream. `elements`
- * is the 16 ISA values, 1-indexed (`elements[0]` is the literal `"ISA"`
- * name placeholder, `elements[1]` is ISA-01, ..., `elements[16]` is ISA-16).
+ * The decoded ISA interchange header. ISA-12 is the interchange control
+ * version number, `00501` being the HIPAA-mandated baseline, and ISA-13 the
+ * interchange control number, which the envelope walker reconciles against
+ * IEA-02.
+ *
+ * `raw` preserves the exact 106-byte ISA + terminator string from input so
+ * round-trip serialization is byte-exact regardless of any lenient
+ * normalization downstream. `elements` is what splitting that span on the
+ * element separator produced, `elements[0]` being the literal `"ISA"` name
+ * placeholder. **Element values are stored RAW**, so an entry is byte text
+ * and not necessarily the value the sender stated. The 1-indexed mapping onto
+ * ISA-01..ISA-16 holds where that split produced exactly 17 entries;
+ * `X12_ISA_EXTRA_ELEMENT_SEPARATOR` reports where it did not, and `raw`
+ * carries all 106 bytes either way.
  *
  * @example
  * ```ts
  * import type { IsaSegment } from "@cosyte/x12";
  * declare const isa: IsaSegment;
- * isa.elements[12]; // ISA-12 - version, expected "00501"
- * isa.elements[13]; // ISA-13 - interchange control number
+ * isa.raw;             // verbatim 106-byte header
+ * isa.elements[13];    // raw text at index 13 of the ISA split
  * ```
  */
 interface IsaSegment {
@@ -1949,7 +1963,7 @@ interface GeSegment {
  * pre-`?`-unescape**, so an element is the framed byte text of its slot and
  * not necessarily the value the sender stated.
  *
- * The Phase 3 envelope walker captures TA1 segments here verbatim; the
+ * The envelope walker captures TA1 segments here verbatim; the
  * typed-ack model is built on top by `parseTA1`, whose five decoded fields
  * are POST-`?`-unescape. `parseTA1` decodes the FIRST TA1 on an
  * interchange, so on a multi-TA1 inbound it does not necessarily describe
@@ -1969,7 +1983,7 @@ interface Ta1Segment {
     readonly elements: readonly string[];
 }
 /**
- * A single ST..SE transaction set inside a functional group. Phase 2
+ * A single ST..SE transaction set inside a functional group. The parser
  * decodes every body segment via {@link "./segment.js".decodeSegment} so
  * `segments` carries typed {@link X12Segment} entries (ST through SE,
  * inclusive). `rawSegments` mirrors the same list as the verbatim raw
@@ -1980,7 +1994,7 @@ interface Ta1Segment {
  * time so envelope invariants can be checked (ST-02 ↔ SE-02 control-number
  * reconciliation, SE-01 segment count). **Read "decoded" as element-SPLIT and
  * nothing more: the strings are PRE-`?`-unescape**, and a reader that publishes
- * one to a consumer unescapes it first (`X12-ST03-READ-NOT-RELEASE-AWARE`).
+ * one to a consumer unescapes it first.
  *
  * @example
  * ```ts
@@ -2006,7 +2020,7 @@ interface X12TransactionSet {
 /**
  * A single GS..GE functional group inside an interchange. `transactions`
  * is the ordered list of ST..SE transaction sets inside it (opaque bodies
- * at Phase 1 - see {@link X12TransactionSet}).
+ * at envelope decode - see {@link X12TransactionSet}).
  *
  * @example
  * ```ts
@@ -2221,7 +2235,7 @@ interface X12Interchange {
 }
 
 /**
- * Public entry point for the `@cosyte/x12` parser - composes the Phase 1
+ * Public entry point for the `@cosyte/x12` parser - composes the
  * delimiter-detection + envelope-decode stages and routes every Tier-2
  * warning through a single emission chokepoint. The four Tier-3 fatal codes
  * (`X12_EMPTY_INPUT`, `X12_NO_ISA_HEADER`, `X12_ISA_TOO_SHORT`,
@@ -2245,11 +2259,11 @@ interface X12Interchange {
  * carries an empty `snippet`: the warning it wraps is registry-built and
  * fully located by `position`, so there is nothing to redact.
  *
- * Phase 1 decodes the envelope (ISA / GS / ST / SE / GE / IEA) and
- * detects the four delimiters from fixed ISA byte positions. Transaction-
- * set bodies inside each ST..SE are kept **opaque** at this phase -
- * `tx.segments` carries the raw segment strings (terminator stripped).
- * Phase 2 adds segment/element/composite/repetition decode on top.
+ * The envelope decode reads ISA / GS / ST / SE / GE / IEA and detects the
+ * four delimiters from fixed ISA byte positions. Transaction-set bodies
+ * inside each ST..SE are kept **opaque** there - `tx.segments` carries the
+ * raw segment strings (terminator stripped). Segment decode adds
+ * element/composite/repetition decode on top.
  *
  * @example
  * ```ts
@@ -2341,7 +2355,7 @@ declare const DELIMITER_POSITIONS: {
  *   against an input that begins with `"ISA"` followed by structurally
  *   wrong bytes (e.g. a tab as element separator with `:` further in).
  *
- * Phase 1 is liberal in what it accepts AFTER the ISA - downstream
+ * The parser is liberal in what it accepts AFTER the ISA - downstream
  * envelope walking emits Tier-2 warnings rather than throwing. But the
  * ISA itself MUST be structurally readable; otherwise no later stage has
  * a delimiter set to work with.
@@ -2360,7 +2374,7 @@ declare function detectDelimiters(raw: string): Delimiters;
 
 /**
  * Fatal error taxonomy for the `@cosyte/x12` parser pipeline. Four Tier-3
- * codes cover every unrecoverable structural failure in Phase 1; anything
+ * codes cover every unrecoverable structural failure; anything
  * less severe is a Tier-2 warning (see `./warnings.ts`). `X12ParseError` is
  * thrown directly; consumers narrow via the `code` discriminant. The set is
  * locked at 4 and is additions-only thereafter - adding a code is a
@@ -2368,8 +2382,8 @@ declare function detectDelimiters(raw: string): Delimiters;
  */
 
 /**
- * Stable string codes for every Tier-3 fatal `parseX12` may throw. Phase 1
- * locks the registry at four codes: anything else MUST be a Tier-2 warning.
+ * Stable string codes for every Tier-3 fatal `parseX12` may throw. The
+ * registry is locked at four codes: anything else MUST be a Tier-2 warning.
  * Consumers narrow on `err.code` to react to specific structural failures.
  *
  * @example
@@ -2480,7 +2494,7 @@ declare class X12ParseError extends Error {
  *
  * The pair `{ unescapeRelease, escapeRelease }` is bijective on inputs that
  * either contain no release-relevant characters OR are already a clean
- * round-trip - this gives the Phase 2 lossless round-trip property: for any
+ * round-trip - this gives the lossless round-trip property: for any
  * value `v` and delimiter set `d`, `unescapeRelease(escapeRelease(v, d), d)`
  * deep-equals `v`.
  */
@@ -2570,9 +2584,9 @@ declare function escapeRelease(value: string, delimiters: Delimiters): string;
  * Public type surface for the `defineLoopSpec()` API. A {@link LoopSpec}
  * is a declarative description of a TR3 loop (e.g. `Loop 2300` in 837P /
  * `Loop 2110` in 835): which segments belong to it, in what order, with
- * what cardinality, and which child loops nest inside it. Phase 2 ships the
- * API and types only - built-in transaction loop specs for the 12 v1
- * transactions are authored through this same public API in Phases 3+
+ * what cardinality, and which child loops nest inside it. This module ships
+ * the API and types only - built-in transaction loop specs for the 12 v1
+ * transactions are authored through this same public API
  * (the dogfooding gate locked in `documentation/repos/x12.md`).
  *
  * Naming convention: `id` is a human-readable loop identifier (`"2300"` for
@@ -2591,7 +2605,7 @@ declare function escapeRelease(value: string, delimiters: Delimiters): string;
  * - `required` - the segment/loop MUST appear at least once.
  * - `situational` - the segment/loop MAY appear when its situational rule
  *   triggers; the parser does not enforce the rule itself but loop-walker
- *   warnings (Phase 3+) reference it.
+ *   warnings reference it.
  * - `optional` - the segment/loop MAY appear in any usage.
  *
  * @example
@@ -2604,8 +2618,8 @@ type LoopUsage = "required" | "situational" | "optional";
 /**
  * Repetition count for a segment or child loop inside its parent. `">1"`
  * means many (TR3 typically writes `>1` to mean "no cap"). A finite max
- * surfaces as the numeric value. Phase 2 stores the value; Phase 3+'s
- * loop walker uses it for over-limit warnings.
+ * surfaces as the numeric value. This module stores the value; the loop
+ * walker uses it for over-limit warnings.
  *
  * @example
  * ```ts
@@ -2618,7 +2632,7 @@ type LoopMax = number | ">1";
 /**
  * A segment slot inside a loop body. Carries the segment id, its TR3
  * usage + cardinality, and an optional position label (e.g. `"Loop 2300
- * #2"`) used by Phase 3+ loop-walker diagnostics. Stored verbatim by
+ * #2"`) used by loop-walker diagnostics. Stored verbatim by
  * `defineLoopSpec`; no validation beyond the structural shape so consumers
  * can author payer-specific segment specs without re-deriving each rule.
  *
@@ -2636,7 +2650,7 @@ interface LoopSegmentSpec {
     readonly description?: string;
 }
 /**
- * A declarative loop description used by Phase 3+ transaction extractors
+ * A declarative loop description used by the transaction extractors
  * and consumer-authored payer profiles alike. Frozen by `defineLoopSpec`
  * so a `LoopSpec` is safe to share across calls.
  *
@@ -2666,12 +2680,12 @@ interface LoopSpec {
 /**
  * Public `defineLoopSpec()` factory for the `@cosyte/x12` loop surface.
  * Returns a frozen {@link LoopSpec} after structural validation - no
- * runtime walker (Phase 3+ owns walking). The DOGFOODING gate: every
- * built-in transaction loop spec shipped in Phases 3+ is authored through
+ * runtime walker (the transaction extractors own walking). The DOGFOODING
+ * gate: every built-in transaction loop spec is authored through
  * this same public API consumers use for payer-specific loops, so a
  * regression in the public surface is impossible to hide.
  *
- * Validation is strictly structural at this phase:
+ * Validation is strictly structural:
  *
  * - `id` and `trigger` are non-empty strings.
  * - `trigger` segment id passes the same `[A-Z][A-Z0-9]{1,2}` shape used
@@ -2778,7 +2792,7 @@ declare function defineLoopSpec(input: DefineLoopSpecInput): LoopSpec;
  *
  * Snapshots are deliberately tiny in v0.0.x - pre-launch initial subsets
  * covering only the codes already exercised by the parser's Tier-1 + Tier-2
- * fixtures. The Phase 10 `pnpm refresh:code-lists` script will regenerate
+ * fixtures. The `pnpm refresh:code-lists` script will regenerate
  * the full WPC-published lists from canonical sources for the first real
  * release; until then `lookup(code)` returns `undefined` for codes outside
  * the subset and consumers receive the **verbatim** inbound code (the
@@ -2868,7 +2882,7 @@ interface CodeListSnapshot {
  * **Pre-launch initial subset.** This snapshot covers the ~30 most
  * commonly observed CARC codes - every value exercised by the Tier-1 /
  * Tier-2 fixtures plus the long-tail codes most cash-posting workflows
- * branch on. The Phase 10 `pnpm refresh:code-lists` script regenerates
+ * branch on. The `pnpm refresh:code-lists` script regenerates
  * the full WPC-published list from the canonical source for the first
  * real publish; until then a CARC absent from the snapshot still parses
  * fine (verbatim) - only its description is unavailable.
@@ -3014,9 +3028,9 @@ declare const lookupClaimStatus: (code: string) => CodeListEntry | undefined;
  *
  * **Initial bundled subset** covers the ~10 most common dispositions.
  * Codes outside the subset still parse (verbatim code preserved on the
- * model); a `X12_UNKNOWN_CLP_STATUS` warning would be a Phase 5+ addition
- * (not bundled at Phase 4 to keep the additions-only warning registry
- * surgical - Phase 4 only adds the codes it actually uses).
+ * model); a `X12_UNKNOWN_CLP_STATUS` warning would be a later addition
+ * (not bundled here, to keep the additions-only warning registry surgical -
+ * this table only carries the codes the readers actually use).
  */
 
 /**
@@ -3288,8 +3302,8 @@ declare const lookupRarc: (code: string) => CodeListEntry | undefined;
  * unknown qualifiers map to `"unknown"` and the verbatim code is still
  * preserved on the parsed diagnosis / procedure.
  *
- * Snapshot date 2026-06-27. This is a curated read-only table - Phase 9
- * (vendor profiles) may LAYER additional qualifiers per payer, but the
+ * Snapshot date 2026-06-27. This is a curated read-only table - the profile
+ * system may LAYER additional qualifiers per payer, but the
  * BASE mapping ships as a frozen artifact so a single CMS change isn't a
  * silent semantic drift.
  */
@@ -4752,7 +4766,7 @@ declare class Remit835BuildError extends Error {
 /**
  * 835 TR3 `005010X221A1` loop specification - authored through the
  * **public** {@link "../../loops/define.js".defineLoopSpec} API. This is
- * the Phase 4 dogfooding gate: the built-in 835 loop hierarchy goes
+ * the dogfooding gate: the built-in 835 loop hierarchy goes
  * through the SAME factory consumers use for payer-specific companion-
  * guide loops. A regression in `defineLoopSpec` cannot hide from the
  * built-in extractors.
@@ -4783,11 +4797,11 @@ declare class Remit835BuildError extends Error {
  * ```
  *
  * @remarks
- * Phase 4 surfaces the loop spec as a frozen artifact (consumers can read
+ * The loop spec is surfaced as a frozen artifact (consumers can read
  * it and assert it matches their companion-guide expectations); the
  * walker in `./get-835.ts` consults the spec to guide its state machine.
- * Phase 9's profile system overlays vendor-specific quirks on top of
- * this baseline.
+ * The profile system overlays vendor-specific quirks on top of this
+ * baseline.
  */
 
 /**
@@ -4822,7 +4836,7 @@ declare const REMIT_835_LOOP_2100: LoopSpec;
  *
  * Cited as Loop 2000 in TR3 X221A1; situational because some payers
  * (notably Medicare FFS) omit the LX header entirely and ship CLP loops
- * directly under the transaction set header. The Phase 4 walker handles
+ * directly under the transaction set header. The walker handles
  * both shapes - claims appear inside Loop 2000 if `LX` is present, at
  * top level otherwise.
  *
@@ -4893,8 +4907,7 @@ declare const REMIT_835_LOOP_1000B: LoopSpec;
  *    (reduces BPR-02), negative PLB = credit to provider (increases
  *    BPR-02). So subtraction is what makes the equation balance.
  *
- * > Phase 4 implementation note: the cosyte roadmap (`operations/roadmaps/x12.md`
- * > §4) sketched these invariants slightly differently - that sketch was a
+ * > Implementation note: an early internal sketch of these invariants was a
  * > simplification. The implementation here matches the **X12 005010X221A1
  * > TR3 §1.10.2 spec text** directly; the roadmap is updated in the same
  * > slice with a forward-pointer to this module so the contract stays
@@ -5248,7 +5261,7 @@ interface X12ClaimDate {
  * inpatient only. CMS-mandated values: `Y` Yes, `N` No, `U` Insufficient
  * documentation, `W` Clinically undetermined, `1` Exempt from POA
  * reporting. Verbatim - the parser preserves the value, never validates
- * against the spec list (Phase 9 profile may layer enforcement).
+ * against the spec list (a profile may layer enforcement).
  *
  * @example
  * ```ts
@@ -5361,9 +5374,10 @@ interface X12ClaimMember {
 /**
  * Decoded Loop 2320 - Other Subscriber Information. Captures the SBR-01
  * payer responsibility code and the associated other-subscriber / other-
- * payer NM1 entities; Phase 5 records the surface so a consumer knows
+ * payer NM1 entities; this reader records the surface so a consumer knows
  * COB exists. Detailed CAS / OI / MOA breakdown inside Loop 2320 is
- * deferred to Phase 9 (it tracks one payer's specific adjudication and
+ * deferred to the profile system (it tracks one payer's specific
+ * adjudication and
  * is rarely needed for outbound claim creation).
  *
  * @example
@@ -5673,12 +5687,12 @@ interface X12LineAdjudication {
  * (Institutional), `005010X224A2` (Dental); X12 005010 base spec for
  * envelope + cross-cutting segments (NM1, N3, N4, REF, PER, DTP, AMT).
  *
- * Phase 5 known limitations (documented in CHANGELOG):
+ * Known limitations (documented in CHANGELOG):
  * - **Loop 2320/2330 (Other Subscriber / Other Payer)** captured at the
  *   surface level only: SBR-01 payer responsibility code and the
  *   adjacent NM1*IL / NM1*PR entities. Detailed CAS / OI / MOA
- *   breakdown inside Loop 2320 is deferred to Phase 9 (companion-guide
- *   tolerance).
+ *   breakdown inside Loop 2320 is deferred to the profile system
+ *   (companion-guide tolerance).
  * - **Loop 2410 (Drug Identification, 837P)** captures LIN qualifier +
  *   code and the optional CTP quantity + UCUM unit. REF inside 2410 is
  *   preserved on tx.segments verbatim but not typed onto the model.
@@ -5688,8 +5702,8 @@ interface X12LineAdjudication {
  * - **CN1 contract information** preserved on tx.segments verbatim, not
  *   typed onto the model.
  * - **Companion-guide enforcement** (e.g. Availity's required REF*EA at
- *   the billing provider) deferred to Phase 9 (profile system).
- * - **Builder** (`build837P`/`I`/`D`) deferred to Phase 8.
+ *   the billing provider) deferred to the profile system.
+ * - **Builder** (`build837P`/`I`/`D`) shipped separately.
  *
  * None of these are silent - verbatim segments remain on
  * `tx.segments` so a consumer can drop down to raw element access for
@@ -5722,7 +5736,7 @@ declare const HL_LEVEL_CODES: Readonly<{
  * Loop 2310x / 2420x line-provider verbatim bucket. Frozen for type
  * safety + IntelliSense - consumers should rarely need these (they're a
  * walker-internal vocabulary), but they're exported for tests + the
- * Phase 8 builder API. @example NM1_QUALIFIERS.BILLING_PROVIDER → "85".
+ * builder API. @example NM1_QUALIFIERS.BILLING_PROVIDER → "85".
  */
 declare const NM1_QUALIFIERS: Readonly<{
     readonly SUBMITTER: "41";
@@ -5976,7 +5990,7 @@ interface Build837ReferenceSpec {
  * Note: when used as a claim-level (2310x) or service-line (2420x) provider,
  * only the NM1 fields round-trip through `get837Claims`; an attached
  * `address` / `contacts` / `references` is emitted but the read side does
- * not re-surface it on the provider (a documented Phase 5 read limitation).
+ * not re-surface it on the provider (a documented read limitation).
  *
  * @example
  * ```ts
@@ -6758,8 +6772,8 @@ declare class Claim837BuildError extends Error {
 
 /**
  * 837 TR3 loop specifications - authored through the **public**
- * {@link "../../loops/define.js".defineLoopSpec} API (the Phase 2
- * dogfooding gate: the built-in 837 loop hierarchy goes through the SAME
+ * {@link "../../loops/define.js".defineLoopSpec} API (the dogfooding
+ * gate: the built-in 837 loop hierarchy goes through the SAME
  * factory consumers use for payer-specific companion-guide loops).
  *
  * Three variants share most of the structure; differences are concentrated
@@ -6796,10 +6810,10 @@ declare class Claim837BuildError extends Error {
  *    SE
  * ```
  *
- * Phase 5 surfaces the three loop specs as frozen artifacts (consumers can
+ * The three loop specs are surfaced as frozen artifacts (consumers can
  * read them and assert they match their companion-guide expectations); the
  * walker in `./get-837.ts` consults them to guide its state machine.
- * Phase 9's profile system overlays vendor-specific quirks on top.
+ * The profile system overlays vendor-specific quirks on top.
  */
 
 /**
@@ -7318,7 +7332,7 @@ interface X12EligibilityAddress {
  * captured verbatim onto its enclosing subscriber / dependent so a
  * provider can re-associate the response with the 270 request it sent.
  *
- * Phase 6 known limitations (documented in CHANGELOG):
+ * Known limitations (documented in CHANGELOG):
  * - **AAA request-validation segments** (rejection reasons at the source /
  *   receiver / subscriber level) are preserved on `tx.segments` verbatim
  *   but not yet typed onto the model.
@@ -7929,7 +7943,7 @@ declare class Eligibility271BuildError extends Error {
 /**
  * 271 TR3 `005010X279A1` loop specification - authored through the
  * **public** {@link "../../loops/define.js".defineLoopSpec} API. This is
- * the Phase 6 dogfooding gate: the built-in 271 loop hierarchy goes
+ * the dogfooding gate: the built-in 271 loop hierarchy goes
  * through the SAME factory consumers use for payer-specific companion-
  * guide loops, so a regression in `defineLoopSpec` cannot hide from the
  * built-in extractor.
@@ -7954,7 +7968,7 @@ declare class Eligibility271BuildError extends Error {
  * ```
  *
  * @remarks
- * Phase 6 surfaces the loop spec as a frozen artifact (consumers can read
+ * The loop spec is surfaced as a frozen artifact (consumers can read
  * it and assert it matches their companion-guide expectations); the walker
  * in `./get-271.ts` consults the HL level codes to guide its state
  * machine. Loop 2110C and 2110D share the identical EB-anchored shape - a
@@ -8328,7 +8342,7 @@ interface X12ServiceLineStatus {
  * verbatim value and emit `X12_UNKNOWN_CLAIM_STATUS_CATEGORY` /
  * `X12_UNKNOWN_CLAIM_STATUS`.
  *
- * Phase 6 known limitations (documented in CHANGELOG):
+ * Known limitations (documented in CHANGELOG):
  * - **QTY / AMT** claim-summary segments (claim count / amount roll-ups in
  *   a 277CA Loop 2200) are preserved on `tx.segments` verbatim but not yet
  *   typed onto the model.
@@ -9028,8 +9042,8 @@ declare class ClaimStatus277BuildError extends Error {
 
 /**
  * 277 / 277CA loop specification - authored through the **public**
- * {@link "../../loops/define.js".defineLoopSpec} API (the Phase 6
- * dogfooding gate). The 277 Claim Status Response (`005010X212`) and the
+ * {@link "../../loops/define.js".defineLoopSpec} API (the dogfooding
+ * gate). The 277 Claim Status Response (`005010X212`) and the
  * 277CA Claim Acknowledgment (`005010X214`) share the same HL spine
  * (`20` Information Source → `21` Information Receiver → `19` Service
  * Provider → `22` Subscriber → `23` Dependent) and the same STC-anchored
@@ -10411,7 +10425,7 @@ interface X12EnrollmentAmount {
  * `tx.segments` up front. The memory win is on the RESULT side - a consumer
  * processing a hundreds-of-MB 834 holds one decoded member at a time, not
  * the whole decoded roster. A true file→iterator streaming parser is a v2
- * item (see roadmap Phase 2 streaming invariant).
+ * item.
  *
  * Spec source: WPC TR3 `005010X220A1`.
  */
@@ -11348,7 +11362,7 @@ interface X12AuthDate {
  * {@link "../shared/hl.js".validateHl}; the `EV` / `SS` event + service
  * levels are intentionally tolerant (omitted from the expected-parent map).
  *
- * Phase 7 known limitations (documented in CHANGELOG):
+ * Known limitations (documented in CHANGELOG):
  * - **Detailed 2010E provider sub-loops** (rendering / attending / operating
  *   provider address + secondary IDs) are captured as bare NM1 entities on
  *   {@link X12ServiceReview.providers}, not split by role.
@@ -11993,7 +12007,7 @@ declare class ServicesReview278BuildError extends Error {
 /**
  * 278 TR3 `005010X217` (request) / `005010X216` (response) loop
  * specification - authored through the **public** {@link
- * "../../loops/define.js".defineLoopSpec} API (the Phase 7 dogfooding gate).
+ * "../../loops/define.js".defineLoopSpec} API (the dogfooding gate).
  * The built-in 278 HL hierarchy goes through the SAME factory consumers use
  * for payer-specific companion-guide loops.
  *
@@ -12026,7 +12040,7 @@ declare class ServicesReview278BuildError extends Error {
  * warnings. Detailed sub-loops (PWK attachments, the full 2010E provider
  * family, HSD service-delivery, SV1/SV2/SV3 line detail) are preserved
  * verbatim on `tx.segments` but not yet destructured onto the model - a
- * documented Phase 7 limitation.
+ * documented limitation.
  */
 
 /**
@@ -12399,7 +12413,7 @@ type Ta1AckCode = (typeof TA1_ACK_CODES)[keyof typeof TA1_ACK_CODES];
  * are defined by the standard; values past `028` exist in some standard
  * revisions and are accepted on parse (Postel's Law) but not enumerated
  * here - the parsed model carries the un-narrowed string on `noteCodeRaw`,
- * post-`?`-unescape as of `X12-TA1-RESIDUALS`. **A clause here said "verbatim"
+ * post-`?`-unescape as of a later release. **A clause here said "verbatim"
  * and is deleted rather than reworded**; `raw.elements[5]` is the byte surface.
  *
  * `000` is the canonical "no error" note paired with a `TA1-04 == 'A'`
@@ -12480,14 +12494,14 @@ declare const TA1_NOTE_CODES: {
  * `028` (some revisions extend the list); `parseTA1` exposes the
  * un-narrowed string on `noteCodeRaw` in that case, so the value survives
  * even when the union cannot statically type it. **It is post-`?`-unescape
- * as of `X12-TA1-RESIDUALS`, and a clause here calling it VERBATIM is
+ * as of a later release, and a clause here calling it VERBATIM is
  * deleted rather than reworded** - `raw.elements[5]` is the byte surface.
  */
 type Ta1NoteCode = (typeof TA1_NOTE_CODES)[keyof typeof TA1_NOTE_CODES];
 
 /**
  * Typed-model surface for the X12 acknowledgment transactions surfaced
- * by Phase 3 - `005010X231A1` 999 (Implementation Acknowledgment) and the
+ * by this package - `005010X231A1` 999 (Implementation Acknowledgment) and the
  * envelope-level TA1 (Interchange Acknowledgment).
  *
  * Two kinds of types live here:
@@ -12624,7 +12638,7 @@ interface X12Ack999Ik4 {
  * One IK4 element-level error wrapped with its (optional) IK3-paired CTX
  * context strings - surfaced verbatim because CTX uses a composite syntax
  * the X231A1 implementer typically writes as `ELEMENT*NM1*8*1`. The
- * library does not try to over-decompose the CTX value at this phase.
+ * library does not try to over-decompose the CTX value.
  */
 interface X12Ack999ElementNote {
     readonly ik4: X12Ack999Ik4;
@@ -12706,7 +12720,7 @@ interface X12Ack999 {
  *   ({@link Ta1NoteCode}); `noteCodeRaw` carries the un-narrowed string
  *   alongside so unknown extensions survive. **A clause here said that
  *   string is preserved VERBATIM and is deleted, not reworded:**
- *   `X12-TA1-RESIDUALS` made it post-unescape, and `raw.elements[5]` is
+ *   a later release made it post-unescape, and `raw.elements[5]` is
  *   the verbatim surface.
  * - `noteCodeRaw` - the un-narrowed TA1-05 string. Equal to `noteCode` when
  *   the value is a known I18 code; equal to the decoded inbound text when
@@ -12715,7 +12729,7 @@ interface X12Ack999 {
  *   byte-exact round-trip.
  *
  * **The five decoded fields are POST-`?`-unescape; `raw` is the verbatim
- * byte surface and is not.** `X12-TA1-RESIDUALS` moved the decoded half:
+ * byte surface and is not.** A later release moved the decoded half:
  * before it, a released TA1-01 read back carrying its `?` and matched no
  * ISA-13, while every dot-path read of the same element already unescaped.
  * Read `raw.elements` when you want the bytes.
@@ -12893,7 +12907,7 @@ declare function parse999(raw: string | Buffer, options?: X12ParseOptions): X12A
  * TA1 is NOT a transaction set: per the ASC X12 standard it lives at the
  * envelope level, between ISA and the first GS (or alone inside an
  * ISA..IEA with no GS at all - the "TA1-only interchange" pattern). The
- * Phase 3 envelope walker captures every envelope-level TA1 verbatim onto
+ * envelope walker captures every envelope-level TA1 verbatim onto
  * {@link X12Interchange.ta1Segments}; this function decodes the first
  * one. Multiple TA1 acks for prior interchanges may co-exist on a single
  * inbound - pass `index` to read the Nth, or scan `ta1Segments` directly.
@@ -12979,7 +12993,7 @@ declare function build999(spec: Build999Spec): X12Interchange;
  * safety invariant as `build999`.
  *
  * Returns the typed {@link Ta1Segment} (matching the envelope-level shape
- * the Phase 3 envelope walker surfaces on
+ * the envelope walker surfaces on
  * {@link "../../parser/types.js".X12Interchange.ta1Segments}). Callers that
  * want a complete on-the-wire byte stream concatenate `raw` + a segment
  * terminator, or wrap the segment inside their preferred envelope. The
@@ -13002,7 +13016,7 @@ declare function build999(spec: Build999Spec): X12Interchange;
  * sender never resubmits against.
  *
  * The grounding is inside the package, not in a spec clause, which is the
- * same tiebreak `X12-ENVELOPE-SPLITTER-NOT-RELEASE-AWARE` recorded: one
+ * same tiebreak the envelope splitter fix recorded: one
  * function disagreed with itself. This module emitted bytes that this
  * package's own reader decoded into a different disposition than the one
  * the caller asked for, and every other builder already released the same
@@ -13042,7 +13056,7 @@ declare function build999(spec: Build999Spec): X12Interchange;
  *   through it.** No total is published: that is what was measured, not a
  *   closed account.
  *   **🩺 A CLAUSE NAMING `parseTA1`'s FIELDS AS A THIRD SUCH SURFACE STOOD
- *   HERE AND IS DELETED, NOT REWORDED.** `X12-TA1-RESIDUALS` made those
+ *   HERE AND IS DELETED, NOT REWORDED.** A later release made those
  *   fields post-unescape, so it is measured false; do not restate it.
  * - **A caller who was pre-releasing the value themselves** (the remedy
  *   `KNOWN-LIMITATIONS.md` named while this was open) is now escaping
@@ -13054,14 +13068,14 @@ declare function build999(spec: Build999Spec): X12Interchange;
  * **And an EMPTY control number USED to go out unrefused.** `escapeRelease`
  * early-returns on `""` and this module had no required-field guard, so
  * `interchangeControlNumber: ""` emitted `TA1**260601*1200*A*000` with no
- * error, through `0.0.15`. `X12-EMPTY-CONTROL-NUMBER-FABRICATED` closed it:
+ * error, through `0.0.15`. A later release closed it:
  * see {@link "../../builder/caller-control-number.js".requireControlNumber}.
- * `X12-CONTROL-NUMBER-GUARD-NOT-TYPE-CHECKED` then made the same guard
+ * A later one still then made the same guard
  * type-check, so TA1-01 draws a refusal naming TA1-01 rather than the escaper's
  * one naming only the builder - same class, same code, different words. The
  * guard is still byte-strict, so a whitespace-only TA1-01 still builds.
  *
- * **The other four slots were left open by that slice and `X12-TA1-RESIDUALS`
+ * **The other four slots were left open by that change and a later one
  * closes them.** TA1-01's guard was the only required-field guard this module
  * had, so `interchangeDate`, `interchangeTime`, `ackCode` and `noteCode` each
  * emitted an absent element on `""` with `warnings: []`. **TA1-05's cell has to
@@ -13313,7 +13327,7 @@ declare function serializeX12(interchange: X12Interchange, opts?: SerializeOptio
  * counts), so the caller never hand-counts a segment total or a group total.
  *
  * The domain-specific builders (`build835`, `build837P`, …) sit ON TOP of
- * this primitive in a later phase: each maps its typed domain model down to
+ * this primitive: each maps its typed domain model down to
  * {@link TransactionSetSpec} segment arrays and delegates the envelope to
  * `buildInterchange`. This file is the shared floor they all stand on.
  */
@@ -13495,9 +13509,9 @@ declare function buildInterchange(spec: InterchangeSpec): X12Interchange;
  *
  * ## The names say `BUILD_REFUSAL_*` and the scope is wider than that
  *
- * The two exported constants were introduced by `X12-BUILDER-BOUNDS`, which
- * bounded the `build*` sites only, and they are published under those names.
- * `X12-CALLER-VALUE-RESIDUALS` then routed `src/profiles/validate.ts` through
+ * The two exported constants were introduced by a change that bounded the
+ * `build*` sites only, and they are published under those names. A later one
+ * then routed `src/profiles/validate.ts` through
  * the same renderers, so `X12ProfileError` is bounded by the same numbers.
  * **The names were deliberately NOT changed**: one ceiling under one name
  * cannot drift, whereas a second name for the same number is exactly how two
@@ -13552,7 +13566,7 @@ declare function buildInterchange(spec: InterchangeSpec): X12Interchange;
  *   newline. A refusal message is therefore bounded but not guaranteed to be a
  *   single log line. Escaping was considered and left out: it would expand the
  *   rendered length by up to 6x per character for a hazard the caller creates
- *   in their own data, and this slice makes the claim it can support and no
+ *   in their own data, and this bound makes the claim it can support and no
  *   wider.
  *
  * @see `src/parser/errors.ts` for the parse-side `SNIPPET_MAX_INPUT` bound this
@@ -13823,7 +13837,7 @@ interface X12WarningPartition {
 declare function partitionWarnings(warnings: readonly X12ParseWarning[], profile: X12Profile): X12WarningPartition;
 
 /**
- * Error taxonomy for the `@cosyte/x12` profile subsystem (Phase 9).
+ * Error taxonomy for the `@cosyte/x12` profile subsystem.
  *
  * `X12ProfileError` is thrown by `defineProfile()` when a profile definition
  * is structurally invalid - a bad/missing name, an unknown option key, or a
@@ -13912,7 +13926,7 @@ declare const availity: X12Profile;
 declare const bcbsCommon: X12Profile;
 
 /**
- * Public barrel for the `@cosyte/x12` profile subsystem (Phase 9). Assembles
+ * Public barrel for the `@cosyte/x12` profile subsystem. Assembles
  * the `profiles` namespace object and re-exports the public profile API:
  * `defineProfile`, `setDefaultProfile`, `getDefaultProfile`,
  * `partitionWarnings`, the `X12ProfileError` class, and the supporting types.
@@ -13947,15 +13961,15 @@ declare const profiles: {
 };
 
 /**
- * Public entry point for the `@cosyte/x12` package. Phase 1 lands the
- * envelope decoder (ISA / GS / GE / IEA + delimiter detection); Phase 2+
- * adds segment/element/composite decode, the warning-code registry
- * expansion, and the public `defineLoopSpec`. Per-transaction helpers
- * (`get835`, `get837Claims`, ...) arrive in Phases 4+.
+ * Public entry point for the `@cosyte/x12` package. It lands the envelope
+ * decoder (ISA / GS / GE / IEA + delimiter detection), segment/element/
+ * composite decode, the warning-code registry, and the public
+ * `defineLoopSpec`. Per-transaction helpers
+ * (`get835`, `get837Claims`, ...) sit on top of it.
  */
 /**
- * Library version string, synced with `package.json#version` at build
- * time by downstream phases. Exported now so consumers (and the
+ * Library version string, synced with `package.json#version` by the
+ * release's version step. Exported now so consumers (and the
  * type-check pipeline) have at least one symbol to resolve through the
  * `exports` map.
  *