import { VerifyOptions, VerifyResult } from '../helpers/types.js';
/**
 * Run a non-destructive round-trip check directly against the user's repo. For every parent
 * metadata XML file belonging to the requested (or manifest-filtered) metadata types, disassemble
 * + reassemble it inside an isolated temp directory (via `verifyXmlRoundtrip`, which never touches
 * the real file) and compare the reconstructed XML against the original.
 *
 * Unlike a real decompose/recompose run, this never writes to the user's working tree at all --
 * `verifyXmlRoundtrip` owns its own temp-directory isolation per file, so there is no scratch
 * project to build or clean up here.
 *
 * The returned `drift` array is empty when every parent XML would survive the round trip
 * semantically; otherwise each entry names the offending file (relative to its package directory)
 * and a short reason. `reordered` is informational only -- sibling/attribute order is not
 * preserved by design, and Salesforce treats metadata as order-agnostic.
 */
export declare function verifyMetadataTypes(options: VerifyOptions): Promise<VerifyResult>;