[amar-python]

Fixes #190.

Summary

T&E uploads stored column_types = [], so review treated every value as text. It returned errors: [] for rows the database rejected on a CHECK, FK or UNIQUE constraint.

• api/services/te_loader.py: returns the target table's mapped column types instead of []. record_upload stores them, so review now type-checks T&E values against the target. Types the API can't check itself (uuid, enums, arrays) still review as text.
• api/services/review.py: for T&E uploads, the database's upload-time reason (stored in uploads.row_errors) is added to the row's errors as {"column": "(database)", ...}. It is dropped once the row has a cell edit, because the original rejection no longer describes the edited row.
• csv-table-hub-main/src/components/review-table.tsx: one line, so any error not tied to a column is shown beside the row. Before, only (beyond header) was shown, so the row said "Invalid" with no reason.

Known limits (not fixed here)

• Row numbers depend on RV-F12: T&E row errors point to wrong source record numbers (survivor-list position) #189. On main, per-row database errors give the row's position in the list of rows that passed the type check, not its CSV row (RV-F12: T&E row errors point to wrong source record numbers (survivor-list position) #189, fixed in fix: address 15 open issues — security, data integrity, tests, CI #202). If an earlier row fails the type check, the reason can land on the wrong row until fix: address 15 open issues — security, data integrity, tests, CI #202 merges. This PR doesn't touch that loop, so it shouldn't conflict with fix: address 15 open issues — security, data integrity, tests, CI #202.
• The stored error list is capped at MAX_ROW_ERRORS_REPORTED, so rows past the cap show no database reason.
• Edited T&E rows are re-checked against types only, not against database constraints. That check happens at M6's staged import (ART M6: approval and transactional staged import (BR-32, BR-33, BR-34; ADR-0002) #110).
• T&E uploads made before this change still have no stored types, so they review as text. They do still show the stored database reasons.

Test plan

• New tests/test_review.py::test_te_review_shows_the_database_reason_a_row_was_rejected: uploads an organisations CSV with a bad org_type. Review returns the CHECK reason, and an edit clears it. Failed before the fix (errors: []).
• test_review.py, test_review_cases.py, test_te_loader_integration.py, test_preserved_uploads.py, test_failed_uploads.py pass against a local PostgreSQL 16 dev deploy. The dynamic-mode review tests still pass.
• Free tier (unit or regression or security or snapshot) passes.
• vitest 147/147, with a new assertion in review-table.test.tsx for the (database) reason.
• CI integration job

---

Generated by Claude Code

[amar-python]

CI failure on 3382641: tests/test_api_coverage.py::TeUploadPipeline::test_response_shape_matches_contract still asserted types == [] for T&E uploads, which this PR intentionally changes. Not a flake. Fixed in the next commit by asserting one type per column, and the M4 test-case doc line about the old limit is updated. The other failing local runs (parity/environments) only need the staging/test/prod databases, which CI deploys.

---

Generated by Claude Code