Exercise 3: Confirming notFound() Handles Both Content and Status — Possible Solution
====================================================================

THE TEST
------------------------------
With app/not-found.tsx in place per this chapter, visiting a path with
no matching row in the pages table (e.g. /this/path/does/not/exist)
triggers the if (!page) branch in app/[...path]/page.tsx, which calls
notFound().

CONFIRMING THE CONTENT
------------------------------
The browser renders "Page not found" - the exact content of
app/not-found.tsx - confirming notFound() correctly located and
rendered the nearest not-found boundary.

CONFIRMING THE STATUS CODE
------------------------------
Opening the browser's own network inspector (or running curl -I against
the same URL) shows the actual HTTP response status is 404, not 200 -
confirming notFound() set the real status code automatically, with no
separate response.status = 404 line anywhere in the route file.

WHY THIS WORKS AS AN ANSWER
------------------------------
It checks both halves of the claim independently - the rendered content
and the actual HTTP status code, not just one or the other - and
confirms both were produced by the single notFound() call alone,
directly verifying this chapter's own comparison against Astro's
two-piece Astro.response.status/Astro.rewrite() combination for the
identical job.