/** * GENERATED FILE — DO NOT EDIT BY HAND. * * Regenerate with: `node scripts/generate-minimax-vision-revisions.mjs`. * The prebuild step in `packages/scoutline/package.json` runs the * generator before `tsc`, so this file is always fresh when the * TypeScript compiler runs. * * Each value is a SHA-256 digest covering the Implementation ID * (`scoutline-direct@0.5.0`), the stable common mapping runtime * (`vision-mappings/common.ts`), only that operation's mapping Module * under `vision-mappings/`, the fixture image bytes, the canonical * request fields, and the exact required assertion IDs. Adding another * operation does not change an existing operation's revision; changing * the common runtime intentionally changes every revision. * * The Implementation ID participates in every revision digest, so * bumping it (e.g. critique C3 swapping the SDK-backed runtime for * the Scoutline direct transport) regenerates the entire map. Any * shipped attestation that pins `mappingRevision` must be re-issued * against the new revisions before the registry will accept it * (see `scripts/attest-minimax-vision.mjs`). * * Operations without a mapping Module carry the placeholder * `"pending-no-mapping-module"` until P5-03 creates their Module. */ import type { SpecializedVisionOperation } from "./vision-conformance.js"; export declare const MINIMAX_VISION_MAPPING_REVISIONS: Readonly>; //# sourceMappingURL=vision-revisions.d.ts.map