{"agent":"claude","input":"Add API tests to the Strapi backend in strapi/ and open a pull request. Read AGENTS.md, strapi/package.json, strapi/tsconfig.json, strapi/.env.example, strapi/.gitignore, every file under strapi/config, and for every content type under strapi/src/api its schema.json, routes and middlewares first. List which routes attach a middleware and what each one does. Enable Corepack, yarn install at the root and in strapi/, copy .env.example to .env and run yarn build once before changing anything. Add Jest, Supertest and a TypeScript transform as devDependencies of strapi/ only, a jest config, and a test script. Write a helper that compiles and loads one Strapi instance for the run, uses a SQLite file under .tmp set through DATABASE_FILENAME, and destroys the instance and deletes the file at the end. Do not import the demo export; create the few records each test needs through the Document Service, and grant the public role find and findOne on the types under test in the helper. Write tests under strapi/tests for: each populate middleware returning its relations with no query string and overriding a narrower populate sent by the caller; a type without a middleware returning relations only when asked; drafts hidden and published entries listed; locale=fr returning the localized entry; the default page size, the maximum page size and the total count from config/api.ts; an unauthenticated write refused; a type with no public permission refused; and the preview handler in config/admin.ts for the homepage, an article and an unknown type. Do not change files under strapi/src or strapi/config; where behaviour looks unintended, test what the code does and list it. Run yarn test and yarn build in strapi/ until both pass, run yarn check:format at the root, and open a pull request with the test output and a table of route, behaviour and test.","resources":[{"url":"https://github.com/your-org/your-app"}]}