competition-template-render-path

1# Competition Template Render Path
2 
3Use this skill only as a downstream specialization after `$ctf-sandbox-orchestrator` is already active and has established sandbox assumptions, node ownership, and evidence priorities. If that has not happened yet, return to `$ctf-sandbox-orchestrator` first.
4 
5Use this skill when the decisive bug or artifact lives in route resolution, server render context, template data, or hydration handoff rather than in a plain JSON API alone.
6 
7Reply in Simplified Chinese unless the user explicitly requests English.
8 
9## Quick Start
10 
111. Map the render chain in order: route resolution, loader or data fetch, template or component context, response HTML, hydration payload, and client takeover.
122. Record host, route params, preview toggles, tenant or host switches, and server-only variables before mutating anything.
133. Compare template gating with loader or handler enforcement.
144. Preserve one successful render and one failing render path with the smallest delta.
155. Reproduce the smallest request-to-render branch that proves the decisive behavior.
16 
17## Workflow
18 
19### 1. Map Route To Render Context
20 
21- Record host, path, route match, loader, template, layout, hydration blob, and client boot chunk for the active view.
22- Note whether the response is SSR HTML, static HTML plus hydration, edge-rendered content, or a template fragment used by another route.
23- Keep server-only context and client-visible context separate.
24…