Exercise 2: Confirming 404.astro Is Never Reached — Possible Solution
====================================================================

STEPS
------------------------------
1. With [...path].astro from Exercise 1 still in place, and no
   explicit not-found handling added yet, visit a URL with no
   matching row, e.g. /this/path/does/not/exist.

2. [...path].astro's own query returns an empty result. Since
   page.title is accessed on an undefined page (no if (!page) guard
   yet), the page either throws a runtime error or, if the query
   result is destructured loosely, renders a broken/empty heading -
   either way, it is NOT the content of src/pages/404.astro.

3. Confirm directly that src/pages/404.astro's own content never
   appears at all, even though the file exists in the project - the
   catch-all route always matches first and Astro never falls
   through to it.

WHY THIS WORKS AS AN ANSWER
------------------------------
It correctly demonstrates that visiting a genuinely nonexistent path
does not render 404.astro's own content, confirming the chapter's
own central gotcha: owning a global catch-all route means Astro's
conventional automatic-404 file-based routing never actually
triggers.