pub const SEED_SOURCE_NOT_READY_GATE: StructuralGate;Expand description
A spec.seed in migrate mode whose SOURCE repository is missing or not
Ready (issue #380). The repository parks Pending with Seeded=False
and re-checks; nothing in kopiur can bring the source up, so it is squarely
“needs a human” — and the park is phase-INVISIBLE in the worst way: a
brand-new repository sitting at Pending looks identical to one that is
simply still bootstrapping, and it will sit there for as long as the source
is down.
WARN rather than Fail, for two reasons that point the same way. The
registry pins one severity per condition+scope
(gate_rows_are_unique_and_internally_consistent), and the sibling
SEEDING_GATE on this same condition must be Warn — a seed legitimately
runs for hours, and a healthy copy must not turn a diagnostic red. And on
its own merits this park is the same shape as
POLICY_REPOSITORY_NOT_READY_GATE: a source repository that is still
bootstrapping alongside this one (the ordinary DR bring-up) comes up by
itself, and one deliberately taken down is a plausible operator choice. The
block is reported either way, with the writer’s message — which is what
makes it worth registering.