Modules and Adaptive UI

Lite, Standard, Full, and Custom are installation profiles, not labels. If a module is disabled, do not create its records, guide, trigger route, handbook chapter, prelude explanation, or empty layout panel. Modify parent children arrays to remove unused sections; do not rely on a visibility flag to hide them.

Use the shared visual grammar: ImageHeader hero; three to six at-a-glance values; one signature panel unique to the record; actionable primary state; then Play, Mechanics, History, and GM hierarchy where the type needs it. Advanced state belongs in later tabs or collapsibles. Do not duplicate values or expose backend state merely because the schema permits it.

The shipped Full layouts are a palette. Setup compiles the smaller layout the actual world needs.