59 Commits

Author	SHA1	Message	Date
Krzysztof kuhy Rudnicki	31a2056d52	deps: earned_time 0.13.2 (unified ladder from 2026-10-18) ... Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>	2026-10-17 18:21:36 +02:00
Krzysztof kuhy Rudnicki	f2ddf3a491	sick day: shutdown = 20:00 + gaming pay of today's credits (earned_time 0.13.1); credits raise to it, no absorb ... Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>	2026-10-17 17:38:24 +02:00
Krzysztof kuhy Rudnicki	9e23ebae4f	deps: earned_time 0.12.0 (shutdown rungs equal gaming pay from 2026-10-18) ... Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>	2026-10-17 16:56:44 +02:00
Krzysztof kuhy Rudnicki	8450644a56	Lock screen: "choose lockers…" opens sickdays' KeepPanel in the lock ... Next to the one-tap "I'm sick" (unchanged: keeps nothing, unlocks), a small secondary link lays sickdays 0.3.0's embeddable KeepPanel over every surface, in-process so it gets input under the lock's grab. Closing the overlay reveals the untouched screen underneath, so no countdown or phone check is restarted or skipped. After the panel's own write + sync: sick with the workout lock standing down -> sick floor, decision, close (shared with the one-tap path, no second mark or push); sick with the workout kept -> sick floor and a note, lock stays; cleared / unchanged / cancel -> the panel just closes. Tests stub KeepPanel and redirect resolve_paths and sync_quietly in every sickdays.* module, sickdays.gui._panel included. The fit check measures the panel on a throwaway pool. Pins bumped to sickdays-v0.3.0. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PAhbNszs5JKdtnD4uBi3xp	2026-10-17 14:06:22 +02:00
Krzysztof kuhy Rudnicki	1a305c0627	Sick days: per-locker keep (sickdays 0.2.0) for the workout lock ... The workout lock, its explanation, the status view and the workday penalty's penalised day now ask _sick.stands_down_workout: a sick day that keeps the workout locker behaves as a normal day. The penalty's ring day is judged by the alarm switch. Shutdown (20:00 floor, grace floor, base, target, preview scripts) keeps is_sick: the floor belongs to the day, not to a locker. The one-tap button still keeps nothing. Test pool fixture and preview harness now redirect every sickdays resolve_paths binding, so keep edits never reach the real pool. Pins bumped to sickdays-v0.2.0. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PAhbNszs5JKdtnD4uBi3xp	2026-10-16 15:18:49 +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	3c1b983c2a	deps: earned-time 0.10.0 (tutor quota per weekday: Tue-Thu 15, Mon/Fri 30, Sat/Sun 50 min) ... Claude-Session: https://claude.ai/code/session_01E57caQF4KXwEvqEnKtJiHM Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>	2026-10-12 21:17:14 +02:00
Krzysztof kuhy Rudnicki	96ad163ee6	earned_time 0.9.0: tutor earner renamed automation -> tutor ... Pins bumped at all four sites; tests follow TUTOR / tutor_bonus_units. pylint 4.1.3 (freshness gate). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01YADHKXzZhhePzQ2rNoXFcK	2026-10-12 16:38:25 +02:00
Krzysztof kuhy Rudnicki	5eb18b92ca	deps: earned_time 0.8.0 (tutor credit per active minute); tutor rung tests for minute rows and legacy blocks ... Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>	2026-10-10 18:32:43 +02:00
Krzysztof kuhy Rudnicki	41ce020e10	deps: earned_time 0.7.0 (tutor confirmed, 15 min shutdown per block) ... Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>	2026-10-10 15:02:56 +02:00
Krzysztof kuhy Rudnicki	2140ca5180	deps: earned_time 0.6.1 (tutor cutover; new-gate rungs spare the floor) ... Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>	2026-10-10 08:24:48 +02:00
Krzysztof kuhy Rudnicki	3a2ad0245c	deps: ruff 0.17.0 (CPY001 ignored: no copyright policy) ... Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>	2026-10-09 22:05:02 +02:00
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	19ccad6978	deps: freedays 0.3.1 (pins crdt-sync 0.9.2); pre-commit hook pins back in step ... freedays 0.3.0 pinned crdt-sync v0.9.1 exactly, which a clean venv could not resolve next to screen-locker's own crdt-sync 0.9.2. The pylint hook environments had also drifted from pyproject.toml (crdt-sync 0.9.1, earned-time 0.3.0). Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018RHwVPyiiQMPh4M3JQwQku	2026-10-09 20:56:32 +02:00
Krzysztof kuhy Rudnicki	965b9c4ebb	Sync: Firebase only — drop the GitHub transport (kuhyx/syncs stays a frozen archive) ... The PC push aborted before it ever tried Firebase whenever the GitHub PAT was missing ("Workouts NOT synced: no sync token"), so once the PAT was lost this machine published nothing although Firebase was configured and live. The phone has not written the GitHub repo since 2026-08-21. - sync_client() / sync_client_or_reason(): firebase_client_for("screen_locker") only, proven with can_access_remote(), healed once from a sibling app's session, else a warning naming what will not sync (push AND pull) plus a recorded degraded source. No config -> warning, no fallback. - _manual_push and scripts/tombstone_sync_record.py take their client from sync_client_or_reason(); the push result carries the reason. - Deleted: read_sync_token, remote_client, the mirror client, _push_outcome (the half-landed-push case no longer exists), SYNC_TOKEN_FILE and SYNC_REPO_OWNER/NAME, the sync_token test fixture. Status backend is "firebase" or "none". - crdt-sync pinned to v0.9.2 in pyproject, requirements.txt and install_systemd.sh (the installer still said v0.9.0). kuhyx/syncs/screen-locker-sync is left untouched as an archive; no code reads it. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018RHwVPyiiQMPh4M3JQwQku	2026-10-09 19:18:56 +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	ec7f4805f7	pin earned-time-v0.3.0 (registers the automation earner) ... Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-10-05 15:20:10 +02:00
Krzysztof kuhy Rudnicki	2dd719e6a4	earned-time-v0.2.0 (anki); shutdown projection prices each day on its own date ... Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-10-05 14:18:42 +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	6f3f93ecec	deps: mcp 2.3.0, pylint 4.1.2, url_launcher 6.3.3, @types/node, eslint ... Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-10-04 18:13:01 +02:00
Krzysztof kuhy Rudnicki	0b0cda6782	Morning-session reader moves to gatelock 0.9.0 ... _morning_session.py is now a thin binding of screen-locker's path and retry budget over gatelock.morning_session, shared with leetcode-guard and book-guard; the verdict tests live there once. Same behaviour, same string. Also bumps mypy 2.4.0 / pylint 4.1.1 / ruff 0.16.10 (newest stable gate) and the stale gatelock pins in install_systemd.sh and the pylint hook. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FBbkN4ZB4aUPJPzR2prRan	2026-10-02 14:05:40 +02:00
Krzysztof kuhy Rudnicki	deb89b3e03	Relaxed days from freedays.WORKDAYS; delete the dead rtcwake mixin and its stale ALARM_DAYS ... Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-09-27 20:24:01 +02:00
Krzysztof kuhy Rudnicki	a918c169df	Take the freshness gate's bump: gatelock 0.8.2 ... Pin only — 0.8.2 (wait_for_x_server waits as long as it takes) was already the installed version the suite ran against; CI's dependency-freshness gate flagged the 0.8.1 pin on 82f3462. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01C7vgacLhb4WJjxuVj2QLEP	2026-09-13 20:06:40 +02:00
Krzysztof kuhy Rudnicki	9b39196671	Take gatelock 0.8.1: nested LockConfig ... The grab axes are grab=GrabPolicy(kind=..., disable_vt=..., preempt_weaker_holder=...) and every colour read goes through config.palette; nothing about the lock's behaviour changed. Also carries the pylint hook on 4.0.8 with the source-only scope config; the gate stays at 8.0 until the remaining findings are cleared. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HHCbkJWXHjtTUaqvnHRAqA	2026-09-12 19:52:38 +02:00
Krzysztof kuhy Rudnicki	fc9720fafe	Take the freshness gate's ten bumps: Flutter 3.47.4, mcp 2.2.0, React 19.3, node 24.21 ... Web lint, tests and build pass on the new pins; the Python suite is unaffected (mcp is the optional MCP-server extra). Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HHCbkJWXHjtTUaqvnHRAqA	2026-09-12 19:52:30 +02:00
Krzysztof kuhy Rudnicki	f716b9529f	Pin freedays v0.2.0 ... v0.2.0 drops freedays's gatelock dependency (importing gatelock pulled in tkinter, so the headless pool needed a GUI toolkit) and adds the sync timer that makes a day marked on the phone actually reach this machine. Mechanical, but not optional: the freshness gate compares the pinned tag against the newest release, so leaving v0.1.0 here would turn this repo red on its next commit. Suite re-run against v0.2.0 before pinning it. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-09-07 15:58:57 +02:00
Krzysztof kuhy Rudnicki	d6e8c0973f	Replace scheduled skips with the shared free-day pool ... Fifth and last app onto freedays (~/utils/freedays). screen-locker is the one that already had this idea: scheduled_skips.json was a bare list of dates, checked first in the lock chain, that only this app could see. That is exactly what the shared pool generalises, so the chain now asks freedays and a day taken here also stands down diet-guard, wake-alarm, leetcode-guard and home-guard. Sick days are deliberately untouched. Their rolling windows (1/7d, 3/30d, 10/90d), the 120-character justification and the escalating countdown all exist to make a sick day *hard* to take. Free days are the opposite -- declared ahead, no reason, consecutive runs allowed. Merging the two policies would have had to ruin one of them, so only the storage of the frictionless half moved. This fixes a real bug in passing. is_scheduled_skip_today compared against a UTC day while add_scheduled_skip.py wrote a local one, so a skip added near midnight could name a date the chain never matched. freedays owns "what is today" for both sides now, in local time, and the disagreement cannot recur. scripts/migrate_scheduled_skips.py moves the existing dates across; it is idempotent and has a --dry-run. Already run here: the 8 real skips (2026-05-19/20/21, 05-29, 05-30, 08-17, 08-22, 08-29) are in the pool and count against 2026, leaving 27 of 35. The original file is gitignored and was left on disk untouched. add_scheduled_skip.py becomes a thin wrapper over freedays rather than being deleted, because arm.sh calls it and the name is in muscle memory. Left as-is it would have kept writing to a file nothing reads. conftest.py went over the 250-line cap, so the two fixtures that keep the suite off real user state moved to _real_state_fixtures.py. They belong together and neither subsumes the other: _isolate_home covers paths resolved from Path.home() at call time, while the freedays redirect covers paths bound into module constants at import time, which redirecting home afterwards cannot reach. requirements.txt also takes pytest-randomly 5.0.0, ruff 0.16.6 and types-requests 2.33.0.20260906, and the pylint hooks' gatelock/crdt-sync pins move off v0.7.1/v0.9.0 -- pip refuses two direct URLs for one distribution, so those stale pins would have made the hook environments unresolvable rather than merely old. 1256 tests, 100% branch coverage. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-09-07 15:42:41 +02:00
Krzysztof kuhy Rudnicki	1d5965b9a7	Close the four gaps that let a decided lock never reach the screen ... Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-30 15:24:45 +02:00
Krzysztof kuhy Rudnicki	8f911585c1	Serve the lock decision, its history and its health at 127.0.0.1:8770 ... The only status surface was a GTK tray icon, commented out of ~/.config/i3 on 2026-08-21. So when the weekly count went wrong, nothing on the machine said so for two weeks -- the same silence that let a deleted timer job stop enforcement for thirteen days in August. Three read-only endpoints, and a React 19 UI over them: /api/status the decision, the week, and whether today has a workout /api/decisions the recorded trail, newest first /api/health timers armed, disarm marker, log and trail freshness The Why view is the one that matters: it renders the run of "weekly_minimum_met 5/5" ticks that hid this week's bug, without anyone having to reach for journalctl. /api/status also carries gaming.workout_today, which is the fact steam-backlog-enforcer will cut the daily budget on. Deliberately just the fact -- the enforcer owns the hour values, so the two repos cannot come to disagree about what a workout day is. It is derived from count_day_credits, the same rule the locker enforces with. _compliance_state_word moves from status_view (tkinter) into _status_projection, and the systemd arming check moves from scripts/check_enforcement_armed.py into screen_locker/_armed_state.py, so the server can answer "is enforcement armed" without a second copy of the logic that would be free to disagree with the gate. web/ mirrors steam-backlog-enforcer/web but tightens it: that config has no "strict" in any tsconfig, extends only tseslint recommended (no type-aware rules at all), and gates neither lint nor typecheck in pre-commit. Here all three run, on strictTypeChecked + stylisticTypeChecked, with noUncheckedIndexedAccess and exactOptionalPropertyTypes. 44 tests, 100% of statements, branches, functions and lines. typescript stays pinned at 6.0.3: 7.0.2 is out, but every published typescript-eslint -- stable, canary and rc-v8 -- declares typescript ">=4.8.4 <6.1.0". The fleet allowlist already carries that entry. The 250-line cap now covers ts/tsx. It was python/shell/dart only, which would have made web/ exempt from the gate the rest of the repo lives under -- the same omission that exempted the whole Flutter app until 2026-08-15. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Fcwu78wk17FWMHbbfbyicc	2026-08-29 22:50:19 +02:00
Krzysztof kuhy Rudnicki	ec0946f64e	Grade against 3.14 too, not just run on it ... `requires-python` and the CI pin already said 3.14, but ruff, mypy and pylint were still grading against 3.10 -- three tools judging an interpreter nothing runs any more, and ruff withholding the pyupgrade fixes that only become safe at the newer target. `pin_ci_python.py` rewrites exactly these three knobs. What the stale target was hiding: 118 sites on `datetime.timezone.utc` instead of `datetime.UTC` (UP017), two classes still written with `Generic[...]` rather than PEP 695 syntax, and ruff's stable formatter applying PEP 758 -- `except (A, B):` becomes `except A, B:`. That last one makes the source 3.14-only at the syntax level, which is what `requires-python = ">=3.14"` already promised; kuhy chose it deliberately over holding ruff a release back (2026-08-29). The PEP 695 fix needed a hand: ruff rewrote `class WidgetGroup(Generic[_W])` to `class WidgetGroup[W: tk.Misc]` but left the body annotated with the module-level `_W`, a *different* type variable -- mypy caught it as "a function returning TypeVar should receive at least one argument containing the same TypeVar". Renamed the body to the new parameter, gave `FrameGroup.__init__` the concrete `list[tk.Frame]` it always wrapped, and deleted the two now-dead module-level TypeVars. ruff, ruff-format, mypy --strict and both pylint passes clean at the new target. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SfnJmxxsZ534AKk16rC2Gr	2026-08-29 11:42:47 +02:00
Krzysztof kuhy Rudnicki	b9c2bf796e	Run CI on exactly one Python, the newest ... Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-28 19:20:48 +02:00
Krzysztof kuhy Rudnicki	d67c770cc9	Latest stable dependencies, and the gate that keeps them there ... Python side: gatelock v0.7.1 -> v0.7.2 and crdt-sync v0.9.0 -> v0.9.1 (both re-cut so consumers stop resolving pre-upgrade constraints), plus every `>=` floor turned into an exact pin -- five majors among them (mypy 1 -> 2.3.1, pylint 3 -> 4.0.7, pytest 8 -> 9.1.1, pytest-cov 4 -> 7.1.0, ruff 0.8 -> 0.16.5) and mcp pinned at 2.1.1. `scripts/ci_mirror.sh` builds a clean venv from requirements.txt and runs the whole CI set: 1146 tests, 100% branch coverage, no lint or type finding. workout_app: sync_settings_ui v0.1.0 -> v0.4.1 and ten exact pins, with the flutter_secure_storage 11 chain (compileSdk 37 / AGP 9.3.2 / Gradle 9.7.1). 411 tests green, analyzer clean, release APK builds. CI's Flutter pin was 3.44.6 while `.fvmrc` says 3.47.2 -- the drift that made kuhylog red on a commit that is clean locally. Both workflows now say 3.47.2, and the gate reads that pin from now on. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CRykabMwPgDzFHcARoqpaK	2026-08-28 15:13:11 +02:00
Krzysztof kuhy Rudnicki	a8b34befb5	Lend the lock screen's grab to the workout app, without unlocking it ... The locker cannot close() to let the app take over: close() also restores VT switching, which would hand the user Ctrl+Alt+F2 and an exit from the very obligation the lock exists to enforce. Only the grab moves; the Tk window stays mapped underneath, so the screen is still covered if the app dies. The watchdog has to be stopped for the duration, and measuring it is what makes that non-negotiable. gatelock's recovery loop re-takes any grab it finds missing every 1000ms -- by design, so that pulling a cable is not an escape -- and holds_grab() is `grab_current() is not None`, which is False once another X client holds it. Verified on a private Xvfb display: a naked release is stolen back within ~1.5s, while stopping the loop first lets the app keep the screen and the locker take it back cleanly afterwards. The same harness confirms the ordering the handshake depends on: while the locker holds the global grab a second X client cannot even finish connecting (4s, no output at all), so there is no window in which the screen is uncovered. It only gets through after the release. Reaching into lock._recovery earns an SLF001 waiver rather than a public pause on LockWindow: gatelock's _recovery.py carries a monotonicity proof that no transition ever decreases the grab, and a public lend_grab() would be exactly that transition. The waiver is documented where the other four SLF001 waivers in this repo already live. start_workout blocks the Tk loop for the whole workout, which is deliberate -- pumping Tk underneath is what would let a tick steal the screen mid-set. The docstring names the cost: a monitor hotplug is not handled until the app exits and grab_input() re-covers every live output. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DfJC1Wu1SEgJ6X49k5Jqtg	2026-08-22 12:08:40 +02:00
Krzysztof kuhy Rudnicki	2c206e5070	Adopt crdt-sync v0.9.0's bundled sync_log signature ... sync_log's eleven flat keywords became SyncTarget / LogCodec / RevisionTracking upstream. Call sites and test doubles follow; the hook's own pinned crdt-sync moves to v0.9.0 too, so the gate checks against the API the code actually imports rather than an older tag. No behaviour change. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VCucBhUkHBBHHbsY7bSdGV	2026-08-21 14:28:14 +02:00
Krzysztof kuhy Rudnicki	6a7a7d8933	Queue behind stronger lockers, single-instance guard, fix budget-crash in fit check ... Root-caused the 2026-08-21 stuck-lock incident: a manual workout unlocked correctly, but the mechanism behind "locked again seconds later" was a stray workout-locker.service re-arm racing a second process into building a competing lock window -- not a leetcode-guard conflict as first suspected (its timer wasn't due until 13:00 that day). Separately, diet_guard held the global grab for ~3 minutes against a newly-arriving, higher-ranked screen_locker that morning, which just retried and logged instead of making progress. - _build_lock_window now calls gatelock.wait_for_turn before arming, so a stronger incumbent is queued behind instead of raced. - New screen_locker/_instance.py (flock-based, mirrors leetcode_guard/diet_guard's own single-instance guards) stops a second process from ever building a competing window in the first place. - Bumped to gatelock v0.7.1, which adds weaker-holder preemption (SIGTERM, reusing the holder's own clean close() path) so a lower- ranked incumbent can no longer block a stronger claim for minutes. - Fixed a live crash in scripts/verify_screen_fits.py: it read the real log.json, so today's exhausted manual-workout budget (itself caused by the incident's duplicate entry) made the fit-check crash on an unset _mw_error_label. Points at a path that can never exist instead, so the measurement no longer depends on live data. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018M5gKyYzxWG6QkCaj1wWfk	2026-08-21 13:04:54 +02:00
Krzysztof kuhy Rudnicki	8bc981da4e	Split _runnerup_verification, _ui_widgets and _sick_dialog ... _runnerup_verification.py (312) -> _runnerup_tcx.py pull + parse TCX _runnerup_backfill.py fill the log for a date or a week _ui_widgets.py (287) -> _ui_form_fields.py labelled fields, focus, disable_paste _sick_dialog.py (278) -> _sick_commitment.py next-day commitment _ui_form_fields also takes disable_paste, since the fields are what use it; _ui_widgets re-exports it for _manual_workout_widgets and _sick_dialog. Two things had to move with the code rather than being left behind: - conftest's _TK_MODULES gains _ui_form_fields, or its tkinter calls reach a real display instead of the mock. - pyproject's S314 waiver follows the ET.parse call it covers into _runnerup_tcx.py. Same approved suppression, new home -- not a new one. Test count 977 -> 978: _ui_form_fields is a new lock-surface module, so test_no_popup_widgets safety-checks it too. 100% branch coverage held; pylint back at 8.70 after fixing a genuinely undefined WidgetGroup annotation the split exposed. `screen_lock --status` unchanged. Gate: 41 -> 28 files. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EveB813BQ8abAP68VSqZ5Y	2026-08-15 20:37:15 +02:00
Krzysztof kuhy Rudnicki	e7fa7fb44c	Let the PC see phone workouts again, and stop losing progression on reinstall ... A real StrongLifts session on 2026-08-10 never reached this machine, so it had to be logged as a manual workout -- spending a manual budget slot on a workout that was genuinely verified. The session was in Firebase the whole time; four separate defects each hid it. - pull_synced_workout() read a hardcoded devices/phone/log.json. Since ffc6c72 the phone pushes under a per-install uuid, so that directory has been frozen since 2026-07-17 and the PC kept returning a stale session from 07-27 as if it were current. Both readers now walk EVERY device directory; reinstalls keep minting new ones, so no single path can be right for long. - A session is identified by SHAPE (it has `exercises`), not by a `kind` field the phone never writes. That filter is why the one reader that did walk every directory discarded real sessions, and it also kept PC-origin runnerup/phone_verified records from being handed to a caller expecting a session. - FirebaseSyncError is a SIBLING of GitHubSyncError, not a subclass, so `except GitHubSyncError` never caught it and a DNS failure took the whole locker down (status=1/FAILURE, then a restart loop). Catch the common parent; a pull failure degrades to a warning. - A GitHub token is no longer required to sync. Firebase has been primary since eb4ff01, so a Firebase-only machine was reporting "sync is OFF" while syncing fine. Sync also only ran once per locker start, so a workout finished after login was invisible until the next login. workout-sync.timer runs the new headless --sync-only every 15 minutes; remove_systemd.sh now removes every unit the installer creates, not just two of them. workout_app: the 2026-08-05 reinstall wiped progression because the DB seeds factory defaults before the backup is restored, and the first write then exported those defaults over the only off-device copy. Storage permission is now settled before the DB opens, a defaults-only DB refuses to overwrite a richer backup, and the three swallowed storage errors say what broke. Sessions that exist only in Firebase/GitHub are restored into local history, so a reinstalled app has the history it actually earned rather than starting at whatever survived. Matched on (date, start_time), so re-syncing never duplicates and local rows always win. Adds a target-reps editor: progression can only ever RAISE reps, so a rep target a defaults re-seed set wrong could not be corrected from the UI at all. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01JS5V44jkHZiH1wC7BH5h5n	2026-08-10 14:39:02 +02:00
Krzysztof kuhy Rudnicki	ffc6c72df0	Push under a persisted per-install uuid, not a fixed role id ... screen_locker pushed manual workouts as "pc" and the workout app as "phone". A role constant collides the moment a second machine takes the same role, and after a reinstall the new install inherits the previous one's CRDT identity. Both halves now mint a uuid once and persist it: the PC in ~/.local/share/screen_locker/.device_id, the app under SharedPreferences 'crdt.nodeId' -- the same key every sibling app uses. The old constant survives as the legacy id and is passed to sync_log / syncLog, so devices/<legacy>/ is skipped as this device's own rather than re-downloaded and re-merged as a peer's on every tick. It drops to None once that path is reclaimed. Note the *read* loop in _workout_sync deliberately still merges every device including this one: the PC needs its own manual workouts in the merged view, so "skip own" would be wrong there. Only the push path and the HLC node id move. The test fixture redirecting the new id file is added in the same change that introduces the constant -- without it the first test that syncs mints a uuid into the real state dir and this machine's live sync identity is decided by whichever test ran first. Verified: ~/.local/share/screen_locker/ held no .device_id after a full suite run. Verified against the live backend, not just mocks: ran the real push_pc_workouts, which minted 57582b3b and pushed 9 records. In the RTDB the new device's log is a strict superset of both old paths -- 0 of devices/pc/'s 10 records and 0 of devices/phone/'s 9 are missing from it. Python: 907 tests, 100% branch coverage. workout_app: 313 tests, analyzer clean. Pins bumped to crdt-sync-v0.6.0 / crdt_sync_dart-v0.7.0. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GZH89WEqAjuJT8WZdqc7AP	2026-08-09 17:31:15 +02:00
Krzysztof kuhy Rudnicki	eb4ff01e04	Sync workouts through Firebase, mirroring to GitHub during the cutover ... Both surfaces of this repo move together, because they share one prefix: screen_locker (the PC, which reads what the phone logged) and workout_app (the phone, which writes). Firebase becomes the primary backend when it is set up, with GitHub kept as a mirror so a device that has not moved yet is still seen. MirrorSyncClient reads the union of both, so a workout logged against either backend still counts -- which is what lets the PC and the phone cut over on different days. The PC's two pulls are read-only, so they need only the client swapped. _manual_push does a real sync_log and now carries a revision cache, as does every push in workout_app: without it each push re-uploads the whole log and each pull re-downloads every peer's, regardless of change. remote_client is public rather than _private because _manual_push imports it; one decision point beats two copies that can drift. The config file is checked before constructing anything, so an unconfigured machine never reaches the network -- without that guard the PC's sync tests asserted against live Firebase data instead of their own fakes, which is how this was caught. screen_locker: 904 tests at 100% branch coverage. workout_app: 299 tests at 100% line coverage; pinned v0.1.0 -> v0.6.0 across three minor versions with no API drift. Four assertions moved off `.single`, which now finds two writes: the log, then the revision published after it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SJ9sxEw3ymzXNjL7SHNpJc	2026-08-05 08:12:40 +02:00
Krzysztof Rudnicki	7e04cf784b	Move the crdt-sync pin to v0.3.0 ... Your in-progress bump, committed as its own change so it is not buried in anything of mine. All three declaration sites move together -- the manifest, the lockfile-equivalent and pylint's hook env -- because a pin that lags the others lints the code against a library it does not actually run with. Verified in a clean venv that v0.3.0 still provides every symbol this repo imports: GitHubSyncClient, GitHubSyncError, Hlc, Record and Log. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BsXnTHyuuCUZsqetTaajcF	2026-08-03 19:54:40 +02:00
Krzysztof Rudnicki	a0a3fb0eb0	Port the MCP server to mcp 2.x, and say what each tool is allowed to do ... mcp 2.0.0 removed mcp.server.fastmcp; MCPServer is the same object under a new name, so @mcp.tool() and mcp.run() are untouched and every tool keeps its name, signature and returned shape. Verified against a clean 2.0.0 venv: all four tools list, and the whole suite -- including test_mcp.py, which could not even import while the dependency was broken -- passes at 100% coverage, 901 tests. Two things the port buys, neither of which existed in 1.x: * Tool annotations. The section banner here already said "state-only; never expose secrets, never mutate"; now the protocol says it too, as read-only, idempotent and closed-world hints, which is what lets a client run these without asking first. The day one of them starts writing, the annotation is what has to change with it. * Structured output. 2.x derives an output schema from the return types and sends structured content alongside the text, so a caller no longer re-parses JSON we already had. No code change -- it falls out of the type hints that were already there. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BsXnTHyuuCUZsqetTaajcF	2026-08-03 19:48:07 +02:00
Krzysztof Rudnicki	feb7c173d5	Pin mcp below 2.0, and keep the crdt-sync bump out of my commit ... CI has been red in three of these repos since 2026-07-30, for a reason that has nothing to do with any commit made here: mcp 2.0.0 removed mcp.server.fastmcp, which _mcp.py imports at module scope, and the manifests asked for `mcp>=1.9` with no upper bound. Verified directly -- 2.0.0 raises ModuleNotFoundError on that import, 1.29.0 provides it. Pinned `<2` in all three places the dependency is declared (requirements, the optional extra, and pylint's hook env) until the server is ported to the 2.x API. Also backs the crdt-sync 0.1.0 -> 0.3.0 line out of pyproject.toml: that is an in-progress change of yours that rode into dd233b2 when I staged the file for its pylint init-hook. It is untouched in the working tree, where the matching lines in requirements.txt and .pre-commit-config.yaml still carry it, so the three move together whenever you commit them. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BsXnTHyuuCUZsqetTaajcF	2026-08-03 17:42:01 +02:00
Krzysztof Rudnicki	dd233b27aa	Run the fit check as a module, so it works where nothing is installed ... CI caught what this machine could not: the hook died with "No module named 'screen_locker'". The package is pip-installed here (editable, pointing at this checkout), so running the script by path found it anyway; a fresh checkout has no install, and `python3 scripts/x.py` puts only `scripts/` on sys.path. `python3 -m scripts.verify_screen_fits` puts the repo root there instead, which is the checkout in CI and here alike -- verified in a throwaway worktree, where the module now resolves to the worktree's own package rather than the installed one. The xvfb re-exec runs the same way, with an explicit cwd so the child does not depend on where the parent was invoked from. pylint had the same blind spot for the same reason: it infers sys.path from the files it is handed, so this script resolved its imports only when a package file happened to be in the same batch -- passing or failing by what else was staged. An init-hook puts the repo root on the path unconditionally. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BsXnTHyuuCUZsqetTaajcF	2026-08-03 16:34:45 +02:00
Krzysztof Rudnicki	a79c4fdd05	Stop the lock screen scrolling itself, and make every screen fit 768px ... This morning the lock screen scrolled to the bottom and back with nobody touching the keyboard, on the 1366x768 panel. Reproduced under Xvfb with the real app: one programmatic focus_set() produced three scrolls, frac 0.000 -> 0.436 -> 0.145. The cause is in gatelock (fixed in v0.4.0, pinned here): the viewport followed every <FocusIn>, and this app focuses a widget on every repaint. It now follows only focus the *user* moved, and a screen that fits cannot scroll at all. The other half is this app's own layout, because scrolling was covering for screens that did not fit. The manual-workout form needed 1643px of a 768px screen -- SUBMIT and BACK were simply off the bottom: * Every font size and pad now goes through the design-system tokens rather than a literal. A positive size means *points* to Tk, so "36" rendered ~37% larger than the 36px intended; that alone was most of the overflow, on all 88 call sites. * The form's cells put their label beside the field instead of above it, and the three reflection boxes share rows instead of taking one each. Result, measured by the new scripts/verify_screen_fits.py (a pre-commit hook now, so this cannot come back quietly): the form is 752px of 768px, and every other screen -- including heat-skip, which had no viewport at all -- fits with room to spare. Also fixed, all found by measuring rather than by reading: content that fits is centred again (the reset-to-top was cancelling it on every repaint), the scrollbar only appears when there is something to scroll, and unlock_screen moved to _unlock_view so screen_lock.py stays under the 400-line cap. Tests: 896 pass. The focus/scroll helpers shipped in 3e77f4e had no coverage at all; test_focus_and_scroll.py covers them now. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BsXnTHyuuCUZsqetTaajcF	2026-08-03 15:57:48 +02:00
Krzysztof Rudnicki	3e77f4e232	Make every lock screen keyboard-operable, and add the missing installer ... The locker was not running at all. workout-locker.service crash-looped ~1977 times in a single boot with ModuleNotFoundError while remaining `enabled`, and has no successful start in the retained journal. A locker that cannot start is a locker that does not lock. Root cause: commit 9b420a9 removed the unit's WorkingDirectory and PYTHONPATH=/opt/screen-locker on the (correct in principle) grounds that "screen_locker is now pip-installed" -- but nothing guaranteed that install. There was no installer, /opt/screen-locker no longer exists, and the package was absent from every Python version's user site-packages. The unit lost its fallback and gained a hard dependency on a manual step nobody re-ran. install.sh fixes that as a script rather than a reminder, and *gates*: it fails if the production interpreter cannot import screen_locker, because an installer that reports success while the service still cannot start is precisely the failure above. It also re-asserts an editable gatelock from ~/utils AFTER the package install and verifies it resolves there -- pyproject pins gatelock to a git tag, so a plain install silently replaces a local editable gatelock with a frozen wheel, which was observed removing ScrollableSurface and taking diet_guard down with it. The keyboard work, all of it Tk defaults rather than local mistakes: - Focus was invisible. Tk ships highlightcolor="#000000" -- a black ring on #211D1B -- and relief="flat" removes the depth cue too, so a keyboard user had no indication of where they were. Now set in the _ui_widgets factory, so a new call site cannot omit it. - Enter did nothing. X11 Tk binds <space> on Button and never <Return>. - tk.Text trapped Tab (inserts a literal tab, refocuses itself) and no-opped Shift-Tab; the only exits are the undocumented Ctrl+Tab / Ctrl+Shift+Tab. - The lock and retry screens started with NOTHING focused. on_focus_ready was a documented no-op arguing "buttons only, nothing to focus" -- exactly backwards: buttons are what needs focusing when there is no other window on screen and a global grab is held. - The heat-skip modal grabbed input fullscreen with no focus, no ring, no Return and no Escape. It now focuses the *declining* option, so a blind Return keeps the workout rather than silently skipping it. The manual-workout form's scroll viewport was pointer-only in three ways at once: tk.Canvas has no class key bindings, so ::tk::FocusOK rejected it as a focus stop; nothing bound wheel, PageUp/PageDown or arrows, leaving only a draggable thumb; and canvas clipping does not unmap children, so below-the-fold fields stayed in the tab ring while Tk never scrolled to follow focus -- Tab led to fields the user could neither see nor reveal. Its height was also a magic 0.7*toplevel above ~230-290px of fixed chrome, i.e. satisfied at 1080p and violated at 768p, where SUBMIT/BACK were pushed off the bottom. All of that is gone by deletion: the surface container is now a gatelock.ScrollableSurface, so the inner viewport is redundant. build_surface and _ensure_container both use it, which fixes the same symmetric-clipping problem for EVERY screen rather than one at a time; center_when_fits keeps short screens looking exactly as they did. Re-arming after a repaint hooks into clear_container(), which all ~19 repaint sites already call. "Remember to call settle after painting" is a rule that would eventually be missed, and on a lock a missed re-arm means unreachable content. The aux windows hardcoded geometry("600x400") and ("700x450") while displaying more than that -- the relaxed-day prompt's own button row requests 862px inside a 700px window, sheared at both edges. That pre-dates this work by a wide margin (Tk's default focus ring accounts for 4px of the 162px overflow). They now size to content, floored at the old values and clamped to the display. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-07-30 16:25:45 +02:00
Krzysztof kuhy Rudnicki	c11e27f123	Pin gatelock 0.2.1, and stop the popup check passing when it cannot run ... The lock-popup-safety job failed on its first CI run for two reasons, and only one of them was the obvious one. The obvious one: the script imports screen_locker directly rather than through pytest, which would have put the rootdir on sys.path for it. CI now installs the package. The one worth having found: CI installs gatelock from the pinned tag, which predated `holds_grab`, so every hostile tick died on an AttributeError -- inside a Tk `after` callback, where exceptions are swallowed and logged rather than raised. The harness sailed past, printed OK and exited 0 while doing no grab re-assertion whatsoever. A verification script that passes when it is broken is worse than not having it. So it now fails closed twice over: an explicit check that the installed gatelock has the predicate at all, with a message naming the fix, and a count of ticks that actually completed -- incremented after the work, so a raising tick does not count. Fewer completed ticks than asked for is reported as "the harness itself is broken, so this result proves nothing", not as a pass. The pin moves to gatelock-v0.2.1, which carries both of yesterday's fixes: the grab predicate that no longer steals the grab off our own posted menus, and the recovery loop that no longer stops forever when a tick raises. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-07-26 15:18:04 +02:00
Krzysztof kuhy Rudnicki	600d0fd084	Migrate screen_locker to gatelock v0.2.0 per-output locking ... The lock now paints one container per live output instead of one window on the primary, and claims the screen through an Arbiter at RANK_SCREEN_LOCKER so the wake alarm can outrank it. The fan-out happens at the widget factory, not the render loop. Painting a screen here is not a pure function -- the ~20 clear_container() flows record workouts, credit weeks and branch on state while they paint -- so re-running a flow per surface would double those side effects. Instead `_label`, `_button_row` and friends build N copies and return a group that mirrors later configure calls to all of them, and a flow body still runs once. Frame groups nest, so `_button(button_row, ...)` reads exactly as it did. The degenerate case carries as much weight as the general one: the status window, the post-sick-day verify window and the relaxed-day prompt have no lock and no surfaces, and share this same factory. They get a group of exactly one frame and behave as they always did. Text boxes are the one thing that cannot be shared. Entries fan out over a single StringVar, but tk.Text has no such variable, so the sick-day description genuinely diverges per monitor; TextGroup.get() returns whichever copy was actually typed into, preserving "answer on any monitor". Tests: the suite hung rather than failed on first run, which is the trap gatelock's own conftest documents -- screen_locker patches its own `tk`, but LockWindow builds Toplevels through gatelock's, and real tkinter over a MagicMock root recurses without bound. `_gatelock_fixtures` closes that and redirects the runtime dir so no test can stand a production locker down. Every other test runs single-output, where fan-out is unobservable, so test_surface_fanout runs on two outputs; each assertion was checked by cropping the group loops to the primary and confirming it goes red. 874 tests, 100% branch coverage, pre-commit clean, no lint suppressions.	2026-07-25 16:26:39 +02:00
Krzysztof kuhy Rudnicki	6629260256	Fix on-fill text contrast on filled buttons, bump gatelock pin ... _ui_widgets.py's _button() always set fg=self._colors.fg (near-white) regardless of bg, so any accent/success/warning/danger-filled button under-contrasted (measured 2.2-3.6:1 vs the 4.5:1 floor). Added _fg_for(bg) so fg is derived from bg instead of hardcoded -- fixes every current _button() call site structurally, not per-instance. Found and fixed 2 more standalone instances of the same bug outside the shared helper (_window_setup.py's demo-close button, _heat_skip.py's heat-skip button). Bumps gatelock to the released v0.1.1 carrying the same on_fill token plus the warm palette rework. Regenerated workout_app's launcher icon assets to match. Verified: gatelock 50/50 + screen_locker 859/859 tests, both 100% coverage; pre-commit (incl. pylint against the real v0.1.1 install) green.	2026-07-21 21:17:14 +02:00
Krzysztof kuhy Rudnicki	b0d9165a79	Retry sync past the boot/resume network race, and stop blaming the token ... The morning routine is started by systemd right after boot and right after resume, so its sync ran seconds before DHCP/DNS were up. Every such run failed outright — and said this: Workout sync push FAILED for 6 workout(s): network error reading screen-locker-sync/devices — a 403 here means the token lacks contents:write on kuhyx/syncs Both halves of that were wrong. It was not a 403, and the token was fine: the same six workouts pushed successfully by hand minutes later on the same token, which reports push=true on the repo. The message cost a real investigation chasing a permissions bug that did not exist. - _sync_retry.with_sync_retry wraps the three sync call sites in a bounded retry (4 attempts, 2s/4s/8s backoff — ~14s, enough for the network to come up, short enough not to drag the routine). Verified offline in a network namespace: three retries, then an honest give-up. - Any GitHubSyncError retries, deliberately including RepoNotFoundError. Classifying transient vs permanent would couple us to which exception crdt_sync chains where; a few wasted seconds on a genuinely bad token is the cheaper mistake. - The push failure log now reports what actually happened. The contents:write hint survives only for RepoNotFoundError, which is the one error that actually implicates the repo or the token. Retry at the application layer rather than ordering the unit after network-online.target: the same race hits on resume, where boot ordering does not apply, and these are user units that cannot depend on a system target. The tests' autouse no-sleep fixture patches the module-local `sleep` name rather than `_sync_retry.time.sleep` — the latter mutates the shared time module object and silently disabled sleep for the whole suite, breaking an unrelated temperature timeout test. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-07-20 08:46:37 +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