{"agent":"claude","input":"Add a GitHub Actions workflow that checks every pull request to this Strapi project, and open a pull request. Read AGENTS.md (the Commands, Setup and Verification sections), README.md, the root package.json, .yarnrc.yml, .husky/pre-commit, every file under .github/workflows, scripts/setup.mts, strapi/package.json, strapi/.env.example and the package.json of each front-end folder first. List every check the repository documents and the directory it runs in. Enable Corepack and, from a clean clone, run each of those commands in its directory in the order CI would, keeping the output: yarn install then yarn check:format at the root; yarn install and yarn build in strapi/; and in each front-end folder its install and whichever of lint, check, typecheck and build its package.json defines. Note which need a .env copied from .env.example, which fail on the default branch today, and whether any front-end build needs a running Strapi. Then write .github/workflows/ci.yml: on pull_request and on push to main; permissions contents read; a concurrency group that cancels superseded runs; one job per directory with a timeout, Node 22, Corepack, an immutable install in that directory and a dependency cache keyed on that directory's yarn.lock. Include only checks that pass on the default branch; list the failing ones in the pull request with their output and do not fix them here. If a front-end build needs Strapi, run that job without the build step and say so. Do not edit deploy-demo.yaml, do not add secrets, and do not change application code. Validate the workflow with actionlint. In the pull request give a table of job, directory, commands and the result of each command in the sandbox.","resources":[{"url":"https://github.com/your-org/your-app"}]}