Last of the ten. The ~190-line `build()` was the bulk, so it became five private StatelessWidgets rather than list-building methods, per the note in the todo that a previous attempt to slice them out as a raw widget-list getter produced unbalanced brackets. settings_screen.dart 211 state, lifecycle, setState paths settings_screen_sections.dart 190 SYNC, OFFLINE BACKUP, app bar settings_screen_exercise_sections.dart 161 WEIGHTS, TARGET REPS, THRESHOLDS settings_screen_widget.dart 89 the public widget + 11 seams settings_screen_actions.dart 86 setState-free actions Every conditional in the new widgets is the one `build()` already had, in the same shape: no defaulted parameters, no `??` fallbacks, no convenience null checks. That was deliberate — the earlier workout_screen pass showed a single added `if (x == null) return` guard is enough to drop the 100% gate, because it is a line no existing test reaches. `_openSyncSettings` split the way `_finishWorkout` did: the navigation half is setState-free and moved to the actions extension, the post-return progression pull keeps the setState and stays on the class. `bash ~/utils/scripts/check_file_length.sh --all` now exits 0. 402 tests pass with a byte-identical name set, dart analyze clean, coverage 100% (2765/2765). 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.