pub const INHERIT_SOURCE_RESOLVED_REASON: &str = "InheritSourceResolved";Expand description
reason for SECURITY_CONTEXT_RESOLVED_CONDITION = True: the hold above
has CLEARED — the workload came back, the selector was corrected, or an
explicit runAsUser was pinned — and the run is proceeding.
Written only when a non-True condition is already standing, so a run that
was never held stays byte-identical and cannot hot-loop. Healing matters as
much as holding: kubectl kopiur doctor suppresses a stale gate only on a
TERMINAL phase, so a Running Snapshot still carrying the False would be
reported as “blocked … will wait forever” for the whole mover run — the exact
inverse of the false diagnosis this condition exists to prevent.
crate::gates::StructuralGate::trips requires the blocked status, so a
True matches no row and can never be read as an unregistered trip.