/**
 * Dispatch operation-def contracts.
 *
 * Canonical home for the {@link OperationDef} and {@link Resolution}
 * interfaces that describe a single dispatchable CQRS operation and the
 * result of resolving one from the operation registry.
 *
 * Promoted to `@cleocode/contracts` in Phase 0b of the SG-ARCH-SOLID Saga
 * (T9831 · E-CONTRACTS-FOUNDATION T9832 · T9954). Originally defined in
 * `packages/cleo/src/dispatch/registry.ts` (lines 14-41 / 43-53). The
 * `packages/cleo` definition is now a re-export shim — every consumer of
 * `OperationDef` / `Resolution` continues to compile unchanged.
 *
 * This promotion unblocks E-CLI-BOUNDARY (T9833) — the registry data
 * relocation can now move {@link OPERATIONS} into `@cleocode/contracts`
 * (or split it without changing the type's canonical home) without
 * crossing a circular dependency.
 *
 * NOT promoted (intentional — different concern):
 *   - `OPERATIONS: OperationDef[]` — the registry data itself remains in
 *     `packages/cleo/src/dispatch/registry.ts` and is the subject of the
 *     follow-up E-CLI-BOUNDARY epic.
 *   - The helper functions (`resolve`, `validateRequiredParams`,
 *     `getByDomain`, `getByGateway`, `getByTier`, `getActiveDomains`,
 *     `getCounts`, `deriveGatewayMatrix`, `getGatewayDomains`) — they
 *     operate on the data and remain colocated with it.
 *
 * @since SG-ARCH-SOLID Saga T9831 · E-CONTRACTS-FOUNDATION T9832 · T9954 (Phase 0b)
 */
export {};
//# sourceMappingURL=operation-def.js.map