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

TASK
In your own words, explain why my_tools_rules.md's own MT4 requires
manual wrapper-class scoping for a My Tools page, but this chapter
found that requirement doesn't actually apply to index.astro's own
native <style> block -- and then explain why this chapter added a
wrapper class anyway.

SOLUTION

MT4's own manual scoping rule exists because of how a My Tools page
actually reaches the live site: it's built as a finished, self-
contained block of HTML that gets injected directly into an already-
existing page via set:html -- essentially the same operation as
assigning raw HTML text to another element's innerHTML. That
injection happens entirely outside Astro's own build process, which
means the <style> block sitting inside that injected HTML is never
seen by Astro's compiler at all -- it ships as plain, literal CSS text
with no automatic rewriting applied to it. A bare selector like
"input { ... }" in that context really does mean every input anywhere
on the page it gets injected into, which is exactly the real leak bug
MT4 documents happening in agent-builder.html.

index.astro is a structurally different situation. It's written as a
genuine, native .astro file, and it goes through Astro's own compiler
directly, the same way any other .astro component on the site does.
Astro's compiler rewrites every selector inside that <style> block --
including a bare "input" selector -- to also require a real, unique
data-astro-cid attribute, and stamps that same attribute onto every
element the component actually renders. The scoping MT4 has to enforce
by hand for an injected fragment happens automatically, for free, for
a real compiled component.

Given that, the wrapper class this chapter still adds isn't fixing a
bug that exists today -- it's added because Chapter 8 hasn't yet
decided exactly how this converter will actually be mounted onto the
live site. If that final integration route ends up moving this
page's own markup into the injected-fragment system MT4's rule
protects (rather than keeping it as a standalone, Astro-compiled
route), the automatic data-astro-cid protection this chapter relied
on would disappear along with it. Having the wrapper class already in
place costs nothing now and means nothing would need retrofitting
later if that turns out to be the path taken.

WHY THIS WORKS AS AN ANSWER
----------------------------
It correctly identifies the real structural difference between the
two situations (compiled-by-Astro vs. injected-and-bypassing-Astro)
as the actual reason MT4's rule applies to one and not the other,
rather than treating the rule as a blanket policy that simply carries
over everywhere -- and explains the wrapper class as genuine
forward-looking insurance against a real, still-open decision, not as
a correction of a bug that was ever actually found in this file.