Marc-André Bombeck eac40e79d6 fix(api): a bad dimension skips its own bulk entry, as the contract said ...

The doc comment beside `a1`..`a5` promised that an out-of-range value marks
THAT entry skipped and never the batch, while the fields sat in the batch
schema and answered 422 for all five hundred. The words were right and the
code was not, and a phone draining a year of local history lost the year to
one row.

The five now parse per entry, the same way the day context does; a bad row
reports `invalid_dimensions` and the rest of the batch lands.

The split buys the tolerance and costs a second copy of "0 to 10", so a guard
offers the same value to both schemas and makes them agree at both ends of the
scale and one step outside each.

2026-08-08 09:58:50 +02:00

..

fixtures/v137

chore: drop two exports nothing reaches

2026-08-07 10:25:52 +02:00

integration

fix(api): a bad dimension skips its own bulk entry, as the contract said

2026-08-08 09:58:50 +02:00