{"agent":"codex","input":"Move the Strapi backend in strapi/ from SQLite to PostgreSQL and open a pull request. Read AGENTS.md, README.md, the root package.json scripts, strapi/package.json, strapi/.env.example, strapi/.gitignore and every file under strapi/config first, and list what the postgres branch of config/database.ts already reads and what is missing around it. Docker is not available: install PostgreSQL from system packages, start it, and create a role and a database for Strapi. Baseline on SQLite: enable Corepack, yarn install at the root and in strapi/, copy .env.example to .env, yarn build, import the demo data with the seed script, start the server and save the JSON answers of GET /api/<plural> for every content type in locales en and fr. Export with strapi export --no-encrypt and keep its summary table. Then add pg to strapi/package.json, set DATABASE_CLIENT=postgres and the connection variables in .env, rebuild, start once against the empty database so the schema is created, stop, run strapi import with the export file, and compare its summary with the export's. Start again, repeat every request and diff against the baseline; explain any difference. Check the tables with psql. Keep SQLite as the default client and keep better-sqlite3. Add the DATABASE_ variables to .env.example, commented, with one line each on DATABASE_SSL and DATABASE_SSL_REJECT_UNAUTHORIZED for hosted databases, and add a short Postgres section to the README with the export and import steps. Search the front-end folders for content API filters and report any whose matching is case-sensitive on PostgreSQL and was not on SQLite, without editing them. Do not commit .env, the export file or any database file. In the pull request include both summary tables, the request comparison, and a cutover checklist: export, create the admin user, recreate API tokens, move uploads.","resources":[{"url":"https://github.com/your-org/your-app"}]}