add daily challenges

Author: stringhandler

meta/tasks/backlog/challenge-history-page.md

@@ -0,0 +1,28 @@
+# Challenge History Page
+
+Extracted from `weekly-challenges.md`. Depends on `weekly-challenge-progress` and `daily-challenge-core`.
+
+## Goal
+View past completed and failed challenges (both weekly and daily) in a combined history view.
+
+## Route
+`/challenges/history`
+
+## Layout
+- Filter tabs: All | Weekly | Daily
+- Grouped by week
+- Each entry shows: type icon, description, status (✅/✗), completion date or failure note, target achieved
+
+## Tauri Command
+```rust
+fn get_challenge_history(
+    challenge_type: Option<String>,  // "weekly", "daily", or None
+    limit: i32
+) -> Result<Vec<ChallengeHistoryItem>, String>
+```
+
+## Acceptance Criteria
+- [ ] Lists past challenges from `challenge_history` table
+- [ ] Filter tabs work (weekly/daily/all)
+- [ ] Grouped by week with clear date headings
+- [ ] Empty state handled gracefully

meta/tasks/backlog/weekly-challenge-generation.md

@@ -0,0 +1,58 @@
+# Weekly Challenges – Generation & Reroll
+
+Extracted from `weekly-challenges.md`. Depends on `daily-challenge-core` (shares `challenge_history` table).
+
+## Goal
+Generate 3 diverse weekly challenge options each Sunday. Allow 2 rerolls before acceptance.
+
+## Database
+```sql
+CREATE TABLE challenge_options (
+    id INTEGER PRIMARY KEY AUTOINCREMENT,
+    week_start_date TEXT NOT NULL,
+    challenge_type TEXT NOT NULL,
+    challenge_description TEXT NOT NULL,
+    challenge_target INTEGER NOT NULL,
+    challenge_target_games INTEGER,
+    hero_id INTEGER,
+    metric TEXT,
+    option_index INTEGER NOT NULL,  -- 1, 2, 3
+    reroll_generation INTEGER DEFAULT 0,
+    created_at INTEGER NOT NULL
+);
+
+CREATE TABLE weekly_challenges (
+    id INTEGER PRIMARY KEY AUTOINCREMENT,
+    week_start_date TEXT NOT NULL,
+    challenge_type TEXT NOT NULL,
+    challenge_description TEXT NOT NULL,
+    challenge_target INTEGER NOT NULL,
+    challenge_target_games INTEGER,
+    hero_id INTEGER,
+    metric TEXT,
+    status TEXT NOT NULL DEFAULT 'active',  -- active, completed, failed, skipped
+    accepted_at INTEGER,
+    completed_at INTEGER,
+    reroll_count INTEGER DEFAULT 0,
+    UNIQUE(week_start_date)
+);
+```
+
+## Generation Logic
+- 3 options, diverse types: max 1 hero-specific, max 1 performance, mix variety
+- Hero selection from last 30 games, prefer heroes with 10+ games
+- Difficulty: mix of easy/medium/hard across the 3 options
+- Reroll: delete old options, regenerate, increment reroll_count; max 2
+
+## Tauri Commands
+```rust
+fn get_weekly_challenge_options() -> Result<Vec<ChallengeOption>, String>
+fn reroll_weekly_challenges() -> Result<Vec<ChallengeOption>, String>
+fn skip_weekly_challenge() -> Result<(), String>
+```
+
+## Acceptance Criteria
+- [ ] 3 diverse options generated each Sunday
+- [ ] Reroll generates fresh set, decrements limit
+- [ ] Reroll disabled after 2 uses
+- [ ] Options persist until new week or accepted

meta/tasks/backlog/weekly-challenge-progress.md

