create_locker (+ _relaxed_day / _early_bird variants) patched Path.resolve to return tmp_path, but ScreenLocker.__init__ computes script_dir = Path(__file__).resolve().parent — the .parent turned the intended per-test tmp_path into tmp_path.parent, pytest's session-shared temp base. Every factory-built locker therefore shared ONE workout_log.json, so any test that wrote a log polluted it and test_saves_pending_marker's `assert not locker.log_file.exists()` passed or failed purely by random ordering (pytest-randomly). The flake was invisible until now because CI died at conftest import (missing crdt_sync) before any test ran; fixing that import in the prior commit exposed it. Reproduced deterministically at CI seed 2701400184. Fix: resolve() now returns tmp_path / "screen_locker" so .parent is the unique per-test tmp_path — each locker gets its own log_file. Also stops tests writing workout_log.json into the real source tree. Verified 747 passed across seeds 2701400184/1/42/999/123456 (was 1 failed at the CI seed). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018PMRRVVkeRyrSaaqueMZKG |
||
|---|---|---|
| .github/workflows | ||
| docs/todo | ||
| screen_locker | ||
| scripts | ||
| stronglift_replacement | ||
| .gitignore | ||
| .mcp.json | ||
| .pre-commit-config.yaml | ||
| CLAUDE.md | ||
| early-bird-workout-check.timer | ||
| install_autostart.sh | ||
| install_systemd.sh | ||
| pyproject.toml | ||
| README.md | ||
| remove_autostart.sh | ||
| remove_systemd.sh | ||
| requirements.txt | ||
| run.sh | ||
| workout-locker.service | ||
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.