Challenge 1: What Breaks When Script Tags Are Reordered — Possible Solution
====================================================================

WHAT WOULD BREAK
------------------------------
Per this chapter's own example, api.js depends on utils.js — it
expects functions or values defined in utils.js to already exist in
the shared global scope by the time api.js itself runs. If the
<script> tags were swapped so api.js loaded BEFORE utils.js, then at
the moment api.js executes, whatever it expects from utils.js simply
wouldn't exist yet. Depending on exactly what api.js does with the
missing value, this would either throw a "not defined" error
immediately, or silently produce undefined/incorrect behavior if the
code doesn't fail loudly right away.

WHY THIS IS A REAL, EASY MISTAKE
------------------------------
Nothing in the plain <script src> model checks or enforces this
ordering at all — per this chapter's own description, order is
"tracked by hand, with nothing checking it for you." A developer
adding a new script tag, or reordering existing ones during a
refactor, has no automated warning that they've just broken a real
dependency; the mistake only surfaces when the page actually runs and
something fails (or silently misbehaves).

WHY A BUNDLER'S DEPENDENCY GRAPH MAKES THIS IMPOSSIBLE, NOT JUST LESS LIKELY
------------------------------
Per this chapter's own after-example, a bundler doesn't rely on the
ORDER files happen to be listed in at all — it reads each file's own
explicit import statements (e.g. api.js's own `import ... from
'./utils.js'`) and builds a real dependency graph directly from that
information. The bundler then computes a load order that is
GUARANTEED correct relative to the actual declared dependencies,
regardless of what order a developer happened to list files in, or
whether they reordered anything. This isn't "the bundler is better at
remembering the right order" — it's that there's no longer any
separate, human-maintained ordering to get wrong in the first place;
the order is a direct, mechanical consequence of the import
statements themselves.

WHY THIS WORKS AS AN ANSWER
------------------------------
It traces the specific failure (api.js running before utils.js exists)
using the chapter's own stated dependency relationship, and explains
why the bundler's approach is a structural fix (order derived
automatically from real dependency declarations) rather than merely a
tool that catches the same class of human error more reliably.