/**
 * OUTPUT_CONTRACTS data — the proof-set of per-operation OUTPUT contracts.
 *
 * SSoT for the OUTPUT (result) shape of CLEO's highest-traffic operations
 * (DHQ-057 · T11692). Each entry is an {@link OperationOutputContract}: a
 * JSON Schema draft-07 document for the LAFS envelope's `data` payload plus
 * the curated list of valid `--field` JSON pointers.
 *
 * Populated INCREMENTALLY — high-traffic operations first. This is the OUTPUT
 * mirror of `INPUT_CONTRACTS` (which lives in core). The data lives here in
 * `contracts` (a leaf package, zero runtime deps) so every consumer — CLI
 * `--describe`, the SDK `describeOperation`, REST clients — resolves against
 * one source of truth.
 *
 * Each `dataSchema` is grounded in the concrete result interface declared in
 * `./tasks.js` (e.g. {@link TasksShowResult}, {@link MinimalMutateEnvelope}) so
 * the schema can never drift from the typed shape without a compile-time touch
 * to this file.
 *
 * @packageDocumentation
 * @module @cleocode/contracts/operations/output-contracts-data
 *
 * @epic T11679
 * @task T11692 — DHQ-057: per-operation output schema SSoT
 */
import type { OperationOutputContractRegistry } from './output-contract.js';
/**
 * SSoT registry of per-operation OUTPUT contracts, keyed by the canonical
 * `<domain>.<verb>` operation id. Extend this map as operations are migrated
 * to the schema-first OUTPUT surface (high-traffic first).
 *
 * @task T11692
 */
export declare const OUTPUT_CONTRACTS: OperationOutputContractRegistry;
//# sourceMappingURL=output-contracts-data.d.ts.map