Romaji to Kana Converter: Astro — Chapter 8, Exercise 2
=====================================================================

TASK
Explain in your own words why Chapter 6's decision to scope the CSS
under a wrapper class "on purpose" turned out to matter directly in
this capstone, tracing the specific real mechanism that makes it
matter.

SOLUTION

Chapter 6 already established that Astro's own compiler automatically
scopes native <style> blocks inside a real .astro file, via a real,
verified data-astro-cid-* attribute rewrite -- meaning the manual
wrapper class (.romaji-page) technically wasn't needed to prevent CSS
leaks as long as this markup stayed inside a standalone, Astro-compiled
page. Chapter 6 kept the wrapper class anyway, describing it as "cheap
insurance" against a specific future scenario: this same markup being
moved out of a compiled .astro page and into the site's own injected-
fragment system instead.

That's exactly the scenario this capstone reaches. My Tools pages (per
my_tools_rules.md's own MT1-MT9 convention) are injected into the site's
shared template via set:html -- the HTML-fragment equivalent of
innerHTML. Once markup is injected that way, it completely bypasses
Astro's own compiler, and with it, the automatic data-astro-cid-*
scoping mechanism Chapter 6 found. A set of unscoped bare-selector CSS
rules (like a plain "input { ... }" or "button { ... }") would leak
straight out into every other element on the shared page the fragment
gets embedded into, genuinely breaking things elsewhere on the site.

Because the wrapper class was already in place from the very first
version of this converter's own CSS, that specific risk never had a
chance to occur: every rule in Chapter 6's own stylesheet is already
written as ".romaji-page .something { ... }" rather than a bare
selector, so the exact same CSS file can be dropped into the My Tools
fragment system with zero changes and zero leakage, regardless of
whether Astro's own compiler scoping is present to help or not.

WHY THIS WORKS AS AN ANSWER
----------------------------
It traces the real, specific mechanism at stake -- Astro's compiler-
level automatic scoping being present in a standalone page but absent
once markup moves into an injected fragment -- and explains concretely
why the wrapper class already being in place is what makes that move
safe today, rather than restating Chapter 6's own "cheap insurance"
phrase without explaining what it actually insures against.