[YarinQuapi]

What changed

• Mobile: a "Report a bad scan" button on the food form (after a scan) and on the "nothing found" screen. It asks for an optional note, then uploads a downsized JPEG (max 1600 px), the recognized text and the parsed values.
• API: new `ScanReport` table (migration `20261110120000_scan_reports`) and `/api/scan-reports`:
  • `POST /` any signed-in user (own 7 MB JSON limit, photo capped at 4 MB)
  • `GET /`, `GET /:id/photo`, `POST /:id/resolve` admin only
• Export script: `npm run export-scan-reports -- ` writes each open report as `.jpg`, `.txt` and `.json` so real failures can become parser tests.
• Docs: `docs/ideas.md` backlog of improvement ideas.

Why

Liquid and some real labels still misread, and the parser can't be tuned without real examples. Reports build a test set from actual use.

For reviewers

• Deploy needs `prisma migrate deploy` on the server before the endpoint works.
• Photos are stored in the database (LONGBLOB), a few hundred KB each.
• The scan-reports router is mounted before the global 1 MB JSON parser on purpose.
• No admin UI yet; reports are read via the export script or the API.

Testing

• API typecheck and 45 tests pass. Endpoints exercised against a local MySQL: create (201), non-admin list (403), anonymous (401), oversize photo (400), admin list/photo/resolve, export script. Test accounts removed afterwards.
• Mobile: `flutter analyze` shows only existing infos; 17 tests pass.
• Not tested: upload from a real iPhone, Hebrew/RTL layout of the dialog.

🤖 Generated with Claude Code