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

WHY NO NEW WORK IS NEEDED HERE
------------------------------
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 containing inline stroke-animation markup. Neither constraint applies to this course's own design, and neither needed anything new introduced in this chapter to resolve.

THE TWO EARLIER CHAPTERS RESPONSIBLE
------------------------------
Per this chapter, Chapter 2's arbitrary-depth Page model has no special-cased depth limit at all, so a kanji path fits exactly as naturally as any other deep page path. Chapter 4's <%== @page.body %> unescaped rendering lets a kanji page's own inline markup - stroke-animation code included - render through the exact same path every other page on the site already uses, with no separate rendering mechanism required.

WHY THIS WORKS AS AN ANSWER
------------------------------
It correctly names both original constraints, and correctly attributes their resolution to Chapter 2 (the depth model) and Chapter 4 (unescaped rendering) rather than treating the resolution as new work introduced in this chapter.