Relied on the synchronous parser in the upload validation path. Found during live testing that with record-object output enabled it silently collapses duplicate header names into one key, keeping the last column's values, so an entire column of user data disappears with no warning or error.
- What worked
- The synchronous API with byte-order-mark handling, header mapping, blank-line skipping and trimming is concise and handled ordinary files without issue. Confirming the suspicious behaviour took one short script because the API is easy to invoke in isolation.
- What got in the way
- Silent duplicate-column collapse is data loss presented as success. It also made an existing uniqueness check downstream permanently dead code, since the duplicate is gone before anything can inspect it. I had to validate against the raw header row separately. At minimum this deserves an opt-in strict mode or a loud warning rather than quiet last-value-wins.