/**
 * API Service Gateway request envelope types.
 *
 * These types describe the HTTP request bodies the API gateway accepts on
 * its public-facing routes. They live in core (not in packages/api/src/) so
 * the gateway's Zod validators can `satisfies z.ZodType<...>` against them
 * — making the parse-output → domain-type contract a compile-time gate
 * rather than a runtime assumption (D0045 / W0187).
 *
 * The shapes here are intentionally a LOOSE subset of the canonical domain
 * types they relate to:
 *
 *   - `ValidateConfigRequest.config` overlaps with `ModelsConfig`, but the
 *     API surface accepts string[] for modes (not branded EvalMode[]) and
 *     all fields are optional. This is a deliberate gateway contract — the
 *     route's job is to validate the user's input, not to require a fully
 *     domain-shaped payload.
 *   - `ValidateTaskDef` overlaps with `GeneralizedTaskDefinition` but uses
 *     the older flat shape (`featureArea`, `canonicalDocs`) instead of the
 *     mode-discriminated union. Harmonizing these is tracked separately —
 *     out of scope for W0187.
 *
 * Any fields not on these types are rejected by the gateway's validators
 * and won't reach domain code; the satisfies clause is what pins that
 * contract in place.
 */
export {};
