Premier League Predictor: Astro — Chapter 12, Exercise 2
====================================================

TASK
Explain the real distinction this chapter draws between "the
framework question" (does adding this app to the live site's own
project require converting it to output: 'server') and "the
infrastructure question" (can the live site's own current deployment
run on-demand code at all), and why this capstone can honestly
resolve only the first one.

SOLUTION

The framework question is entirely about what Astro itself, as a
piece of software, actually requires to produce server-rendered
pages. Checked directly against Astro's own documentation, the real
answer is: not much. A project can keep output: 'static' — its
default, and almost certainly what the live site already uses — and
still mark specific pages with export const prerender = false to get
genuine on-demand rendering for just those pages, with the rest of
the site staying prerendered exactly as before. There's no separate
"hybrid" mode to reach for and no need to flip the whole project over
to output: 'server'. That's a real, verifiable, static fact about how
Astro's build system works, and this chapter is able to state it
confidently because it's something the framework's own documentation
settles directly.

The infrastructure question is a completely different kind of
question: once a page is marked prerender = false, something has to
actually EXECUTE that page's own server-side code on every real
request — which means the deployed environment needs a real adapter
(this course has used @astrojs/node throughout) and a runtime capable
of running it continuously, not simply serving pre-built static HTML
files from a directory. Whether the live site's current hosting setup
already has that capability, or serves purely static files with no
Node process behind it at all, isn't something Astro's own
documentation can answer — it depends entirely on the real, specific
way that particular site happens to be deployed today (which web
server it runs, whether any Node process is already involved, what
the hosting provider actually supports).

This capstone can only speak to the first question, because it's the
one with a fixed, documented, verifiable answer that doesn't depend
on anything outside this course. The second question depends on real,
current facts about a specific deployment this course has no direct
visibility into — asserting a confident answer to it would mean
guessing at infrastructure details rather than reporting something
actually checked, which is exactly the kind of unverified claim this
course's own discipline has avoided everywhere else.

WHY THIS WORKS AS AN ANSWER
----------------------------
It correctly separates a documented, verifiable framework-level fact
(Astro's per-page prerender opt-out needs no full output:'server'
conversion) from a genuinely unknowable, deployment-specific
infrastructure fact (whether the live site's own current hosting can
run on-demand code at all), and explains precisely why only the first
kind of claim belongs in a course that verifies what it states rather
than guessing.