@@ -0,0 +1,38 @@
+# Weekly Challenges – Acceptance & Progress Tracking
+
+Extracted from `weekly-challenges.md`. Depends on `weekly-challenge-generation`.
+
+## Goal
+Accept a challenge, track progress against matches played during the week, auto-complete or auto-fail.
+
+## Requirements
+- On accept: set `accepted_at` timestamp; only matches after this time and before week end count
+- Progress evaluated per challenge type (wins, avg stat, hero-specific, etc.)
+- Auto-complete when target reached; auto-fail on Sunday rollover
+- Archive completed/failed challenges to `challenge_history`
+
+## Tauri Commands
+```rust
+fn accept_weekly_challenge(challenge_id: i64) -> Result<WeeklyChallenge, String>
+fn get_active_weekly_challenge() -> Result<Option<WeeklyChallenge>, String>
+fn get_weekly_challenge_progress() -> Result<Option<ChallengeProgress>, String>
+```
+
+## ChallengeProgress struct
+```rust
+pub struct ChallengeProgress {
+    pub challenge: WeeklyChallenge,
+    pub current_value: i32,
+    pub target: i32,
+    pub games_counted: i32,
+    pub days_remaining: i32,
+    pub completed: bool,
+}
+```
+
+## Acceptance Criteria
+- [ ] Accepting locks in challenge, disables reroll
+- [ ] Progress counts only post-acceptance, within the week
+- [ ] Auto-completes when target met
+- [ ] Sunday rollover archives incomplete as failed
+- [ ] `days_remaining` calculated correctly

meta/tasks/backlog/weekly-challenge-ui.md

@@ -0,0 +1,31 @@
+# Weekly Challenges – UI (Selection Page & Dashboard Widget)
+
+Extracted from `weekly-challenges.md`. Depends on `weekly-challenge-progress`.
+
+## Goal
+Build the `/challenges` page for viewing/selecting weekly options, and a dashboard widget showing active progress.
+
+## Routes
+- `/challenges` — main challenge page (selection or active progress view)
+
+## Selection View (no challenge accepted yet)
+- Show 3 option cards with description, type tag, difficulty badge
+- Accept button on each card
+- Reroll button with remaining count ("2 rerolls remaining")
+- Skip This Week button
+
+## Active Progress View (challenge accepted)
+- Challenge description + progress bar (current/target)
+- Days remaining in week
+- List of recent relevant matches with pass/fail indicator
+
+## Dashboard Widget
+- Card showing active weekly challenge with mini progress bar
+- Link to `/challenges` for details
+- Shows "Choose this week's challenge" if none accepted yet
+
+## Acceptance Criteria
+- [ ] Can view 3 options and accept one
+- [ ] Reroll works and shows updated count
+- [ ] Active challenge shows real-time progress
+- [ ] Dashboard widget visible alongside daily widget

meta/tasks/done/daily-challenge-core.md

