v0.1.3
Added
- The v2 session token from a successful login is now cached to disk (
config/.token-v2,0600) and reused on the next start, so the server no longer re-runs the username/password login (user/signon) on every construction. That endpoint is the one TickTick rate-limits with HTTP 429, so reusing the token -- as a logged-in browser does -- avoids the throttle entirely. A stale cached token is detected (the startup sync rejects it), cleared, and replaced by a single fresh login that repopulates the cache.
Full Changelog: v0.1.2...v0.1.3