Exercise 1: Confirming Nothing New Is Needed — Possible Solution
====================================================================

WHY NO NEW WORK IS REQUIRED
------------------------------
Per this chapter, kanji's two original constraints were a fixed-depth
content hierarchy with no natural slot for individual characters, and
no self-contained-fragment convention for a page with inline markup.

THE TWO EARLIER CHAPTERS RESPONSIBLE
------------------------------
Chapter 2's raw SQL schema has no depth column, no depth constraint,
and no special-casing of any kind - a kanji page's own parent_id
chain works exactly like any other page's. Chapter 4's
<%- page.body %> renders any page's own stored HTML - including a
kanji page's own inline stroke-animation markup - through the
identical rendering path every other page on the site already uses.

WHY THIS WORKS AS AN ANSWER
------------------------------
It correctly names both original constraints and correctly attributes
their resolution to Chapter 2 (the schema) and Chapter 4 (rendering),
confirming this chapter genuinely needs no new code to solve either
one.