# Template and module rendering How `migrate` renders a page when the page is not itself approved but its type has an approved sibling (Path A′), or when a page matches no template and must be rendered as a one-off (Path B — `unique` rendering). This is the substantive new behavior introduced by the migrate- template-canon refactor. Path A (page is itself `approved`) is unchanged — the proposed.html is used verbatim, with `:root` refreshed from latest DESIGN.md. ## Render path selection For each page in scope, the render branch is chosen by LLM judgment: | Branch | Trigger | |------------|----------------------------------------------------------------------------------| | **Path A** | Page status is `approved`. Use its proposed.html verbatim. | | **Path A′**| Page status is `directed`, page `type` matches an approved sibling's archetype. | | **Path B** | Page typed `unique`, or no template archetype matches. | The LLM should prefer Path A′ when a template is genuinely applicable. Path B is the escape hatch — for landing pages with no peer template, error pages, search pages, or pages whose content shape doesn't fit any approved archetype. ## Path A′ — template-applied rendering For a `directed` page whose `type` has an approved archetype: ### Step 1 — load the archetype Read the approved sibling's `-proposed.html` from `stardust/prototypes/`. This is the **structural seed** for the target page. ### Step 2 — inject this page's content into slots Read the target page's typed slots from `stardust/current/pages/.json § slots`. The slots were captured during `extract --prep`. For each slot in the archetype (identified by `data-slot="..."` within `data-template=""`), inject this page's value: - `data-slot="article-headline"` ← target page's `headline` slot - `data-slot="article-byline"` ← target page's `byline` slot - `data-slot="article-body"` ← target page's `body` slot - ... and so on for every slot the archetype defines The injection preserves the archetype's structural elements (wrapping divs, classes, data-attributes) and replaces the inner content with the target page's slot value. ### Step 3 — adapt where content doesn't fit The target page may carry content that doesn't have a matching slot in the archetype, or may be missing slots the archetype requires. The LLM judges: - **Extra content** (target has a video embed; archetype has no video slot) → place in the archetype's overflow region (a slot named `