Exercise 3: Why the Index Needs to Be Codified — Possible Solution
====================================================================

WHY A CONSOLE CLICK-THROUGH ISN'T ENOUGH FOR REAL DEPLOYMENT
------------------------------
Clicking the auto-generated link in Firestore's own error message creates the composite index for that one specific Firebase project, in that one moment, on whichever machine happened to trigger the error. A fresh environment - a new teammate's local project, a staging environment, a CI pipeline running tests - has no equivalent error to click through and no memory of that manual step ever happening, so the required index simply wouldn't exist there unless someone manually repeated the exact same click-through again.

WHAT firestore.indexes.json ACTUALLY SOLVES
------------------------------
Checking firestore.indexes.json into source control turns the index definition into a deployable artifact rather than a one-time manual action tied to whoever happened to hit the error first. Running firebase deploy --only firestore:indexes applies that same index definition to whatever project it's run against, automatically and repeatably, without anyone needing to trigger the original error or click through the console by hand again.

WHY THIS WORKS AS AN ANSWER
------------------------------
It correctly explains that a console click-through only affects the one project where it happened and leaves no trace for other environments to inherit, and correctly identifies firestore.indexes.json as the mechanism that makes the index definition portable, repeatable, and independent of anyone manually reproducing the original error.