mirror of
https://github.com/kuhyx/screen-locker.git
synced 2026-11-10 19:07:16 +01:00
Krzysztof kuhy Rudnicki
78db299086
The largest lib/ file on the 250-line list and the one never attempted. It has no private widget classes to lift out (pattern A did not apply), so the cut is by responsibility: workout_screen.dart 250 state fields, lifecycle, setState methods workout_screen_session.dart 182 save/restore, break maths, threshold write workout_screen_finish.dart 110 the write-everything finish step workout_screen_body.dart 105 exercise list + break banner workout_screen_dialogs.dart 73 finish/reset confirmations workout_screen_appbar.dart 68 clock + Reset/Finish actions workout_screen_breaks.dart 67 rest timers, threshold edits Two constraints shaped it. `setState` is `@protected` and unreachable from an extension, so methods that call it either stay in the class or split into a class-side wrapper plus a setState-free body — that is why `_finishWorkout` keeps only its three lines and delegates to `_persistFinishedWorkout`. The breaks extension needs real state writes, so the class exposes one named `_applyBreakState` shim rather than scattering the seam. The extensions are named `_Foo`, not `Foo`: extending the private `_WorkoutScreenState` from a public extension trips `library_private_types_in_public_api`. Coverage caught one real regression mid-way. Restructuring the threshold update as a map-returning helper with an `if (s == null) return` guard added a branch no test exercises and dropped the gate to 2753/2754. Rewritten as `_writeThresholds`, mutating in place with the original `if (s != null)` shape, so the extraction stays a pure move. dart analyze clean; 402 tests pass with a byte-identical test-name set (captured via --reporter json and diffed, since a count alone cannot tell a lost test from a duplicated one); flutter coverage back to 100%. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EveB813BQ8abAP68VSqZ5Y |
||
|---|---|---|
| .github/workflows | ||
| docs | ||
| screen_locker | ||
| scripts | ||
| stronglift_replacement | ||
| .gitignore | ||
| .mcp.json | ||
| .pre-commit-config.yaml | ||
| CLAUDE.md | ||
| DESIGN_AUDIT_TODO.md | ||
| early-bird-workout-check.timer | ||
| install_autostart.sh | ||
| install_systemd.sh | ||
| install.sh | ||
| pyproject.toml | ||
| README.md | ||
| refactor_claude_todo.md | ||
| remove_autostart.sh | ||
| remove_systemd.sh | ||
| requirements.txt | ||
| run.sh | ||
| todo_finish_dart_250_prompt.md | ||
| todo_fix_pylint_10_prompt.md | ||
| workout-locker.service | ||
| workout-sync.service | ||
| workout-sync.timer | ||
screen-locker
Tkinter/systemd screen locker with workout tracking, sick-day management, and wake-alarm integration. It enforces a workout cadence by locking the screen until a RunnerUp-verified (or explicitly justified) workout is logged.
MCP server (Claude Code integration)
screen-locker exposes a read-only MCP server (screen_locker._mcp) so
Claude Code and its subagents can query workout compliance and the
lock-decision state through typed tools — without shelling out to the
screen-locker-status CLI or opening the Tk window.
- Read-only tools:
get_status(full status snapshot),get_summary(one-line i3blocks summary +ok/warn/lockstate word),explain_lock(why the screen is / isn't locked right now),get_flags(the individual boolean lock-decision predicates for today). - There are no write/action tools, by design. Nothing here logs a workout or mutates state — workouts are logged only from RunnerUp-verified TCX data, never from a caller's claim. No tool exposes the sync token or any HMAC key.
The mcp SDK is an optional dependency (pip install -e '.[mcp]'), kept out of
the CLI/systemd system-python path. One-time setup of the dedicated venv that
Claude Code spawns:
./scripts/setup_mcp.sh
Registration lives in the checked-in .mcp.json (project scope).
Restart Claude Code in this repo and approve the project MCP-server prompt for it
to load. Verify with claude mcp list.