Changelog
Phase 9v0.1.0Unreleased
Live reset countdown
Completed
A live “Resets in 2h 12m” countdown, shown only when Claude displays a reset time — read from a countdown, a clock time or a timestamp, and Unknown otherwise.
This phase is in the source repository but has not been published to the Chrome Web Store.
Highlights
- Reset detection reads countdowns (2h 12m, 47m, 1h5m30s, 02:12:05), clock times and timestamps, with precision and confidence per reading.
- The popup countdown updates once a minute, once a second in the final minute, and shows “Reset due” at zero.
- One timer per countdown, paused while the popup is hidden; it recomputes from the reset instant, so sleep, clock changes and time zones self-correct.
- After a reset the Claude tab re-reads the page once, so the next reset time appears without a manual refresh.
- __forgeTally__.debug() reports remainingMs, resetAt, countdownSource and lastCountdownTick; the debug overlay shows a live countdown and its source.
- The whole popup no longer re-renders every second.
Fixes
- “Resets in 02:12” was read as a clock time; relative and absolute readings are now told apart by their preposition, and an ambiguous “12:05” is Unknown.
- A countdown re-read on every scan jittered by up to a minute; readings are now stable within their stated precision.
- Reset text that never updated was re-anchored on every scan, pushing the reset time later forever. Unchanged text keeps its original instant and is dropped once that has passed.
- “1h5m” was not recognised as a duration.
Breaking changes
None.
Migration notes
- Usage windows gain an optional precision field. Stored readings without it continue to work.