@@ -0,0 +1,101 @@
+# Daily Challenges – Core Backend
+
+Extracted from `weekly-challenges.md`.
+
+## Goal
+Implement the database schema, generation logic, and Tauri commands for daily challenges.
+
+## Requirements
+
+### Database
+New tables:
+- `daily_challenges` – one row per day, auto-generated at first access
+- `challenge_history` – archived completed/failed challenges (shared with future weekly challenges)
+
+```sql
+CREATE TABLE daily_challenges (
+    id INTEGER PRIMARY KEY AUTOINCREMENT,
+    challenge_date TEXT NOT NULL,        -- "YYYY-MM-DD"
+    challenge_type TEXT NOT NULL,        -- "quick_win", "performance", "efficiency", "participation"
+    challenge_description TEXT NOT NULL,
+    challenge_target INTEGER NOT NULL,
+    challenge_target_games INTEGER DEFAULT 1,
+    hero_id INTEGER,                     -- NULL for non-hero challenges
+    metric TEXT,                         -- "wins", "kills", "gpm", "last_hits", "deaths", "hero_damage"
+    status TEXT NOT NULL DEFAULT 'active', -- active, completed, failed
+    created_at INTEGER NOT NULL,
+    completed_at INTEGER,
+    UNIQUE(challenge_date)
+);
+
+CREATE TABLE challenge_history (
+    id INTEGER PRIMARY KEY AUTOINCREMENT,
+    challenge_type TEXT NOT NULL,        -- 'daily' (or 'weekly' later)
+    period_start_date TEXT NOT NULL,
+    challenge_description TEXT NOT NULL,
+    status TEXT NOT NULL,                -- completed, failed
+    completed_at INTEGER,
+    target_achieved INTEGER
+);
+```
+
+### Challenge Types & Templates
+Use a fixed template list with hero/stat filled from player history:
+
+**Quick Win (easy):**
+- "Win 1 game today"
+- "Win 1 game with [Hero]" (hero from last 10 games)
+
+**Performance (medium):**
+- "Get [N]+ kills in one game" (N = avg kills + 2, min 10)
+- "Achieve [N]+ GPM in one game" (N = avg GPM + 30, min 400)
+- "Finish with positive KDA in one game"
+- "Deal [N]+ hero damage in one game" (N calibrated to avg, min 15000)
+
+**Efficiency (medium):**
+- "Get [N]+ CS at 10 minutes" (N = avg CS@10 + 5, min 50) – requires parsed matches
+- "Die [N] times or less in one game" (N = avg deaths - 1, max 3)
+
+**Participation (easy):**
+- "Play 2 games today"
+- "Play a game with [Hero]" (hero not played in last 7 days)
+
+### Generation Logic
+- 60% Easy (quick_win / participation), 30% Medium (performance), 10% Hard
+- Check last 7 daily challenges to avoid repeating same type consecutively
+- For hero-specific challenges, pick from matches in last 10 games
+- Auto-generate when first accessed for the day; cache in DB
+
+### Daily Streak
+- Count consecutive days where `status = 'completed'` going back from yesterday
+- Return 0 if yesterday was not completed
+
+### Archive Logic
+- On each call to `get_current_daily_challenge`, check if any `active` challenges exist for past dates and mark them `failed`, archive to `challenge_history`
+
+### Tauri Commands
+```rust
+fn get_daily_challenge() -> Result<Option<DailyChallenge>, String>
+fn get_daily_challenge_progress() -> Result<Option<DailyChallengeProgress>, String>
+fn get_daily_streak() -> Result<i32, String>
+```
+
+### DailyChallengeProgress struct
+```rust
+pub struct DailyChallengeProgress {
+    pub challenge: DailyChallenge,
+    pub current_value: i32,     // e.g. wins so far today
+    pub target: i32,
+    pub completed: bool,
+    pub games_counted: i32,     // number of matches evaluated
+}
+```
+
+## Acceptance Criteria
+- [ ] Tables created in `init_db`
+- [ ] Daily challenge auto-generated on first access each day
+- [ ] Old active challenges auto-archived as failed
+- [ ] Progress evaluated against today's matches (after midnight)
+- [ ] Challenge auto-marked completed when target met
+- [ ] Streak correctly calculated from history
+- [ ] All 3 Tauri commands working

meta/tasks/done/daily-challenge-dashboard-widget.md

@@ -0,0 +1,38 @@
+# Daily Challenges – Dashboard Widget
+
+Depends on: `daily-challenge-core`
+
+## Goal
+Show today's daily challenge progress on the dashboard with streak tracking.
+
+## Requirements
+
+### Widget States
+- **Active**: Show description, progress bar, time until midnight ("resets in Xh Ym")
+- **Completed**: Show "✅ Daily Complete!" with time completed and current streak
+- **No matches yet**: Show at 0% progress with motivational copy
+- **Loading/no challenge**: Skeleton/spinner
+
+### Layout (fits within existing dashboard card grid)
+```
+⚡ Today's Challenge
+Get 10+ kills in one game
+[████░░░░░░] 0/1
+Resets in 8h 23m
+🔥 3 day streak
+```
+
+### Behaviour
+- Load on dashboard mount alongside existing goal calendar
+- Refresh after `refresh_matches` is called (re-invoke `get_daily_challenge_progress`)
+- Does NOT need its own refresh button — piggybacks on existing match refresh
+
+### Navigation
+- No dedicated challenges page needed yet — widget is self-contained
+
+## Acceptance Criteria
+- [ ] Widget visible on dashboard
+- [ ] Shows correct progress after fetching matches
+- [ ] Countdown to midnight updates each minute (use `setInterval`)
+- [ ] Streak displayed when > 0
+- [ ] Completed state visually distinct from active state