Constant SCHEDULE_REPLACEMENT_HELD_CONDITION 

pub const SCHEDULE_REPLACEMENT_HELD_CONDITION: &str = "ReplacementHeld";

SnapshotSchedule condition recording that concurrencyPolicy: Replace is holding a due slot because the run it would replace is itself parked behind its repository’s mover-Job concurrency cap (REPOSITORY_SLOT_AVAILABLE_CONDITION = False). Cancelling a queued run frees no capacity and the replacement would re-queue behind it, so Replace degrades to Forbid-like waiting until the pool drains.

Deliberately not a registered structural gate (crate::gates::STRUCTURAL_GATES): unlike ScheduleRunnable=False, this state needs no human — it clears by itself the moment a slot frees up. It exists so the wait is visible in status and so the accompanying Normal event fires once on entering the hold rather than on every requeue.