pub const RESTORE_REFERENT_AVAILABLE_CONDITION: &str = "ReferentAvailable";Expand description
Restore condition recording whether the object this restore’s repository
is DERIVED from exists. Set False (with
RESTORE_REFERENT_MISSING_REASON) when the readiness gate cannot even
look up the repository because a referent is absent: the explicit
spec.repository object itself, or the source.fromPolicy SnapshotPolicy
the repository ref is read from (issue #393).
Its own condition rather than the Ready one: the registry’s coarse
crate::gates::StructuralGate::trips filter keys on condition+polarity,
so registering a Ready=False row would make every unrelated Ready=False
reason on a Snapshot/Restore read as an unknown gate from a newer
operator. Only this gate ever writes this condition, so it cannot misfire.
Structural (crate::gates::RESTORE_REFERENT_MISSING_GATE): a referent
that is never created never self-heals, and while it is missing the restore
sits at phase: Pending with its policy.waitTimeout window deliberately
NOT started — the phase-invisible park shape of #359.