/**
 * Derive `VersionedInputs` from a stored report record.
 *
 * Shared by both diagnosis emission paths — the `ailf interpret` command and
 * the post-pipeline summary hook (`runPostPipelineHooks`) — so they build
 * identical version metadata. Co-locating the logic here is the durable fix
 * for W0286: the two paths previously inlined separate copies that drifted,
 * and the hook copy coalesced every axis to the literal `"unknown"`.
 *
 * The path-relevant axes fall back to the canonical engine constants, NEVER
 * `"unknown"`. `diagnosisVersion` is the visible provenance slug in the
 * diagnosis artifact path (`diagnosis-{diagnosisVersion}-{hash}.json`); a
 * `"unknown"` slug erases the signal that path is meant to carry. `cardVersion`
 * feeds the path's content hash and the cache key, so it must also be the real
 * registry version for cache identity to be correct.
 *
 * The two non-path axes (`graderJudgmentsVersion`, `ensembleVersion`) have no
 * canonical version source today and fall back to `"unknown"`; they affect only
 * the cache key, not the artifact path. Wiring them to real sources is out of
 * scope for W0286.
 */
import { type VersionedInputs } from "../../_vendor/ailf-core/index.d.ts";
/**
 * The four-version chain is carried in `report.summary.versions` per the
 * Phase 5 schema. When a field is absent (legacy reports, or any report
 * produced before version metadata was populated), the path-relevant axes
 * resolve to the canonical constants and the rest to `"unknown"`.
 */
export declare function defaultVersionsFromReport(report: unknown): VersionedInputs;
