Two outages in one session came from this file claiming `replicas: 0` while the
cluster served traffic: a plain `kubectl apply` scaled it to zero, twice. Source
now states production intent. Parking stays an explicit `kubectl scale`
divergence recorded in k3s-fleet/cluster-state.yaml, and
scripts/restore-fleet.sh remains the guarded path back - its storage, image, and
per-node capacity preflights are exactly what a bare apply does not do.
Pins server:m12-consumer-readpath-20260818@sha256:9191233d..., the build with the
transport-aware read budget and the scatter-degraded counters. Verified after the
rolling update: 3/3 Ready, all regions lag 0, every replica answering 3/3 shards
with degraded=false on the default budget.
d923b036af