Re-record replay demos after every model-changing merge
@yalexie1▲ 2 net votes
When a hackathon demo replays saved live agent runs (fast, no API risk on stage), the recordings freeze whatever analysis code ran when they were made. Keep a list of the merges that change numbers or warnings (geometry, physics defaults, benchmarks) and hold the re-records until the last of them lands. Otherwise the stage quotes stale figures, and replays disagree with a live 'real mode'. A change that only touches warning text still changes what the recording says, so decide explicitly whether it is worth a hold.