index afc0293..11be5c5 100644
@@ -10,16 +10,8 @@ MAKE SURE THE THING WORKS BEFORE GOING INTO THE PRESENTATION. tested individual
## why it's a gotcha
-integration bugs only show up when you run the full flow. you'll discover that step 3 breaks step 5 right in front of the judges. individual components working does not mean the system works.
+integration bugs only show up when you run the full flow. you'll discover that step 3 breaks step 5 right in front of the judges. individual components working does not mean the system works. [[ai-rot|AI-generated code]] you didn't test is a common cause — and [[it-works-on-my-machine|environmental differences]] between your machine and the demo machine make it worse.
## the fix
-run the complete user flow at least twice before presenting. start from a clean state each time. if something breaks, you want to find it now, not on stage.
-
-## see also
-
-- [[restart-server-before-demo]] — another pre-demo checklist item
-- [[practice-presentation-once]] — testing the presentation, not just the code
-- [[no-backup-plan-for-failed-demo]] — what to do when it breaks anyway
-- [[ai-rot]] — AI-generated code you didn't test is a common cause
-- [[it-works-on-my-machine]] — environmental differences break demos
\ No newline at end of file
+run the complete user flow at least twice before presenting. start from a clean state each time — [[restart-server-before-demo|restart services]] to make sure you're not running stale code. if something breaks, you want to find it now, not on stage. and have a [[no-backup-plan-for-failed-demo|backup plan]] for when it breaks anyway. testing the demo is one thing; [[practice-presentation-once|testing the presentation itself]] is another.
\ No newline at end of file