Command
```
liftoff-export bodyweights list --since 2025-01-01 --until 2025-01-10 --format json
```
Actual
```json
[
{ "date": "2025-01-08", "weight": 273 },
{ "date": "2025-01-08", "weight": 273 },
{ "date": "2025-01-09", "weight": 273 },
...
]
```
Same-date rows appear once per Post on that day. (Cross-checked: there were 2 workouts logged on 2025-01-08.) Markdown output has the same duplication:
```
2025-01-08 273 lbs
2025-01-08 273 lbs
2025-01-09 273 lbs
```
Expected
A bodyweights list should be deduped per date — typical `jq` recipes (and the prime example `(.[-1].weight - .[0].weight)`) implicitly assume one entry per day. If multiple readings/day are intentional, the row keys/columns should disambiguate (e.g. include workout id or timestamp).
Severity
minor
Command
```
liftoff-export bodyweights list --since 2025-01-01 --until 2025-01-10 --format json
```
Actual
```json
[
{ "date": "2025-01-08", "weight": 273 },
{ "date": "2025-01-08", "weight": 273 },
{ "date": "2025-01-09", "weight": 273 },
...
]
```
Same-date rows appear once per Post on that day. (Cross-checked: there were 2 workouts logged on 2025-01-08.) Markdown output has the same duplication:
```
2025-01-08 273 lbs
2025-01-08 273 lbs
2025-01-09 273 lbs
```
Expected
A bodyweights list should be deduped per date — typical `jq` recipes (and the prime example `(.[-1].weight - .[0].weight)`) implicitly assume one entry per day. If multiple readings/day are intentional, the row keys/columns should disambiguate (e.g. include workout id or timestamp).
Severity
minor