gogobee has started filing a `retreat` bulletin — an expedition that ended with the player walking out alive. Pete had no case for it, and handleAdventureIngest answers an unrecognized event_type with 400. That failure is silent and total. gogobee's sender treats any non-2xx as a failure, retries eight times over roughly two hours, and then parks the row for good. A gogobee emitting `retreat` at a Pete who doesn't know the word would not log an error anyone reads — it would just quietly drop every retreat the realm ever files. So Pete has to learn it BEFORE gogobee starts saying it. Deploy order matters here, and it is Pete first. The copy leads with everyone coming home, because that is the true and the kind part: a retreat is a bad day, not a funeral. Bulletin tier — it rides the daily digest and does not interrupt the room. Announcing every failed run live would be a firehose, and an unkind one. https://claude.ai/code/session_01B2MwktU4RgfWkar8HM3zZn
16 KiB
16 KiB