golang-graphqllisted

# Go GraphQL APIs Work within the GraphQL implementation and schema workflow already selected by the project. Do not switch libraries or regenerate unrelated schema output. ## Establish the local contract Before editing, inspect: - `go.mod` and the selected GraphQL library version; - schema files, generation configuration, generated-file policy, and generation command; - HTTP/WebSocket construction, authentication middleware, authorization checks, and error presentation; - resolver, batching, persistence, and test conventions. Verify API names against the selected version's official documentation. Treat generated files as derived unless the repository documents otherwise. ## Follow the selected implementation - For gqlgen generation, handler setup, error presentation, request-scoped loaders, and client tests, read [gqlgen recipes](references/gqlgen.md). - For graph-gophers resolver signatures, scalar mapping, schema options, and direct execution tests, read [graph-gophers recipes](references/graphql-go.md). Do not combine their resolver or middleware APIs: gqlgen validates generated interfaces at compile time, while graph-gophers validates reflected resolver signatures when the schema is parsed. ## Schema and resolver changes - Preserve field nullability, pagination shape, error contract, and compatibility unless the user requests a breaking schema change. - Make a field non-null only when the resolver contract can reliably supply it; remember that an error on a non