Everyone leaves with a routine for shipping changes safely, and the team agrees how it gets back to a working version when a release breaks.
Read Days 71, 73 and 77 (about five minutes each), or Module 8 on the cheat sheet.
Quick round: when did you last push your work, in a few words?
Pick one live or nearly-live tool. Write down how you'd roll it back, who can do it, and what counts as broken enough to roll back. Any blank answer is this week's work.
Each tool owner tries one rollback on a test version and writes down the steps and how long it took.
Agree the team rule: “Roll back first. Debug second.”
Ignoring a red CI result, or switching the check off to merge faster (Day 74). Red means stop, even on a Friday.
A whiteboard or shared doc, and a timer.
Next session: Module 9 · Vibe coding at work. Bring the rollback plan and how long the test took.