9 Commits

Author	SHA1	Message	Date
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	279a7b1ed7	repo contract: CLAUDE.md commands, test_changed, CI gate ... Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-10-04 17:15:50 +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	83d77884a0	Workout screen never moves when a rest starts; a sandbox flavor to prove it on the phone ... The rest banner used to be inserted into the column only while a break ran, so its arrival took height from the exercise list, shifted every tile down and pushed the last one into scroll range. The strip is now a permanently reserved 64 dp slot (muted "Rest / 00:00" while idle, Skip keeps its space), the list is a non-scrolling column that scales down as a whole if it would not fit (0.96 on the Pixel 6a with four tiles, pinned by a widget test at the phone's logical size with the status bar simulated), and the activity is locked to portrait. Verified on the real phone: only the tapped circle's pixels change when a rest starts. Verifying that needed a workout screen that today's already-logged workout did not offer, so the app gained a `sandbox` product flavor beside `daily`: com.kuhy.workout_app.sandbox installs side by side with its own data, refuses every network connection at the socket layer, starts no LAN server for the PC to pull from, keeps its /sdcard files beside the daily build's, wears a red SANDBOX ribbon, and offers a SANDBOX section in Settings (wipe, mark today not done, rest length in seconds). MainActivity answers the flavor and carries a `WorkoutSandbox` logcat trace of every tap, break, save and navigation. On Linux the same mode is WORKOUT_SANDBOX=1, driven under Xvfb by scripts/run_sandbox_xvfb.sh. CI builds --flavor daily; .phone-deploy-flavor tells phone_deploy.sh the same. Set circles and the home icon buttons carry semantics labels so they can be addressed by element (and by screen readers). Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01YbBZqUaNWyhHYfzz6zGC7q	2026-09-20 18:55:08 +02:00
Krzysztof kuhy Rudnicki	9ab7c09c79	The early-bird window is the wake-alarm carrot, not a clock ... 05:00-08:30 (09:00 with the extended reward) locked nobody but did hold the workout lock off on a clock that knew nothing about whether the user was up, next to the morning-session rung that did. EarlyBirdMixin._is_early_bird_time is now that rung's verdict: open before the alarm, during the session, and until 11:00 once it completed in time -- exactly what wake-alarm signs. The wake_alarm_skip rung banks the pending marker so the carrot's end still tries a phone/RunnerUp workout before locking; early-bird-workout-check.timer moves to 09:30:30 and 11:00:30, the two possible ends. The consumer's boot-retry window starts at 05:00 with the refresher. Also: the sick screen lists four past justifications, one line each -- six full-length ones pushed it 7 px past 1366x768, which the screens-fit gate only sees with a real history on disk. Takes @types/node 26.6.2, eslint 10.11.0. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01XTdfXjbGYYrY7Quxcfz6mg	2026-09-20 08:39:44 +02:00
Krzysztof kuhy Rudnicki	53bbdda419	Read the morning-session carrot from wake-alarm's signed file ... The wake_alarm_skip rung has been dead since the repos split: it read ../wake_alarm/wake_state.json (no longer a path) for a skip_workout field nothing ever wrote, and answered "no skip" for a year without an error. It now reads ~/.local/state/wake_alarm/morning_session.json, written HMAC-signed by wake-alarm every two minutes through the morning, and the whole decision is: signature ok, dated today, now < exempt_until. A completed-in-time morning defers the lock to 11:00; a live one until min(start + 90 min, 09:30); nothing else changes the ladder. The enforce path waits up to 30 s for a freshly booted PC's refresher; status paths never wait. Takes Flutter 3.47.5. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Tp54ewdXRLaimUuT8LgYyn	2026-09-19 16:41:17 +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	16ada6e5a2	Tell "could not check" apart from "no workout", and stop double-granting bonuses ... A real 1h57m workout on 2026-08-24 synced to Firebase and the locker still locked the screen. The trigger was auth: screen_locker was the only app with no cached firebase_auth.json, so it fell back to a stale shared password and got HTTP 400 every run. The defect was what it did next — an unreadable primary source was reported as "no workout" rather than "could not check", which is the same conflation that took 2026-06-12. Recover the session by borrowing a live refresh token from a sibling app, track degraded sources as state instead of a log line, and say so on the lock screen: name the backend, the error, and how stale the data is, so a sync fault reads as a sync fault. Also fix two bugs found while finishing the recovery: restore_and_bonus.py banked `existing + bonus` with no idempotence guard while finish_2026_08_24.sh advertised "safe to re-run" — a second run silently granted the compensation hours again. Guard on a durable `shutdown_bonus_granted_for` list; the bonus map alone cannot answer the question, since a week's total mixes earned streak hours with corrections. _extra_benefits._save_state rebuilt state from four hardcoded keys, so the next weekly rollover would have dropped that guard and re-armed the double-grant. Merge onto loaded state instead. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EJmPLyT8NU4DzDJPV1KEX5	2026-08-24 13:07:20 +02:00