6 Commits

Author	SHA1	Message	Date
Krzysztof kuhy Rudnicki	bbc14ec04c	earned_time 0.6.0: per-day registry consumer, sleep-ladder date-proof tests, pin v0.6.0 ... Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>	2026-10-09 21:36:53 +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	6a07dc56aa	Reading hour from book-guard: +1h shutdown; base 20->19 from 2026-10-01 ... Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-09-26 19:02:24 +02:00
Krzysztof kuhy Rudnicki	02a93f1322	Shutdown +1h on a day with a LeetCode solve; base moves 21:00 -> 20:00 ... Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-09-15 20:06:26 +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