/**
 * PD Config Override Provenance Tests — PRI-637
 *
 * Feature flag config lifecycle: a config override may carry `source` metadata
 * (`owner` | `system`); absence means LEGACY_UNKNOWN. This suite pins the
 * lifecycle contract:
 *
 * - Resolution precedence: registry default ← explicit override; an override's
 *   `enabled` is what wins, provenance never flips the value.
 * - Legacy overrides (no source) are PRESERVED as-is — never promoted to
 *   `owner`, never downgraded to `system`, never guessed from the boolean.
 * - Owner pins (source: 'owner') survive effective computation.
 * - Observation-safety: effective values computed from a pre-PRI-637 config
 *   are identical after applying the provenance contract (idempotent, and no
 *   legacy `enabled` value is rewritten).
 * - Alias conflict keeps existing canonical precedence; the canonical entry's
 *   source is preserved.
 * - `system` is an ORIGIN HINT, not an auto-delete license: direct
 *   `.pd/config.yaml` editing is a supported path, so a system entry may carry
 *   Owner intent; provenance never gates the value, and cleanup keyed on
 *   `system` requires explicit Owner confirmation.
 */
export {};
//# sourceMappingURL=pd-config-provenance.test.d.ts.map