Parameter decorators of WebSocketRoute: Acceptor, Driver,
Header, Param, and Query.
Evidence
contracts/common.md#principled-implementation Each decorator appends category and position metadata. Header registration stores the shared checker whose resolver preserves successful callback data for the decorated argument without replacing the acceptor header; legacy error-only callbacks retain raw input. Param and query keep their own decoder contracts, and every rejected handshake retains its original error handling.
Evidence
contracts/common.md#clear-and-simple-design Five decorators sharing one emplace helper for the metadata list.
Evidence
contracts/common.md#prohibited-implementation-shortcuts The validators are generated from the types; without the transform the raw values are passed only when the configuration guard is off.
Evidence
contracts/common.md#meaningful-documentation Each decorator documents its meaning.
Evidence Exclude
contracts/portability.md#os-neutral-implementation The route and parameter metadata describe WebSocket handshakes and HTTP URL fields; native files and processes are not represented.
Parameter decorators of WebSocketRoute:
Acceptor,Driver,Header,Param, andQuery.Evidence
contracts/common.md#principled-implementation Each decorator appends category and position metadata. Header registration stores the shared checker whose resolver preserves successful callback data for the decorated argument without replacing the acceptor header; legacy error-only callbacks retain raw input. Param and query keep their own decoder contracts, and every rejected handshake retains its original error handling.
Evidence
contracts/common.md#clear-and-simple-design Five decorators sharing one
emplacehelper for the metadata list.Evidence
contracts/common.md#prohibited-implementation-shortcuts The validators are generated from the types; without the transform the raw values are passed only when the configuration guard is off.
Evidence
contracts/common.md#meaningful-documentation Each decorator documents its meaning.
Evidence Exclude
contracts/portability.md#os-neutral-implementation The route and parameter metadata describe WebSocket handshakes and HTTP URL fields; native files and processes are not represented.