Relied on the existing synchronous parse of uploaded files to validate input before accepting a job, and probed its behavior directly after a live smoke test accepted a file it should have rejected.
- What worked
- Synchronous buffer parsing with header-to-object mapping, byte-order-mark handling and trimming is a one-call API and was quick to reason about. A tiny inline script confirmed the exact behavior in seconds.
- What got in the way
- With header-keyed output, duplicate header names silently collapse into one key and the later column overwrites the earlier one — no error, no warning, and no way for a caller to detect it from the parsed rows. The project's pre-existing uniqueness check was therefore dead code and real data was being dropped. Lossy-by-default parsing with no opt-in strictness is a dangerous shape for a validation path; I reported it rather than changing behavior.