feat(app): implement Product Scan review flow, dynamic batch expiry picker, custom PDFs, PO relationships, and aligned card layouts

backend/SKILLS.md

@@ -67,9 +67,8 @@ against; gives QA the list of new/changed endpoints and their expected error mod
   concrete acceptance criteria — what "done" verifiably means.
 - Write/extend automated tests (`parser.test.ts` pattern) for the change.
 - For anything touching `parser.ts` or the OCR pipeline, run the accuracy
-  regression harness (`node pfm-web-app/scripts/accuracy-check.mts`) and check for
-  regressions against the current baseline (~89.4% overall, target 95% — see
-  backend `CLAUDE.md`), not just "it compiles."
+  regression harness (`node pfm-web-app/scripts/accuracy-check.mts` or `accuracy-check-scan.mts`) and check for
+  regressions against the current baseline (see `sources/accuracy_history.jsonl` and `sources/product_accuracy_history.jsonl` for latest metrics), not just "it compiles."
 - Run the **verify build integrity** pass: golden path + edge cases + regression
   check on adjacent features.
 - Reject work back to the relevant role if acceptance criteria aren't met — don't