Exercise 2: Why Test Mode Is Switched Off Last — Possible Solution
====================================================================

WHAT COULD GO WRONG IF IT WERE SWITCHED OFF EARLIER
------------------------------
Per this capstone, if live API keys were active while the catalog,
checkout flow, order-lookup feature, bulk-discount hook, and caching
setup were all still being actively built and tested, any real
customer or accidental test transaction attempted during that process
could process a genuine charge against a real card - exactly the kind
of accidental live transaction Chapter 5's own Test Mode warning
addressed.

WHY WAITING UNTIL EVERYTHING ELSE IS VERIFIED IS THE SAFER ORDER
------------------------------
Per this capstone, Test mode is switched off "deliberately the very
last step, so nothing still being actively verified could ever
accidentally process a real charge." Every other piece of the store
- catalog, design, checkout flow, shipping/tax, security fixes, the
discount hook, and caching/performance - is fully built and confirmed
working first, while the store is still safely isolated from real
payments.

WHY THIS WORKS AS AN ANSWER
------------------------------
It correctly identifies the risk of leaving live keys active during
active development/testing (a real accidental charge), and correctly
explains that ordering the switch to live mode last is what protects
against that risk during every earlier step of the capstone.