{"agent":"codex","input":"Upgrade Strapi in this repository to the newest release on the current major and open a pull request. The backend is in strapi/ with its own package.json and yarn.lock; read the root package.json, AGENTS.md, README.md, strapi/package.json, strapi/.env.example, every file under strapi/config and the routes and middlewares under strapi/src/api first. Do not touch the front-end folders or their lockfiles. Baseline on the untouched branch: enable Corepack, yarn install at the root and in strapi/, copy strapi/.env.example to strapi/.env, run yarn build in strapi/, import the demo data with the seed script, start the server, and save the JSON answers of GET /api/<plural> for every content type under strapi/src/api in locales en and fr, plus one findOne per collection type. Then stop the server and run npx @strapi/upgrade minor in strapi/, keeping its full output. Read the target version's engines from the registry and compare with this app's engines field and the README's Node requirement; if the minimum rose, update both and say so first in the pull request. Rebuild, start on the same database, repeat every request and diff against the baseline. Regenerate the committed types with yarn strapi ts:generate-types. Check git diff on strapi/package.json: only version lines and engines may change, not the strapi.uuid field. Do not upgrade @strapi/plugin-seo or any other dependency in the same pull request. If the build fails or an answer differs, find the cause in the release notes between the two versions, fix what belongs in this repository, and list anything left. If the app is already on the newest release, end with one line saying so and open nothing. In the pull request give the versions before and after, the upgrade tool's output, the build result and a table of the requests compared.","resources":[{"url":"https://github.com/your-org/your-app"}]}