Back to Details

competition-template-render-path

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Competition Template Render Path

竞赛模板渲染路径

Use 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.
Use 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.
Reply in Simplified Chinese unless the user explicitly requests English.
本技能仅作为下游专用技能，在
$ctf-sandbox-orchestrator
已激活并完成沙箱假设、节点归属判定和证据优先级设定后使用。如果尚未满足上述条件，请先返回
$ctf-sandbox-orchestrator
流程。
当决定性漏洞或特征存在于路由解析、服务端渲染上下文、模板数据或hydration切换环节，而非仅存在于普通JSON API中时，使用本技能。
除非用户明确要求英文回复，否则使用简体中文回复。

Quick Start

快速开始

  1. Map the render chain in order: route resolution, loader or data fetch, template or component context, response HTML, hydration payload, and client takeover.
  2. Record host, route params, preview toggles, tenant or host switches, and server-only variables before mutating anything.
  3. Compare template gating with loader or handler enforcement.
  4. Preserve one successful render and one failing render path with the smallest delta.
  5. Reproduce the smallest request-to-render branch that proves the decisive behavior.
  1. 按顺序梳理渲染链路：路由解析、加载器或数据获取、模板或组件上下文、响应HTML、hydration payload、客户端接管。
  2. 在修改任何内容前，记录主机、路由参数、预览开关、租户或主机切换配置、仅服务端可见变量。
  3. 对比模板访问控制与加载器或处理程序的执行逻辑。
  4. 留存差异最小的一条成功渲染路径和一条失败渲染路径。
  5. 复现能证明决定性行为的最小请求到渲染分支路径。

Workflow

工作流

1. Map Route To Render Context

1. 路由到渲染上下文映射

  • Record host, path, route match, loader, template, layout, hydration blob, and client boot chunk for the active view.
  • Note whether the response is SSR HTML, static HTML plus hydration, edge-rendered content, or a template fragment used by another route.
  • Keep server-only context and client-visible context separate.
  • 记录当前活跃视图的主机、路径、路由匹配结果、加载器、模板、布局、hydration blob、客户端启动chunk。
  • 标注响应类型是SSR HTML、静态HTML加hydration、边缘渲染内容，还是供其他路由使用的模板片段。
  • 严格区分仅服务端可见上下文和客户端可见上下文。

2. Trace Template And Enforcement Boundaries

2. 追踪模板与执行边界

  • Show where permissions, feature flags, preview state, tenant selection, or host-based switches are applied.
  • Compare template-level gating, loader-level gating, and backend handler enforcement instead of trusting any one layer.
  • Record hidden fields, inline data, hydration JSON, meta tags, or alternate partials that expose the decisive branch.
  • 标明权限、功能开关、预览状态、租户选择、基于主机的切换逻辑的生效位置。
  • 对比模板层访问控制、加载器层访问控制和后端处理程序执行逻辑，不要信任单一层级的校验。
  • 记录暴露决定性分支的隐藏字段、内联数据、hydration JSON、meta标签或备用分片。

3. Reduce To The Decisive Render Path

3. 收敛到决定性渲染路径

  • Compress the result to the smallest sequence: request -> route match -> loader or template context -> rendered output or hidden data -> resulting effect.
  • State clearly whether the decisive weakness lives in route selection, template context construction, server-client hydration handoff, or mismatched enforcement between render and handler.
  • If the task becomes mostly emitted bundle recovery or source map reconstruction, hand off to the tighter bundle skill.
  • 将结果压缩为最小序列：请求 -> 路由匹配 -> 加载器或模板上下文 -> 渲染输出或隐藏数据 -> 最终效果。
  • 明确说明决定性漏洞存在于路由选择、模板上下文构建、服务端-客户端hydration切换，还是渲染与处理程序之间的执行逻辑不匹配。
  • 如果任务主要转为产物包恢复或source map重构，请转交给更适配的bundle技能处理。

Read This Reference

参考文档

  • Load 
    references/template-render-path.md
    for the render checklist, hydration checklist, and evidence packaging.
  • 加载
    references/template-render-path.md
    获取渲染检查清单、hydration检查清单和证据打包规范。

What To Preserve

需留存内容

  • Route names, loader names, templates, layouts, hydration keys, and host or preview switches
  • One success or failure pair that shows where render-layer behavior diverges
  • One minimal request-to-render sequence that reaches the decisive branch
  • 路由名称、加载器名称、模板、布局、hydration key、主机或预览开关
  • 一组能展示渲染层行为差异的成功/失败请求对
  • 一条能触达决定性分支的最小请求到渲染序列