26 Commits

Author	SHA1	Message	Date
Krzysztof kuhy Rudnicki	814ad87301	deps: node 24.22.1, gradle 9.8.2, sqflite 2.4.5, sqflite_common_ffi 2.4.5, pnpm 12.15.0, typescript-eslint 8.72.0, vite 8.3.5 (newest stable) ... Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017k9j5dbjenpfZj7dh2faPN	2026-10-23 18:09:40 +02:00
Krzysztof kuhy Rudnicki	0b0a18e81c	deps: newest stable (freshness gate); migrate web/ npm -> pnpm ... web: react/react-dom 19.3.1, vitest + coverage-v8 5.0.4, jsdom 30.1.3, user-event 14.6.8, typescript-eslint 8.71.2. Lockfile is now web/pnpm-lock.yaml (packageManager pnpm@12.14.0); hooks and CI use pnpm with --frozen-lockfile. Node 24.22.0 in workflows; workout_app sqflite 2.4.4+2 / sqflite_common_ffi 2.4.4. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Xfj1sxKH9VBPqpcAni8Jry	2026-10-16 14:16:56 +02:00
Krzysztof kuhy Rudnicki	0b809c4af1	deps: Flutter 3.47.7 (fixes red freshness CI) ... Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-10-09 10:53:10 +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	c81f1bac3f	CI: 10 Flutter shards, under the 20-job concurrency limit ... Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-10-02 15:17:16 +02:00
Krzysztof kuhy Rudnicki	5d9b348436	CI: 12 Flutter test shards so Tests fits in a minute ... Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-10-02 15:14:48 +02:00
Krzysztof kuhy Rudnicki	429e854ddd	CI: slim Flutter SDK for gating jobs; APK only on app changes, Gradle cached ... Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-10-02 15:06:56 +02:00
Krzysztof kuhy Rudnicki	6f351179d7	Flutter 3.47.6 and web deps to newest stable ... Flutter 3.47.5 -> 3.47.6 (.fvmrc + CI); web: globals 17.13.0, typescript-eslint 8.71.0, vite 8.3.2, vitest + coverage-v8 5.0.3. Web lint, 100% coverage and build pass. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FBbkN4ZB4aUPJPzR2prRan	2026-10-02 14:19:46 +02:00
Krzysztof kuhy Rudnicki	7ae4c13407	CI under 60 s: uv, xdist, split pre-commit, sharded Flutter coverage ... Tests (~214 s, gated by flutter-coverage): - Flutter suite runs as 8 parallel buckets of whole test files (check_flutter_coverage.sh --shard I/N); flutter-coverage merges their lcov files (--merged N) and applies the unchanged 100% bar and every-lib-file-present guard. `flutter test --total-shards` splits test cases inside each file, so every shard would still compile all 77 files. Proved locally: the merged lcov matches an unsharded run line for line (3312/3312), and a missing shard fails. flutter-action caches the SDK. - pytest: uv install, -n auto -q -p no:sugar (local: 25.9 s -> 10.6 s, 100% coverage both ways). - lock-popup-safety: uv, and no apt step -- xvfb-run and setup-python's tkinter are already on the runner (screens-fit relies on both already). pre-commit (~122 s): matrix of mypy / pylint / flutter-analyze / rest, each installing only its own toolchain, with a per-group hook cache. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0188kZdx3bb56QM8JFUnbHuM	2026-09-26 19:36:32 +02:00
Krzysztof kuhy Rudnicki	a03afb8ae7	CI runs the Flutter and web coverage bars; they only ran on pre-push before ... Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-09-20 21:54:16 +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	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	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	d35097f461	Give CI the node packages its web hooks have always needed ... The pre-commit workflow has been red since 8f91158 added the status UI: it installs Python and Flutter deps but never node ones, so `tsc --build` could not find the 'vite/client' and 'node' type libraries and failed TS2688 on every run. Nothing was wrong with the code; the job simply could not build it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BJUtseRczWVBJW8LvL1aQH	2026-08-30 15:32:51 +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	e32b9c5c66	Refresh the gate workflow from the shared template ... Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-28 16:55:12 +02:00
Krzysztof kuhy Rudnicki	6b756c8da2	Give the pre-commit workflow the shared-gate checkout it needs ... Both delegating hooks were exiting 1 with "shared gate not found at /home/runner/utils/scripts/...". The workflow runs `pre-commit/action` against a bare checkout, so nothing put kuhyx/utils where the delegates look. It now checks the shared repo out to `.utils` and points `UTILS_ROOT` at it, the same way every other workflow in the fleet does. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CRykabMwPgDzFHcARoqpaK	2026-08-28 15:19:11 +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	a889341979	Adopt the four markdown namespaces and gate them ... Renames this repo's markdown onto README.md / CLAUDE*.md / DOCS*.md / TODO*.md so a future session can tell a live task from a finished record without reading the file to find out. TODO files carry the literal "REMOVE ME AFTER FINISH" and are deleted when the work lands. Enforced by the md-naming pre-commit hook and CI workflow, both delegating to the shared gate in kuhyx/utils so this repo's idea of a valid name cannot drift from every other repo's. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01A47aX5DJwmA3QFn3pkEWi7	2026-08-24 15:53:42 +02:00
Krzysztof kuhy Rudnicki	76a4c6a0a7	Finish the Python side: scripts, conftest, and the last test modules ... verify_lock_popup_safety.py (318) -> _xvfb_reexec.py shared re-exec _popup_form_check.py HostileLock, ticks, the real-form check verify_screen_fits.py (266) -> uses _xvfb_reexec too conftest.py (329) -> _tk_mocks.py the tk mock + the module patch list _opt_in_fixtures.py requestable fixtures three test modules -> _part4/_part5/_part15 siblings conftest keeps every autouse fixture. pytest applies autouse fixtures from conftest only, so one moved to a sibling would silently stop running and take its safety guard with it -- verified by asserting the fixtures are still listed, not just that the suite is green. The five near-identical _isolate_* fixtures collapse into one table-driven _isolate_state_files, which also picks up the _shutdown_sick_state binding an earlier split created. scripts/ becomes a real package so the shared helpers are importable. Both gates now run as `python3 -m scripts.<name>`, including CI -- the path form put scripts/ on sys.path instead of the repo root, and the alternative was a try/except ImportError that this repo's no-silent-failures hook rightly rejects. Each gate was run in its exact invocation form. Note: verify_lock_popup_safety still fails on `RecoveryLoop.__init__() takes 3 positional arguments but 6 were given`. That is pre-existing -- confirmed by running it at HEAD in a clean worktree before touching it -- a gatelock API drift, not this refactor. Left as found. 978 tests at 100% branch coverage. Gate: 41 -> 22 files, all remaining ones Dart plus DESIGN_AUDIT_TODO.md. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EveB813BQ8abAP68VSqZ5Y	2026-08-15 20:57:29 +02:00
Krzysztof kuhy Rudnicki	2d331f1467	Derive versionCode from the commit count, not github.run_number ... run_number counts workflow RUNS, not code. Two failure modes, one of which already bit: it resets to 1 if this file is renamed (the existing NOTE warned about that), and it can fall BEHIND a build produced outside this workflow. On 2026-08-09 diet-guard's phone held a manually sideloaded vc 8 while CI's next build was vc 6, so `adb install -r` refused every CI build with INSTALL_FAILED_VERSION_DOWNGRADE. The only non-destructive escape was re-running the workflow until the counter passed 8 -- forcing a downgrade needs an uninstall, which wipes app data. `git rev-list --count HEAD` only ever increases, tracks the code rather than the CI file, and is already far ahead of every installed build (diet-guard 62 vs 9, screen-locker 118 vs 5, wake-alarm 41 vs 5, todo 51). Needs fetch-depth: 0 -- checkout@v4 is shallow by default and would count 1. Verified the count is identical from the repo root and from app/, so the job's `working-directory: app` default does not affect it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GZH89WEqAjuJT8WZdqc7AP	2026-08-09 18:15:34 +02:00
Krzysztof kuhy Rudnicki	e3cd68dc21	Build and publish a signed APK on every push to main ... screen-locker had no APK build at all; releases were not produced. Adds a standalone release-apk.yml plus the release signing config the app was missing. Signing follows the pattern proven in home_inventory: gradle reads android/key.properties when present and falls back to the debug key when absent, so local `flutter run --release` is unaffected. CI writes that file from repository secrets and shreds it afterwards, and apksigner fails the build closed if a debug-signed APK ever appears. This repo has no Flutter analyze/test job, so the release job is not gated on tests — a broken commit still publishes, with the build failing as the only backstop. Add `needs:` if a Flutter CI job is added later. versionCode is github.run_number, which is per-workflow-file — this file must never be renamed, or the counter resets and updates stop installing. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014dzgcZxmpS3VtmLci2sbxj	2026-08-04 20:55:04 +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	c0aae7d05b	Make the lock overlay's sport selector usable, and focus its form fields ... The manual-workout sport selector was a `tk.OptionMenu`, and while the screen was locked it could not be changed. A posted Tk menu is a separate override-redirect toplevel that takes the Tk grab for itself, and gatelock's 1s recovery tick attacks it from both sides: `_surfaces.enforce()` lifts the lock surface over the menu, and `_reassert_grab()` read the grab sitting on the menu as "the grab was lost" and yanked it back. The menu opened on click and died within a second. On 2026-07-26 that forced an hour-long walk to be logged through the table-tennis form, with the reason typed into `racket`. Radio buttons instead. They are ordinary children of the surface, so they lift with it and live inside the root's grab tree -- neither mechanism can reach them. That is a structural guarantee, not a tuned workaround; the alternative, teaching gatelock to skip its lift while a popup is posted, would open a window where something could cover the lock. They are also the first version of this control styled from the shared palette, where the OptionMenu was default grey on the dark overlay. Nothing on a lock surface may open a popup, so two halves enforce it. The static half walks each module's AST for popup-creating names -- AST rather than a source regex because the modules explain this bug in prose that names the very widgets being banned. Its module list is derived ("imports tkinter", minus a short reasoned exemption list) rather than hardcoded, so a new lock screen is in scope the day it is written; a hardcoded list drafted today would already have missed `_sick_dialog`. The behavioural half is `scripts/verify_lock_popup_safety.py`: it builds the real form with real Tk, replays both hostile behaviours for five ticks, and re-runs the original failure so the mechanism stays demonstrated rather than described. It re-execs itself under Xvfb -- a global grab on the developer's own session would freeze it -- and a CI job runs it, because the pytest suite replaces the whole `tk` module and so cannot host it. Separately, no field ever took keyboard focus. Under a global grab that means typing goes nowhere with no other window on screen to reveal why. The manual-workout and sick-justification forms now each name their own first field via a `focus=` flag; `on_focus_ready` genuinely has nothing to focus (it fires before those screens exist) and its docstring now says that instead of claiming the lock window has no typed input at all. `scripts/fix_2026_07_26_sport.py` re-files that walk as sport "other", rebuilt through the form's own draft/validate/build path so it carries exactly the writer's key set, and re-signed. `start_time` and the date are untouched so `workout_id` stays stable and the phone converges instead of gaining a duplicate. Kept as the audit trail for the edit; the walk's details come from the entry and `--details`, so nothing personal lands in a tracked file. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-07-26 15:08:08 +02:00
Krzysztof kuhy Rudnicki	23b9bd5cde	Install Flutter in pre-commit CI so flutter-analyze can run ... The pre-commit workflow has been red on every run since 2026-07-04: it executes the flutter-analyze hook but never installed Flutter, so the hook failed command-not-found each time (Dart was never actually analyzed in CI). Add subosito/flutter-action pinned to 3.44.6 (matching the version the app is developed against, Dart SDK ^3.12.2) plus a `flutter pub get` step so `flutter analyze` resolves packages. The sibling flutter-test-coverage hook is pre-push-only and does not run in this default-stage CI job, so analyze is the only Flutter dependency here. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018PMRRVVkeRyrSaaqueMZKG	2026-07-11 17:23:42 +02:00
Krzysztof kuhy Rudnicki	e8bef664f5	chore: set up as standalone repo ... Extracted from testsAndMisc monorepo. Changes: - Rewrote imports from python_pkg.screen_locker.* → screen_locker.* - Vendored python_pkg.shared.log_integrity → screen_locker._log_integrity - Vendored wake_alarm constants (ALARM_DAYS, WAKE_AFTER_HOURS, RTCWAKE_BIN) into _constants.py - Extracted has_workout_skip_today into new screen_locker._wake_state module - Added tests for _wake_state.py (392 tests, 100% branch coverage) - Moved scripts/service files to repo root - Added standalone pyproject.toml, requirements.txt, .pre-commit-config.yaml, .gitignore - Added GitHub Actions CI workflows Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-05-28 07:43:06 +02:00