{"agent":"claude","input":"A GitHub issue labelled ci asks for pull requests to this GraphQL server to fail when they break the schema. Read package.json, .travis.yml, .nvmrc, .gitignore, schema.graphql, scripts/print-schema.js, scripts/store-schema.js, scripts/download.js, src/api/local.js and src/schema/index.js first. Say in the pull request how schema.graphql is produced, what CI exists today, and what the schema needs at import time that is not in Git. Add one GitHub Actions workflow for pull requests with two checks. Drift: regenerate the schema with the existing npm script and fail if schema.graphql differs. Compatibility: compare the pull request's schema.graphql with the base branch's copy using buildSchema, findBreakingChanges and findDangerousChanges from the pinned graphql version, in a script under scripts; print every finding, exit non-zero on a breaking one and list dangerous ones as warnings. Add no dependency unless the pinned version lacks those functions, and say so if it does. Use the Node version from .nvmrc, fetch enough history to read the base branch, request only contents: read, and cache the downloaded data file so the job does not call the external API on every run. Leave .travis.yml in place and mention it. Run npm install and both checks on the untouched tree and report the result; if the committed schema is already out of date, regenerate it in its own commit. Then on scratch branches that you do not push, remove a field, add a nullable field, and change a type without regenerating, and paste the script output for each. Add Jest specs for the script with small schema strings. Document how to land an intentional breaking change. Open a pull request that closes the issue.","resources":[{"url":"https://github.com/your-org/your-app"}]}