v1.6.1

• Today's activity counts no longer start the day holding yesterday's.
  The calendar is read at most hourly, and that hour was counted in elapsed
  time alone. A reading taken shortly before midnight therefore sat inside its
  hour well past midnight, serving yesterday's totals and summary under a name
  that says today. The cached figures now carry the date they counted, and
  midnight in your account's timezone ends it.
• A new day that cannot be fetched reads zero rather than yesterday's numbers.
  Carrying values over is right within a day and wrong across one. The hourly
  backoff is unaffected, so a rate-limited account still gets one attempt.
• Signing back in around midnight no longer restores yesterday's counts.
  The figures kept between fetches are now held with the date they counted,
  rather than read back off the last stored update. That stored update is only
  replaced when a whole refresh succeeds, so a refresh that read the calendar
  and then failed on something later left the previous day's numbers in place
  to be picked up and relabelled. A dead token also no longer spends the hour:
  it is not this host refusing us, so the refresh after renewal can ask
  again rather than sitting the hour out on nothing.
• Signing back in through the add-on clears the add-on's warning. The
  notice about it waiting for a verification code stayed up after a recovery
  that had visibly just worked, with nothing to press. A password sign-in
  still leaves it alone, because that says nothing about the add-on.