# fix\(usage\): keep numeric CLI reset dates parsable \(\#270\) · lucenx/codexbar-plasma

[View on GitCafe](https://git.cafe/lucenx/codexbar-plasma/commit/38d05a9943aa0a19ba61b6c03d801140ac833983)

Repository: [lucenx/codexbar-plasma](https://git.cafe/lucenx/codexbar-plasma)

Visibility: public

Requested revision: 38d05a9943aa0a19ba61b6c03d801140ac833983

Requested commit: 38d05a9943aa0a19ba61b6c03d801140ac833983

Commit: 38d05a9943aa0a19ba61b6c03d801140ac833983

Tree: 77e7ec65f5db2f0fb8f898bfcffb8bf7c0dc1441

Author: Simone

Committer: GitHub

## Message

```
fix(usage): keep numeric CLI reset dates parsable (#270)

ProviderSnapshot stored a numeric resetsAt as its epoch digits, while every
later reader parses that field as a date string: the popup countdown through
ResetPresentation, the panel "resets within" rule through Date.parse, and the
private-mode timestamp projection. A provider reporting a numeric reset date
therefore printed the raw milliseconds instead of a countdown and never
satisfied the reset visibility rule, even though ProviderSnapshot and
ResetPresentation both already accept numeric dates on the resetValue path.

Normalize a numeric reset date to its ISO form when the row is built, out of
range and non-finite values keeping the existing empty reset, and pin the
behavior in tst_provider_snapshot.

Documentation: CHANGELOG Unreleased and the ProviderSnapshot notes in
docs/development.md.

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
```

## Parents

- [cb27eee2e6fd7639bdba5136f4b3bebad2fb445d](https://git.cafe/lucenx/codexbar-plasma/commit/cb27eee2e6fd7639bdba5136f4b3bebad2fb445d?format=markdown)

[Source at this commit](https://git.cafe/lucenx/codexbar-plasma/tree/38d05a9943aa0a19ba61b6c03d801140ac833983?format=markdown)