@cosyte/hl7 0.0.2 → 0.0.3

package/CHANGELOG.md

@@ -15,6 +15,129 @@ per the cosyte version ladder (`0.0.x` until first alpha).
 
 ### Added
 
+- **The published JSDoc is swept, and `src/` doc comments are gated
+  (`pnpm check:no-internal-refs` third pass; `PUBLIC-SURFACE-HYGIENE`).** Doc comments compile
+  into `dist/index.d.ts` and `dist/index.d.cts`, `dist` is the first entry in `files`, and every
+  `npm i @cosyte/hl7` receives them, so what a consumer's editor renders on hover is public
+  surface and the founder directive of 2026-07-27 applies to it. Re-measured with the shipped
+  rules before the change: **293 distinct lines** across tracked `src/*.ts` (253 phase-rule, 39
+  identifier-rule, 5 ADR, 1 jargon, 1 traceability marker), of which a local build carried
+  **164 distinct lines into `dist/index.d.ts`** (137 phase-rule, 22 identifier-rule, 5 ADR,
+  1 jargon, 1 traceability). After: **0 on every rule, in `src/` doc comments and in both built
+  declaration files.** A consumer hovering `parseHL7`, `defineProfile`, `Medication` or
+  `buildMessage` no longer reads which internal phase built it. Every `Plan N` build-order
+  reference was swept in the same pass, by hand, and **the built declaration file now carries
+  none**: no rule catches them, and they contradicted the `CLAUDE.md` sentence this change adds.
+  For scale, the base commit's build carried 28 such lines, from 61 doc-comment lines in `src/`.
+
+  **Identifiers were translated, never deleted, and no public export lost its documentation.**
+  That is measured, not asserted: the built `dist/index.d.ts` carries **691 doc-comment blocks,
+  633 documented declarations and 237 `@example` blocks before and after, and the sorted list of
+  documented declaration names is byte-identical.** Heads left behind by a front-of-line strip
+  were repaired: nine composite parsers wrapped `HL7-VALUE-REDECODE)` onto a continuation line,
+  where a naive strip leaves `). Absent / empty components are OMITTED`.
+
+  **Stripping the framing exposed a false claim on a published API, which is the argument for
+  doing this at all.** `defineProfile`'s doc block in `dist/index.d.ts` told consumers that
+  `opts.extends` was "ACCEPTED but IGNORED, resulting in `lineage === [opts.name]` regardless".
+  The implementation merges parents (lineage, `dateFormats`, `customSegments`, `description`,
+  composed `onWarning`) and re-validates the merged result. The text now describes what the
+  function does. Four sibling claims of the same kind were also stale and are gone: `emitMessage`,
+  `emitPrettyPrint`, `emitJson` and `buildMessage` were each documented as an unimplemented stub
+  ("Stub throws", "Implementation lives in..."), and all four have been implemented for some time.
+  Internal framing is where stale claims hide, which is why this is a correctness change and not
+  a tidying one.
+
+  **The gate now has a third pass** with its own rule array, its own extractor and its own
+  positive/negative self-tests written in the language of source rather than markdown. It scans
+  `/** */` text only, line by line and again over the block reflowed the way a hover tooltip
+  reflows it, because multi-token rules are blind to a violation that straddles a wrap and this
+  package wraps its doc comments. `//` and `/* */` comments are deliberately **not** covered and
+  keep their identifiers: they do not reach `dist` (checked both directions), and the convention
+  names source comments as a place identifiers belong. 61 such lines remain in `src/` by choice.
+
+  Every claim above was checked RED against a seeded violation rather than assumed: a single-line
+  violation in an exported function's JSDoc; a violation split across a wrap that a line-only
+  grep scores 0 on; the same bookkeeping in a `//` comment staying green; widening the source
+  identifier rule to the `WORD-N` shape failing its own negative self-test naming `MSH-2`; an
+  extractor that strips the comment leader before testing the terminator reporting 66 false hits
+  on a clean tree; and an extractor that yields nothing refusing to report green.
+
+  **The ceiling is stated rather than implied shut, and "0 on all six rules" is a statement about
+  these rules, not about the founder's rule.** Measured on the built `dist/index.d.ts`, what still
+  ships is **144 lines carrying `D-NN` internal decision numbers** and **51 lines carrying item
+  identifiers from nine prefixes the list does not hold** (`HELPERS` 14, `BIP` 15, `PROF` 8,
+  `SER` 6, `MODEL` 4, `PARSE`, `WR`, `TOL`, `TYPES` 1 each). `D-NN` is the deliberate
+  non-catch it has always been, because legacy SNOMED RT codes are axis-prefixed in exactly that
+  shape (`D-13000`, `T-32000`, `M-80003`). The item identifiers need new prefixes added to the
+  list, which is a **rule** change needing its own negative self-tests (`SER`, `WR`, `TOL` and
+  `BIP` are exactly the short generic tokens that made `PKG` unsafe), so it is not smuggled in on
+  the back of a prose sweep. Separately, `dist/` is untracked build output, so no checked-in gate
+  can read it: this gates dist's _source_, which holds only because the dts build copies doc text
+  verbatim, and the `164` figure is a hand-taken snapshot. Two "the per-X slice of Y" false
+  positives, where `slice` means portion, were fixed by rewording rather than by narrowing the
+  rule.
+
+  Documentation, tooling and CI only. No change to the published package surface, parser
+  behavior, or warning codes.
+
+- **Public-surface hygiene gate in CI (`scripts/check-no-internal-refs.sh`,
+  `pnpm check:no-internal-refs`, `.github/workflows/no-internal-refs.yml`;
+  `PUBLIC-SURFACE-HYGIENE`).** Founder directive of 2026-07-27: no internal project bookkeeping on
+  any surface a consumer reads. The remediation half of that directive was a sweep of 149 references
+  across 11 repos, and a sweep regresses the first time someone writes `(CCDA-P8)` into a README, so
+  the deliverable here is the gate; the sweep rides along. **50 violating lines across 15
+  `docs-content/` pages were cleared** (re-measured with the shipped rules against the previous tree;
+  the backlog's count of 44 was markdown-only and predates two of the rules): phase identifiers in
+  page titles and headings, `HL7-N` / `HL7-J` / `HL7-ESC` / `HL7-R` / `VERIFY-AT-BUILD` item
+  identifiers, a citation of `operations/roadmaps/hl7.md`, bracketed spec-trace tags (`[S-NTE]`,
+  `[S-DTM-IMPL]`), an "Open-question #12", and review-process commentary ("All confirmed 3-0
+  (pass 5)", "all verified 3-0 in the research pass", "Assumption logged"). One more, in `README.md`,
+  was fixed by hand and is caught by no rule: a pointer to "the roadmap's known-limitations", a file
+  the reader does not have. Identifiers were translated at the boundary, not merely deleted, and
+  every head left behind by a front-of-line strip was repaired: a heading cut to `: datetime
+precision` reads worse than the text it replaced. The datetime page needed more than a strip: with
+  its phase framing gone it read as documentation of shipped behaviour while still describing, in the
+  present tense, a `parseHl7TsDtm` zero-fill defect that no longer exists in the library (the API it
+  planned has shipped). It is now written as what the package does, its unexecuted plan and test
+  bookkeeping are gone, and a provenance claim that survived the strip in a stronger form than the
+  original ("all verified against primary Ch. 2A") is removed rather than reworded. The detection
+  rules are lifted
+  from `cosyte/.github` `scripts/release-notes.mjs`, which is already tested byte-for-byte against
+  the 14 published release bodies, and they are **keyed on known project prefixes, never on the
+  `WORD-N` shape**: `MSH-2`, `PID-3`, `OBX-5`, `TQ1-7`, `NM1-03`, `PKG-4`, `ICD-10-CM`, `HL7-V2`,
+  `FHIR-R4`, `DICOM-SR`, `NCPDP-SCRIPT`, `FHIR-bridge`, `HL7-defined` and the four `CSP`
+  Clinical Study **Phase** field names are the reference material an HL7 parser's docs exist to
+  provide, and a shape rule deletes them. That is asserted, not assumed: the script carries a
+  **negative** self-test per rule, built from that material, alongside the positive one, so widening
+  a rule into the `WORD-N` shape reds the gate instead of silently corrupting a segment reference on
+  the next sweep. Where a rule could not be guarded it was **cut** instead: `phase` after a
+  determiner ("the non-goals of this phase") is not detected at all, because catching it also caught
+  "the phase of the clinical study" and "the phase of illness", and when the collision is
+  with clinical reference material the reference material wins. The scan harness is the em-dash gate's,
+  in mllp's variant: scan list built and `./`-prefixed in one loop so the scan stays a single command
+  with stderr bound to all of it, no `sed -z`, no `-d skip`, no `-I`, `-e`/`--`, `-0 -r`, and a
+  refusal to print OK from an empty list, an unreadable input, a non-regular-file entry, or any
+  scanner stderr. Every one of those routes was checked RED against a seeded violation rather than
+  inherited. **Every rule is also applied a second time to paragraph-joined text**, because the rules
+  are multi-token and this repo hard-wraps markdown: a violation straddling a wrap was invisible to a
+  line scan and one was live (`A future phase` / `may add opt-in decode`, with the gate printing OK).
+  The join squeezes whitespace the way markdown does, which is load-bearing rather than cosmetic: a
+  verbatim join leaves the continuation line's indentation in place, and about 600 lines of
+  `docs-content/` start indented, so the pass would have missed the dominant wrap shape while
+  reporting that it ran.
+  It scans the public surface only (`README.md`, `TRADEMARKS.md`, `LICENSE`, `docs-content/`, and the
+  npm `description` and `keywords`) because the same identifier is required on the inside:
+  `CHANGELOG.md`, `.changeset/`, commits and PRs are where it belongs. A tripwire refuses the run if
+  `package.json`'s `files` starts shipping anything the gate does not cover. **Three holes are measured and disclosed rather than implied
+  shut:** `dist/` ships the compiled JSDoc, and the tracked `src/*.ts` files carry 253 phase-rule and
+  39 identifier-rule lines, of which a local build puts 137 and 22 into `dist/index.d.ts` for every
+  consumer's editor to render, unswept and ungated here because remediating ~290 source doc comments
+  is its own reviewable change (**that change is the entry above, which swept them and added the
+  third pass**; `dist/` is untracked, so no checked-in gate can re-derive that figure without
+  building first, and that part is still true); determiner-plus-`phase` is not detected, by choice;
+  and the rules catch identifiers, not English sentences about our process. Documentation and CI only: no change to the
+  published package surface, parser behavior, or warning codes.
 - **Em-dash brand gate in CI (`scripts/check-no-emdash.sh`, `pnpm check:no-emdash`,
   `.github/workflows/no-emdash.yml`; `EMDASH-CONFORMANCE` part 1).** The founder directive of
   2026-07-24 (`knowledgebase/06-brand/voice-and-tone.md`) bans `U+2014` outright across every cosyte

package/README.md

@@ -251,7 +251,7 @@ for (const charge of parseHL7(raw).charges()) {
 }
 ```
 
-These are **breadth** helpers: they surface the common trigger events' core fields, not a scheduling-workflow state machine, signature verification, or a claims/pricing engine (see the roadmap's known-limitations).
+These are **breadth** helpers: they surface the common trigger events' core fields, not a scheduling-workflow state machine, signature verification, or a claims/pricing engine (see the known limitations in the docs).
 
 ### Order & medication timing
 

package/dist/index.cjs

@@ -38,7 +38,7 @@ var ProfileDefinitionError = class extends Error {
   profileName;
   /**
    * Construct a new `ProfileDefinitionError`. `profileName` is optional so
-   * Phase 6 callers may omit it when the offending profile cannot be named
+   * callers may omit it when the offending profile cannot be named
    * (e.g. during initial validation before a name is parsed).
    *
    * @internal
@@ -1863,11 +1863,11 @@ var Field = class {
   isNull;
   /** Reference to the underlying `RawField.repetitions` (no defensive copy). */
   repetitions;
-  /** The 5 encoding characters for this message. Exposed for composite parsers (Plan 04). @internal */
+  /** The 5 encoding characters for this message. Exposed for composite parsers. @internal */
   enc;
   /** Position of this field in the parent message: used for position-aware error messages. @internal */
   position;
-  /** The full `RawField` this wrapper wraps. Exposed for composite parsers (Plan 02/03/04). @internal */
+  /** The full `RawField` this wrapper wraps. Exposed for composite parsers. @internal */
   raw;
   /**
    * Construct a new `Field`. Called internally by `Segment.field(n)`; user
@@ -1884,7 +1884,7 @@ var Field = class {
   /**
    * First-repetition, first-component, first-subcomponent value as a decoded
    * string: unescaped ONCE by the tokenizer on parse, returned verbatim here
-   * (never re-unescaped, HL7-VALUE-REDECODE). Returns `""` when the field is
+   * (never re-unescaped). Returns `""` when the field is
    * empty or HL7 null. Equivalent to `msg.get('SEG.N')` for a top-level access.
    *
    * @example
@@ -1915,7 +1915,7 @@ var Field = class {
    * vendor-quirk control id containing an unescaped delimiter (`ID^X`) must
    * not be truncated to its first component.
    *
-   * **Byte-verbatim for parsed content (HL7-ESC).** The parse pipeline stores
+   * **Byte-verbatim for parsed content.** The parse pipeline stores
    * *decoded* content, but also records the original wire bytes of any escape
    * whose decode is not byte-faithful (`RawComponent.rawSubcomponents`), so
    * re-serialization preserves the sender's exact escape bytes: hex escapes
@@ -2169,7 +2169,7 @@ var Segment = class {
   enc;
   /** Absolute index of this segment in `Hl7Message.rawSegments[]`. Used for position tracking. @internal */
   absoluteIndex;
-  /** The full `RawSegment` this wrapper wraps. Exposed for mutation methods (Plan 04). @internal */
+  /** The full `RawSegment` this wrapper wraps. Exposed for mutation methods. @internal */
   raw;
   /**
    * Lookup map from profile-declared field name → 1-indexed HL7 position.
@@ -2186,7 +2186,7 @@ var Segment = class {
    * should obtain `Segment` instances via `msg.segments(type)` or
    * `msg.allSegments()`.
    *
-   * The optional `customFields` parameter is the per-segment slice of the
+   * The optional `customFields` parameter is the per-segment portion of the
    * applied profile's merged `customSegments` map (PROF-07 / D-16). When
    * supplied, `get(name)` resolves names against it; otherwise `get(name)`
    * always returns `undefined`.
@@ -3881,8 +3881,7 @@ var Hl7Message = class {
    * Raw positional tree produced by the parser. 1-indexed per HL7 convention
    * (`fields[0]` is the segment-name / MSH separator placeholder slot). Use
    * `segments(type)` / `allSegments()` for typed wrapper access: this field
-   * is exposed for advanced callers that need the raw tree directly (e.g.
-   * future serialization phase 5).
+   * is exposed for advanced callers that need the raw tree directly.
    */
   rawSegments;
   encodingCharacters;
@@ -3898,7 +3897,7 @@ var Hl7Message = class {
   dateFormats;
   /**
    * Merged `customSegments` map from the applied profile, stored so
-   * `allSegments()` can hand per-segment slices to `Segment` constructors
+   * `allSegments()` can hand per-segment portions to `Segment` constructors
    * (D-16). Undefined when no profile was applied.
    * @internal
    */
@@ -3907,40 +3906,40 @@ var Hl7Message = class {
    * Lazily built cache of Segment wrappers keyed by segment type. Built on
    * first `segments(type)` call and filtered from `_allSegments` so
    * individual Segment instances are identical across both caches (D-11).
-   * Plan 04 mutation methods drop this cache wholesale.
+   * The mutation methods drop this cache wholesale.
    * @internal
    */
   _segmentsByType;
   /**
    * Lazily built cache of every Segment wrapper in document order. Built on
-   * first `segments(type)` / `allSegments()` call. Plan 04 mutation methods
+   * first `segments(type)` / `allSegments()` call. The mutation methods
    * drop this cache wholesale.
    * @internal
    */
   _allSegments;
   /**
-   * Lazily built `Meta` view (Phase 4 D-02 memoization). Dropped wholesale
+   * Lazily built `Meta` view (memoized). Dropped wholesale
    * by `invalidateCaches`. `Meta` is always defined (D-03: MSH absence
    * throws `NO_MSH_SEGMENT` at parse time) so no null-sentinel is needed.
    * @internal
    */
   _meta;
   /**
-   * Lazily built `MessageStructure` view (Phase G). Dropped wholesale by
+   * Lazily built `MessageStructure` view. Dropped wholesale by
    * `invalidateCaches`. Always defined: `analyzeMessageStructure` returns an
    * `recognized: false` summary for unmodelled types rather than absence.
    * @internal
    */
   _structure;
   /**
-   * Lazily built `Patient | undefined` view (Phase 4 D-02 memoization). Uses
+   * Lazily built `Patient | undefined` view (memoized). Uses
    * a null-sentinel cache because `undefined` means "not yet computed" while
    * `null` means "computed, absent". D-04: no PID → public value `undefined`.
    * @internal
    */
   _patient;
   /**
-   * Lazily built `Visit | undefined` view (Phase 4 D-02 memoization). Same
+   * Lazily built `Visit | undefined` view (memoized). Same
    * null-sentinel convention as `_patient`. HELPERS-03: no PV1 → public
    * value `undefined`.
    * @internal
@@ -3964,8 +3963,8 @@ var Hl7Message = class {
   }
   /**
    * Resolve a dot-path (e.g. `PID.5.1`, `OBX[2].5`, `PID.3[0].1`) to its
-   * decoded leaf string (unescaped once at parse: never re-unescaped on read,
-   * HL7-VALUE-REDECODE). Returns `undefined` when the path doesn't
+   * decoded leaf string (unescaped once at parse: never re-unescaped on
+   * read). Returns `undefined` when the path doesn't
    * resolve: never throws on missing path (MODEL-05). Throws `TypeError`
    * on malformed path syntax (e.g. `"pid.5"`, empty string).
    *
@@ -4000,7 +3999,7 @@ var Hl7Message = class {
    * Return the cached array of `Segment` wrappers for `segmentType` in
    * document order. The returned array identity and the individual Segment
    * instances are both stable across calls (D-11). Invalidated wholesale
-   * by Plan 04 mutation methods.
+   * by the mutation methods.
    *
    * @example
    * ```ts
@@ -4023,7 +4022,7 @@ var Hl7Message = class {
    * Iterate every `Segment` in document order (MSH first, then every
    * subsequent segment). Cached per-message; same array reference and same
    * Segment instances on repeat calls (D-11). Invalidated wholesale by
-   * Plan 04 mutation methods.
+   * the mutation methods.
    *
    * @example
    * ```ts
@@ -4057,7 +4056,7 @@ var Hl7Message = class {
    * @example
    * ```ts
    * console.log(msg.meta.type);                     // "ADT^A01"
-   * console.log(msg.meta.timestamp?.raw);           // fidelity TS (Phase N)
+   * console.log(msg.meta.timestamp?.raw);           // fidelity TS
    * console.log(msg.meta.controlId);                // "MSG001"
    * ```
    */
@@ -4065,8 +4064,8 @@ var Hl7Message = class {
     return this._meta ??= buildMeta(this);
   }
   /**
-   * Structural-conformance summary for the common message types (roadmap
-   * Phase G): a misroute/truncation safety net, NOT a conformance validator.
+   * Structural-conformance summary for the common message types: a
+   * misroute/truncation safety net, NOT a conformance validator.
    * Reports, per the message's recognized (MSH-9.1, MSH-9.2) type, which
    * Required segment groups are present and which are entirely absent
    * (`missingGroups`: the same set the parser flags as
@@ -4134,7 +4133,7 @@ var Hl7Message = class {
   }
   /**
    * Every OBR as an Order with its OBX children grouped positionally (D-12) and
-   * its TQ1 / legacy embedded-TQ (ORC-7) `timings` (Phase M: the repeat pattern
+   * its TQ1 / legacy embedded-TQ (ORC-7) `timings` (the repeat pattern is
    * surfaced verbatim, never resolved to a schedule). D-05: returns `[]` when no
    * OBR present. D-06: not memoized.
    *
@@ -4150,7 +4149,7 @@ var Hl7Message = class {
     return orders(this);
   }
   /**
-   * Message-level NTE notes (Phase P): every NTE segment with no recognized
+   * Message-level NTE notes: every NTE segment with no recognized
    * preceding parent (not immediately following a `PID`, `ORC`, `OBR`, or
    * `OBX`), surfaced verbatim in document order so nothing is dropped. Notes
    * that DO attach to a specific patient / order / result are exposed on those
@@ -4167,7 +4166,7 @@ var Hl7Message = class {
   }
   /**
    * Every recognized ADT patient-identity event (merge / move / link /
-   * unlink / person add/update: roadmap Phase K), with the MRG-sourced
+   * unlink / person add/update), with the MRG-sourced
    * `prior` and PID/PV1-sourced `surviving` parties labelled by role and the
    * spec-constant `direction: "MRG_TO_PID"` on merge/move events. Returns
    * `[]` when the trigger event is not in the identity family. D-06: not
@@ -4188,13 +4187,13 @@ var Hl7Message = class {
   }
   /**
    * Every RXO/RXE/RXD/RXA as a typed `Medication`, with RXR (route) and RXC
-   * (component) segments grouped positionally under their parent (Phase D,
-   * P0 safety). D-05: returns `[]` when no RX* parent present. D-06: not
-   * memoized. The give *amount* and give *strength* are surfaced separately
-   * and never reconciled (Phase D §4).
+   * (component) segments grouped positionally under their parent. D-05:
+   * returns `[]` when no RX* parent present. D-06: not memoized. The give
+   * *amount* and give *strength* are surfaced separately and never
+   * reconciled.
    *
    * Each medication also carries its TQ1 / legacy embedded-TQ (RXE-1) `timings`
-   * (Phase M: repeat pattern verbatim, never resolved to a schedule).
+   * (repeat pattern verbatim, never resolved to a schedule).
    *
    * @example
    * ```ts
@@ -4211,7 +4210,7 @@ var Hl7Message = class {
   /**
    * Every RXA of a VXU^V04 as a typed `Immunization`, with RXR (route/site)
    * and OBX children grouped positionally under the RXA and `orderControl`
-   * from the preceding ORC of the VXU order group (Phase E, P0 safety). D-05:
+   * from the preceding ORC of the VXU order group. D-05:
    * returns `[]` when no RXA present. D-06: not memoized. The vaccine code
    * carries its own provenance; the action code (RXA-21) is surfaced verbatim
    * and `recordOrigin` (administered vs historical) is derived only from the
@@ -4279,7 +4278,7 @@ var Hl7Message = class {
     return insurance(this);
   }
   /**
-   * Every SCH of an SIU message as a typed `Appointment` (roadmap Phase Q), with
+   * Every SCH of an SIU message as a typed `Appointment`, with
    * the AIS/AIG/AIL/AIP resource segments that follow it grouped positionally
    * under that SCH. Surfaces the placer/filler appointment ids, SCH-25 filler
    * status (Table 0278), SCH-11 start/end timing, and the resource groups
@@ -4299,7 +4298,7 @@ var Hl7Message = class {
     return appointments(this);
   }
   /**
-   * Every TXA of an MDM message as a typed `ClinicalDocument` (roadmap Phase Q),
+   * Every TXA of an MDM message as a typed `ClinicalDocument`,
    * with the OBX narrative body grouped positionally under that TXA. The
    * completion status (TXA-17) and availability status (TXA-19) are surfaced as
    * **distinct** fields and never conflated: a document can be available before
@@ -4319,7 +4318,7 @@ var Hl7Message = class {
     return documents(this);
   }
   /**
-   * Every FT1 of a DFT message as a typed `Charge` (roadmap Phase Q), one per
+   * Every FT1 of a DFT message as a typed `Charge`, one per
    * FT1 in document order. Surfaces billing-critical fields (FT1-6 transaction
    * type, FT1-7 code, FT1-11/12 extended/unit amount, FT1-19 diagnosis linkage)
    * with **no billing logic and no money-as-float**: amounts are the verbatim
@@ -4413,7 +4412,7 @@ var Hl7Message = class {
    * `TypeError` with an actionable message otherwise).
    *
    * The value is accepted verbatim: unescaped delimiter characters are NOT
-   * rejected on input (D-18). Re-escaping on serialize is Phase 5's concern.
+   * rejected on input (D-18). Re-escaping is the serializer's concern.
    *
    * MSH-1 / MSH-2 follow the user-facing HL7 convention: `setField("MSH.3", ...)`
    * targets MSH-3 (sending application), matching `msg.get("MSH.3")`.
@@ -4499,11 +4498,11 @@ var Hl7Message = class {
     return this;
   }
   /**
-   * Set a **typed composite** at a field (or field-repetition) dot-path,
-   * roadmap Phase T, the conservative-emit mirror of the typed read accessors
+   * Set a **typed composite** at a field (or field-repetition) dot-path:
+   * the conservative-emit mirror of the typed read accessors
    * (`asXpn`/`asCx`/…). The caller passes a structured value (an XPN name, a CX
    * identifier, a TS timestamp, …) by its {@link CompositeKind}, and the setter
-   * encodes it into a spec-clean field using the HL7-R encode-safe path: any
+   * encodes it into a spec-clean field using the encode-safe path: any
    * delimiter embedded in a component value is **escaped, never injected**, so
    * a `familyName` of `"Smith^Jr"` re-parses to exactly that string rather than
    * forging a component boundary. No hand-assembly of `^`/`&`/`~`.
@@ -4694,8 +4693,8 @@ var Hl7Message = class {
     return this;
   }
   /**
-   * Drop every wrapper AND helper cache wholesale (Phase 3 D-17 + Phase 4
-   * D-02). Called by every mutation method so subsequent `segments(type)` /
+   * Drop every wrapper AND helper cache wholesale (D-17 + D-02). Called by
+   * every mutation method so subsequent `segments(type)` /
    * `allSegments()` / `meta` / `patient` / `visit` reads rebuild from the
    * mutated `rawSegments` tree.
    * @internal
@@ -6809,7 +6808,7 @@ async function* parseStream(source, optionsOrProfile) {
 }
 
 // src/index.ts
-var VERSION = "0.0.2";
+var VERSION = "0.0.3";
 
 exports.ACK_CODES = ACK_CODES;
 exports.ACK_CONDITIONS = ACK_CONDITIONS;