Implement streak tracking with persistence and frontend context #213
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.

Closes #161
Implement streak tracking with persistence and frontend context
Body
add daily streak entity + service with timezone-safe updates and duplicate-day guard
expose /streaks and /streaks/update endpoints with optional timezone input
introduce StreakProvider/useStreak on frontend and wire streak page to live data
Test Plan
BE: call POST /streaks/update twice same day → no double increment
BE: call POST /streaks/update on consecutive days (or simulate via date headers) → streak increments; skip a day → resets to 1
FE: load /streak with valid token → weekly calendar matches backend streakDates; streak count shows current
FE: trigger updateStreak() after completing daily quest → streak count updates without page reload