/**
 * Compile-time-only type-accuracy check for `OrderItem.estimatedDelivery` —
 * the delivery estimate the buyer was shown at checkout, frozen onto the order
 * item (API 2026-08-21, migration 0278).
 *
 * Same pattern as types.reorder.typecheck.ts: no runtime assertions, never
 * imported by index.ts — `bun:test` won't pick it up (the name doesn't match
 * `*.test.ts`) and `bun build` won't bundle it, but `tsc --noEmit` /
 * `tsc --emitDeclarationOnly` fails loudly if the type drifts from the wire.
 *
 * What is pinned here, and WHY:
 *
 *  - THREE states, not two. `string` = show it; `null` = the API knows about
 *    the field and has nothing to show (a pre-0278 order, or a line with no
 *    supplier product — SuperPass / robux-via-pass); ABSENT = an API
 *    deployment older than the field. Making it required would break every
 *    legacy-shaped literal AND tell callers an estimate is always there.
 *
 *  - `string`, not a structured `{p50, p90}`. The top of the resolution chain
 *    is `supplier_products.estimated_delivery_override` — free-form operator
 *    copy with no structural form at all — so the wire carries a FINISHED,
 *    already-localized sentence. A caller that tries to parse minutes back out
 *    of it is reading operator prose; this fixture exists so a future "let's
 *    make it structured" edit has to change the SDK type deliberately.
 */
export {};