Convenience helpers for constructing domain types.

Official JV-Data code table identifiers; widths refer to bytes, including spaces.

The functional API always connects to COM. Test doubles are injected only through internal test boundaries.

Pure acquisition metadata from the SDK's data-type list and JVOpen contract.

Retains the failing API and original code; explanatory text is not a transport diagnosis. SDK -413 can occur independently of Xanthos and does not imply retryability or an observed HTTP status. See docs/sdk-known-limitations.md (SDK-COM-413).

Original SDK code or HRESULT is retained independently of explanatory text.

Synchronous SDK operations. COM executes on the session's STA; UI calls wait for the user's choice.

A recognized code has a label; an unrecognized code retains its exact representation.

JV-Link timestamps are local Japanese race-service times, with no implicit UTC conversion.

Owned raw bytes and all read out-values; decoding is an explicit separate operation.

JVRTOpen has no file-count or timestamp out-parameters.

Strict, byte-oriented primitives shared by official record readers.

Lossless envelope. Reading a header does not certify the remaining record layout.

Header codes are preserved; data-category meanings depend on the record type.

Meanings from the official format list; H5 is not an official record identifier.

Positions are one-based byte offsets in the original record.

Official record projection. Raw bytes remain available on every successful result.

Explicit ownership of one COM instance. Dispose releases it; closeData only closes its data session.

Owned event registration. Public functions expose shutdown and asynchronous delivery errors.