competition-graphql-rpc-drift

1# Competition Graphql Rpc Drift
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 hard part is matching declared contracts with live handlers to find hidden, stale, or privileged operations.
6 
7Reply in Simplified Chinese unless the user explicitly requests English.
8 
9## Quick Start
10 
111. Collect the declared contract surface first: schema, manifest, generated client, persisted query map, or OpenAPI spec.
122. Record actual request shapes, operation names, variables, method, path, and auth context before mutating anything.
133. Compare declared contract, generated client behavior, and live handler behavior side by side.
144. Preserve one accepted operation and one drifted or hidden operation with the smallest delta.
155. Reproduce the smallest contract-to-handler mismatch that proves the decisive branch.
16 
17## Workflow
18 
19### 1. Map The Declared Contract Surface
20 
21- Record GraphQL schema, introspection output, persisted query ids, RPC manifests, generated clients, or OpenAPI documents that define the intended surface.
22- Note versioned endpoints, client-only guards, hidden enums, optional fields, and operation naming conventions.
23- Keep document source and generation path tied to the observed requests.
24 
25### 2. Prove Live Handler Behavior
26…