competition-websocket-runtime

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Chinese

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 behavior is carried by realtime handshake and frame flow rather than one-shot HTTP alone.

Reply in Simplified Chinese unless the user explicitly requests English.

仅可在

$ctf-sandbox-orchestrator

已激活，且已完成沙箱假设配置、节点归属确认、证据优先级确定后，作为下游专用技能使用。如果尚未满足上述前置条件，请先返回调用

$ctf-sandbox-orchestrator

。

当核心行为由实时握手和帧流决定，而非仅由单次HTTP请求决定时，使用本技能。

除非用户明确要求使用英文，否则请用简体中文回复。

Map the handshake first: origin, path, headers, cookies, query, auth token, and upgrade response.
Separate connection setup, subscription messages, keepalives, server pushes, and reconnect logic.
Record message schema, topic or channel identity, and state side effects in one chain.
Tie frames to rendered, stored, or backend-visible effects.
Reproduce the smallest handshake-plus-frame sequence that reaches the decisive state change.

Record the initial HTTP or SSE request, upgrade headers, cookies, tokens, query params, origin checks, and negotiated protocol.
Note whether auth material is carried by headers, cookies, query strings, or initial application frames.
Keep route, subscription endpoint, and session identity tied together.

Separate subscribe, unsubscribe, ack, heartbeat, server push, reconnect, and terminal frames.
Recover message types, channel IDs, schema fields, and sequencing that matter to behavior.
Distinguish transport keepalive from application-level business messages.

Compress the result to the smallest sequence: handshake -> auth or subscribe frame -> pushed or accepted frame -> resulting state change.
Keep canonical frame order and any replayed minimal order side by side.
If the hard part is generic protocol reassembly without runtime UI or app-state linkage, switch back to the tighter protocol skill.

Load
```
references/websocket-runtime.md
```
for the handshake checklist, frame checklist, and evidence packaging.

Handshake headers, cookies, query params, auth material, negotiated subprotocol, and channel IDs
Frame schemas, subscription messages, server pushes, reconnect flow, and resulting state changes
The smallest replayable realtime sequence that proves the decisive branch