Lock Version 1. After today, no new features — only bug fixes.

A real studio freezes code before release. Code freeze means: the feature set is final. You can fix bugs, but you cannot add anything new. This discipline prevents last-minute chaos.

After today:

  • No new features
  • Only critical bug fixes
  • No "just one more thing"
  • No refactoring
  • No experiments
  • Add "// Version 1.0 — Code Freeze" comment at top of main.js
  • Tag version in HTML header or title
  • Clean folder structure (remove test files)
  • Remove all test/debug variables
  • Confirm localStorage compatibility
  • Optional: add simple start screen (title + "Press Start")
  • Verify game loads cleanly with no console errors
    •
    Checkpoint

    Both projects load cleanly. No unused code. No console errors. The game is frozen.

    This IS the freeze. Nothing new after today.

    "Code freeze except for this one thing..." — NO. A freeze with exceptions is not a freeze.

    Deleting code that's actually needed — test after every deletion. Remove only what you're certain is unused.

    Not testing after cleanup — cleaning up files can break paths and references. Verify everything still loads.

    Forgetting to remove debug code — search for console.log, test variables, and temporary hacks. Remove them all.

    Ask: "Why do professional teams freeze code?" Answer: because every change before launch is a risk. The game works NOW. Changes might break it. Freezing protects what works. This is real-world software discipline.