{"agent":"claude","input":"Upgrade graphql-js in this GraphQL server to the newest major its other dependencies allow. Read package.json, package-lock.json, .nvmrc, .babelrc, jest.config.js, .flowconfig, the scripts directory, the handler directory and everything under src first. List the declared and locked versions of graphql and every package that has it as a peer, with each peer range. Use npm view to read graphql's dist-tags and the peer ranges of newer releases of those packages, then state the target major and which package limits it. Record a baseline: npm ci (note what postinstall does and whether it needed the network), npm test, npm run print-schema saved to a file, a comparison of that file with the committed schema.graphql, and each query under doc/example_queries executed against the schema. Then move graphql up one major at a time, moving graphql-relay to a release whose peer range allows it at the same step. At each step read that major's release notes, run npm test, and fix what broke with the documented replacement: single-object arguments to graphql() and execute(), type resolvers that return a type name, and renamed or removed utilities. Do not change resolver behaviour, do not upgrade dataloader, Babel, Jest, ESLint or Flow unless a step cannot pass without it, and say so if that happens. After the last step, print the schema again and compare it with the baseline as text and with findBreakingChanges and findDangerousChanges; both must report nothing. Regenerate schema.graphql only if its printed form changed. Rerun the example queries and confirm the handler module still loads the built schema. Open a pull request with the version table, one section per major listing what changed and why, the schema comparison, and the command output before and after.","resources":[{"url":"https://github.com/your-org/your-app"}]}