12 Commits

Author	SHA1	Message	Date
Krzysztof kuhy Rudnicki	46393fa866	late credits: a credit at/after tonight's shutdown sets it to min(23:00, its own time + reward); grace floor removed (also on sick days) ... Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>	2026-10-17 18:14:04 +02:00
Krzysztof kuhy Rudnicki	7d8daca111	sick days: one shared sickdays pool, 20:00 shutdown floor, one-tap lock button ... A sick day is now a date in the shared sickdays pool (utils sickdays 0.1.0) and nothing else. Removed: the 7/30/90-day budget, the escalating lockout countdown, the justification form, the commitment prompt and its double debt, the workout-debt counter, the -60 min shutdown cut and its sick_day_state.json, the post-sick-day --verify-workout mode, the sick auto-upgrade, scripts/revoke_sick_day.py and their tests. - Lock screen: "I'm sick" on the retry, no-phone and both Tue-Thu screens; one tap -> sickdays.add_sick_day(today) -> sick floor -> best-effort background sickdays.sync_quietly -> unlock. Refusals (free day, unreadable pool) are shown and the lock stays. - Shutdown: the reset resolves with earned_time.resolve(..., sick=True) (max(20:00, ladder), capped 23:00) and saves the sick lift with the grace lift, so later credits absorb it instead of stacking on 20:00. A day marked after the reset is lifted by the new _sick_floor live pass (every 5-min tick, --sync-only, --apply-bonuses, and the tap itself). - Workout lock and grace floor stand down on a sick day; workouts that day credit normally through the sync paths. - wake-alarm workday_penalty.json is void when its issued_date or penalty_date is a sick day. - Status window, i3 line, CLI --status, MCP flags and web reasons read sickdays. - scripts/migrate_sick_history.py imports sick_history.json's dates via sickdays.import_legacy, verifies and removes the file; idempotent, run by install.sh. - Pins: earned-time 0.11.0, freedays 0.4.0, sickdays 0.1.0 (tags pending); pre-commit 4.7.0, ruff 0.17.1 (freshness gate). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Xfj1sxKH9VBPqpcAni8Jry	2026-10-16 13:30:39 +02:00
Krzysztof kuhy Rudnicki	aedfdbc7f5	Credit: one reward per workout slot, desktop notification, --help, runnerup-watch ignores re-pulls ... Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018RHwVPyiiQMPh4M3JQwQku	2026-10-09 19:05:08 +02:00
Krzysztof kuhy Rudnicki	373a075606	Shutdown: walks as workout, rest days, grace floor, workout ledger (earned-time 0.4.0) ... - A day's RunnerUp walks (_Walking.tcx) count once their moving time sums to 40 min - Rest days: declared ahead, 2 per ISO week, HMAC-signed; pay the first workout unit - Grace floor: shutdown >= first task + 60 min (capped); skipped on a sick day - Workout ledger: one signed credit row per log credit slot and rest day - Day-aware ladder amounts from earned_time 0.4.0; preview_shutdown dry-run script Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QrjUTo1yhgAsUUasdw4bpG Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-10-09 10:43:45 +02:00
Krzysztof kuhy Rudnicki	275a0862fc	shutdown: minutes end to end (*_MINUTES schedule keys, HH:MM helper args, to_hours removed) ... Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-10-04 19:48:24 +02:00
Krzysztof kuhy Rudnicki	ed5fa133d0	shutdown: derive base and bonuses from the shared earned_time registry ... The base hour, the workout/LeetCode/reading hours and the reading cut date were duplicated here and in steam-backlog-enforcer. They now come from earned_time (kuhyx/utils, earned-time-v0.1.0): the reset sums the registry, the live pass iterates its flat earners (stamps unchanged: <name>_bonus_date), and _leetcode_bonus/_reading_bonus are replaced by the shared HMAC ledger reader. A gate registered later needs no code here. The schedule still stores whole hours; _earned.to_hours raises on a remainder rather than flooring it. Verified identical to the old code on today's real ledgers and log (reset target, stamps, live passes, base hours). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Aktgaq93yt51c6D3X5Fzsm	2026-10-04 18:55:51 +02:00
Krzysztof kuhy Rudnicki	82f3462896	Replay today's earned shutdown credit in the daily base reset ... The i3bar showed 21:00 on 2026-09-13 with a counted workout on disk. The football was logged at 00:02 and credited against the previous day's config (already at the 23 ceiling, so it bought nothing); the 09:15 base reset then wrote 21/21 and only re-layered the weekly bank, never asking what today's log had already earned. Live credits are read-add-write, so every workout credited between local midnight and the first locker tick of the day lost its hours to the reset that followed. - _shutdown_base.reset_to_base_if_new_day takes the log and writes min(23, base + hours today's entries earned) in one write, using the same credit rule as the weekly count. Idempotent: still once per day. - _workout_credit names FIRST_WORKOUT_BONUS_HOURS=2 / EXTRA_WORKOUT_BONUS_HOURS=1 and derives earned_shutdown_bonus_hours() from them; _shutdown and the +1h path use the constants instead of literals so the replay and the live paths cannot drift. - _weekly_check.credit_key: a synced copy whose sync_record_id names an entry already filed on the same day shares that entry's slot. This morning's rekey (967e3cd) let the sync pull the football back in as manual:2026-09-13T14:30, which counted as a second credit (weekly 4/5 instead of 3/5) and would have made the replay ask for 24. - annotate_duplicate_credits.py passes the day's id index so the ledger records the manual duplicate the same way it records phone/PC pairs. Verified through the real path: cleared last_reset_date, started workout-locker.service -> "--restore 23 23 5", "Daily base reset: Mon-Wed=23, Thu-Sun=23 (base 21/21 + 2h already earned today)", shutdown_countdown.sh prints "23:00"; a second start changed nothing. leetcode-guard grants no shutdown time anywhere (grepped screen-locker, digital-wellbeing, i3 config) — the 23:00 comes from the workout alone. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01C7vgacLhb4WJjxuVj2QLEP	2026-09-13 20:00:05 +02:00
Krzysztof kuhy Rudnicki	a48bd1334a	Credit StrongLifts sessions from the headless sync, as pc_workout_verified ... `sync_now()` -- what workout-sync.timer runs every 15 minutes -- only ever ingested MANUAL records. The session reader `pull_synced_workout()` was reachable only from `_verify_phone_workout`, i.e. the interactive lock/status UI, so a finished session earned nothing until a lock screen happened to open. That was survivable while the phone was the only device recording sessions: the same lock screen that demanded the workout also verified it. The Linux build finishes sessions with no lock screen involved at all, so the credit would simply never arrive. `pull_all_session_records()` is the session counterpart to the existing `pull_all_manual_records()` -- `pull_synced_workout` returns only the single newest session for the live unlock check, which cannot backfill a week. New type `pc_workout_verified` rather than reusing `phone_verified`: it is machine-checked in exactly the same way (same WorkoutSession payload, same set/rep and duration validation), but there is no phone involved, and writing "phone_verified" into an HMAC-signed log would make the log lie about its own provenance. Ingestion re-derives the verdict instead of trusting the record's `succeeded` flag -- the record arrives over the network and this is the thing handing out unlock credit. Every rejection logs at WARNING with an actionable reason, per the repo's no-silent-failures rule. One real leak fixed along the way: formatting the duration with `.0f` rounded 34m59s up to "35 min", which is precisely the hidden accept bar -- the message would have told the user the real threshold while rejecting them at it. It now truncates, so the advertised 40 stays the only number shown. Verified against live data: ingests the 4 real synced sessions, and a second run ingests 0 (the write chokepoint dedups by workout_id), so the repeating timer cannot double-credit. Suite green at 100% branch coverage, 1046 tests. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DfJC1Wu1SEgJ6X49k5Jqtg	2026-08-22 11:26:20 +02:00
Krzysztof kuhy Rudnicki	c1c73d43ba	Stop the relaxed-day popup from re-firing every 30 minutes after Skip ... workout-locker.timer (added in e5db254) re-runs the full lock-decision chain every 30 minutes, but is_relaxed_day() is a pure date check with no memory of an earlier same-day dismissal. Clicking "Skip — No Penalty" only closed the window without persisting anything, so the next tick re-derived reason=relaxed_day and rebuilt the same popup. Now the skip button writes a relaxed_day_skip marker to the log (excluded from weekly counting and sync, same treatment as heat_skip), and the startup chain checks for it before re-entering the relaxed-day branch. Also renames workout_log.json to log.json throughout the repo, tests, docs, and Dart comments, since the fix touches that file anyway. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014qH2hJ6mvCJd3ZXpAJSaF7	2026-08-18 21:55:59 +02:00
Krzysztof kuhy Rudnicki	298daf028d	Give manual workouts full effect parity; raise minimum to 5, double budget ... Synced manual workouts never earned shutdown/debt credit (only weekly count), which silently missed pushing shutdown time for a same-day workout logged on the phone. Manual workouts now go through the same credit logic as any other workout type, count individually toward the weekly total and rate budget (no more once-per-day collapse), and stack same-day shutdown bonuses like verified workouts. Also bumps the weekly minimum from 4 to 5 and doubles the monthly manual-workout budget to 10. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-07-19 13:50:39 +02:00
Krzysztof kuhy Rudnicki	79879263ba	Support multiple workouts per day; fix the dead sync; ban silent failures ... The workout log stored ONE workout per calendar day, so a second same-day workout was silently dropped and could never earn credit. Multiple workouts per day: - workout_log.json: {date: entry} -> {date: [entry, ...]}. Legacy entries are wrapped on read (_log_io.load_workout_log) so their HMACs stay valid — no re-signing; every write normalizes the file, migrating it progressively. - New write chokepoint (_log_mixin.write_signed_entry) APPENDS and dedups by a stable workout_id, returning RecordResult so callers can tell a new workout from a duplicate. Re-verifying the same workout is a no-op. - count_weekly_workouts is anti-gaming: each VERIFIED workout counts individually; self-reported manual entries count at most once per day. Four real workouts in one day satisfy the week; four manual entries count as one. - Reward: the day's first counted workout gets the base +2h; an additional same-day VERIFIED workout gets +1h; an additional manual gets nothing. The old "+1h when weekly_count > 4" gate is replaced — weekly volume is the banked bonus's job and shouldn't be paid twice. - Fixed: the unlock screen labelled the +1h "#{weekly_count - 4}", which can render negative under the new rule. Removed the dead runnerup_manual type. - Flutter: the manual budget counts distinct DAYS, matching the PC. PC->phone sync (it had never worked once): - push_pc_manuals pushed from a side-store written at log-time, so anything logged before that feature existed could never publish. _manual_push now derives the crdt log directly from workout_log.json — the single source of truth — covering manual AND verified runs. The record id is the workout's own workout_id (derived for legacy entries to match the phone's format) and the HLC comes from the entry's own timestamp, so a re-push is byte-identical and the repo never churns. - The phone reads every kind (readMergedWorkoutPayloads) and lists the PC's workouts under "SYNCED FROM PC". The manual budget still sees manual-only, so a verified run can't consume a self-report slot. - Settings claimed "Connected." whenever a token STRING existed. It now verifies against the API on open, so a revoked token reports 401 instead of showing a green lie. Never fail silently: - 30 swallowed exceptions across 19 files now log WARNING with the concrete cause AND consequence — plus the token guards in _workout_sync that returned [] in total silence, the exact bug that hid the dead sync for weeks. - New pre-commit hook (scripts/check_silent_failures.py) fails any except that neither re-raises nor logs loudly. ruff's S110 only catches `except: pass`; the real pattern here was `except: log.info(); return []`. Documented in CLAUDE.md. Verified on real data: the Jul 13 run (pulled from its actual TCX over ADB) now counts alongside that day's manual squash, and all three workouts are published to kuhyx/syncs. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Fv8ULVt3Q67GwCFbM7doHB	2026-07-17 09:22:31 +02:00
Krzysztof kuhy Rudnicki	d9119a6582	Add manual (unverified) workout logging with evidence form ... Adds a rate-limited manual-workout entry point (StatusWindow + locked retry screen) for activities like table tennis that ADB/RunnerUp can't verify, gated by a 2/7d + 5/30d budget and a detailed evidence form rather than free text. Full credit toward the weekly minimum, debt clearing, and commitment prompt, matching phone/RunnerUp verification. Also stops tracking personal runtime state (workout_log.json, sick_history.json, extra_benefits_state.json, scheduled_skips.json, shutdown_base.json, early_bird_pending.json) in git — these are regenerated locally and never belong in a public/private repo's history. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AbPcvAvt1JhiRzEyPDE5dA	2026-07-05 20:08:52 +02:00