Found during the Bevy 0.20 upgrade (#253).
bot_outcomes_are_pinned changed on floor 2 (turn counts), because Bevy 0.20 stores resources as entities and so allocates entities in a different order. Recorded missions replay identically and the golden file is unchanged, so the simulation itself is fine. But the bot's choices depend on entity allocation or iteration order somewhere, which means its pins churn whenever an unrelated change spawns an entity.
Find where the bot, or the observation it reads, iterates in entity order, for example NPCs, impediments or sessions in query order, and sort by a stable key (position, then a stable id). Then re-pin once.