reverse-skills-max: initial public release (restored, redacted, hardened)
This commit is contained in:
@@ -0,0 +1,27 @@
|
||||
# Graphql And Rpc Drift Checklist
|
||||
|
||||
## First Pass
|
||||
|
||||
- GraphQL schema, introspection output, persisted query ids, RPC manifest, generated client, OpenAPI doc
|
||||
- Operation names, fields, variables, method, path, version headers, auth context
|
||||
- Live handlers, fallback routes, hidden operations, stale fields, client-only guards
|
||||
|
||||
## Chain To Reconstruct
|
||||
|
||||
1. Declared contract is identified
|
||||
2. Real request shape is captured
|
||||
3. Handler normalization or hidden branch is observed
|
||||
4. Contract drift or hidden operation is confirmed
|
||||
5. Resulting capability or artifact is reproduced
|
||||
|
||||
## Evidence To Keep Together
|
||||
|
||||
- Contract side: schema, manifest, generated client, version marker, persisted query id
|
||||
- Request side: operation name, variables, method, path, headers, cookies
|
||||
- Effect side: hidden data, accepted action, privilege, or backend state change
|
||||
|
||||
## Common Pitfalls
|
||||
|
||||
- Treating generated clients as proof of the only supported operations
|
||||
- Looking at GraphQL schema or OpenAPI docs without capturing real requests
|
||||
- Describing hidden operations without proving the exact handler branch they hit
|
||||
Reference in New Issue
Block a user