Exercise 1: A Cataloged Component That Won't Render — Possible Solution
====================================================================

The most likely reason is that "alert" was added to catalog.ts but no
matching entry was ever added to registry.tsx. The catalog only
declares that "alert" is an allowed component type - it says nothing
about how to actually render one. The registry is the file
specifically responsible for connecting a type name to a real
component implementation, and if that connection was never made, the
renderer has no real component to use when it encounters "alert" in a
spec, even though the catalog says the type itself is valid.

This is exactly the kind of two-step registration this chapter's own
catalog/registry split creates: adding a component to the catalog
alone only grants "permission" for the AI model to reference it, it
doesn't automatically make it renderable. Both files need a matching
entry for a component to actually work end to end.

ANSWER: The most likely reason is a missing registry.tsx entry for
"alert" - the catalog only declares that the type is allowed, it
doesn't connect it to a real component. Without a matching entry in
the registry, the renderer has nothing to actually render when it
encounters "alert" in a spec, even though the catalog itself is
correctly configured.

WHY THIS WORKS AS AN ANSWER
------------------------------
This correctly applies the chapter's own catalog-vs-registry
distinction to diagnose a realistic failure mode, rather than treating
"add it to the catalog" as sufficient on its own.