Exercise 1: Kanji's Two Original Constraints, Resolved — Possible Solution
====================================================================

THE TWO ORIGINAL CONSTRAINTS
------------------------------
Per this chapter, kanji pages were kept separate for two real reasons: a fixed, three-level content hierarchy with no natural slot for a flat grid of individual characters, and no self-contained-fragment convention, since a kanji page is a complete standalone document with its own inline stroke-animation markup rather than a plain content fragment.

WHY NEITHER APPLIES ANYMORE
------------------------------
Per this chapter, Chapter 2's own arbitrary-depth Page model removes the first constraint entirely - a path like japanese/kanji/水 fits exactly as naturally as any deep course path, with no special-casing required by the model at all. Chapter 4's own {!! $page->body !!} rendering removes the second constraint - a kanji page's stroke-animation markup and inline CSS can live directly in the body column and render through the exact same mechanism every other page on the site already uses, with no separate rendering path needed.

WHY THIS WORKS AS AN ANSWER
------------------------------
It correctly names both original constraints and correctly ties each one back to the specific earlier chapter (Chapter 2 for depth, Chapter 4 for rendering) that already resolves it, rather than treating the resolution as something new introduced in this chapter.