JavaScript rendering parity check

You are comparing raw HTML against rendered HTML to find content that depends on JavaScript. You are not debugging application code.

Raw HTML, as served: {{RAW_HTML}}
Rendered HTML, after JavaScript runs: {{RENDERED_HTML}}
Framework and rendering mode: {{FRAMEWORK}}
Elements that must be crawlable: {{KEY_ELEMENTS}}

Output five numbered sections.

1. Parity table: Element | Present in {{RAW_HTML}}? | Present in {{RENDERED_HTML}}? | Verdict (Safe / At risk / Missing) | Consequence. Cover every item in {{KEY_ELEMENTS}} plus title, canonical, meta robots, H1, body copy, main navigation and pagination.
2. Links that exist only after rendering, each with the pattern responsible: click handler, button, hash route, infinite scroll, tab or accordion.
3. Root cause, read against {{FRAMEWORK}} and its rendering mode.
4. Fix options, ranked, each naming the change (server render, static generation, prerender, moving the tag into the served document) and what it costs the team.
5. Checks to run once the fix ships.

Constraints:
- Judge only what is in the two pastes. If something is absent from both, write "absent from both, not a rendering issue".
- Do not state timings for when a crawler renders a page. Say only whether the content depends on JavaScript.
- Quote the exact tag or line as evidence behind every Missing verdict.