kuhyx/screen-locker
1
0
Fork 0
mirror of https://github.com/kuhyx/screen-locker.git synced 2026-11-10 20:27:13 +01:00
Code Issues Actions 6 Packages Projects Releases Wiki Activity
148 Commits 1 Branch 97 Tags 10 MiB
Python 55.9%
Dart 39.5%
Shell 2.5%
TypeScript 1.2%
C++ 0.3%
Other 0.4%
b8cf634fa6
Go to file
Krzysztof kuhy Rudnicki b8cf634fa6 Record why the popup gate fails on a drifted gatelock 
The RecoveryLoop call in HostileLock matches gatelock 0.4.0, which is what
requirements.txt pins and what the pylint hook installs. gatelock 0.5.0
regroups the five arguments into a RecoveryCollaborators object, so running
this gate against a locally-installed 0.5.0 fails with

    RecoveryLoop.__init__() takes 3 positional arguments but 6 were given

That is environment drift, not a defect in the check -- against the pinned
version the gate runs and passes both halves. Comment says so, and says how to
resync, so the next reader does not "fix" the code to match whatever happens to
be installed. (I nearly did; against the pin that edit would have broken CI.)

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EveB813BQ8abAP68VSqZ5Y
2026-08-15 21:00:49 +02:00
.github/workflows Finish the Python side: scripts, conftest, and the last test modules 2026-08-15 20:57:29 +02:00
docs Qualify a run on EITHER duration or distance, not both 2026-08-14 11:04:18 +02:00
screen_locker Finish the Python side: scripts, conftest, and the last test modules 2026-08-15 20:57:29 +02:00
scripts Record why the popup gate fails on a drifted gatelock 2026-08-15 21:00:49 +02:00
stronglift_replacement Add sync-status card and duration-threshold fixture 2026-08-15 18:41:31 +02:00
.gitignore Make the lock overlay's sport selector usable, and focus its form fields 2026-07-26 15:08:08 +02:00
.mcp.json Add read-only MCP server exposing workout/lock status 2026-07-10 21:28:09 +02:00
.pre-commit-config.yaml Finish the Python side: scripts, conftest, and the last test modules 2026-08-15 20:57:29 +02:00
CLAUDE.md Support multiple workouts per day; fix the dead sync; ban silent failures 2026-07-17 09:22:31 +02:00
DESIGN_AUDIT_TODO.md Add a design-rules audit against the new safe-design-rules checklist 2026-07-21 15:25:20 +02:00
early-bird-workout-check.timer Add heat-skip feature and fix early-bird 9:00 re-check gap 2026-06-29 11:23:19 +02:00
install_autostart.sh chore: set up as standalone repo 2026-05-28 07:43:06 +02:00
install_systemd.sh Let the PC see phone workouts again, and stop losing progression on reinstall 2026-08-10 14:39:02 +02:00
install.sh Make every lock screen keyboard-operable, and add the missing installer 2026-07-30 16:25:45 +02:00
pyproject.toml Split _runnerup_verification, _ui_widgets and _sick_dialog 2026-08-15 20:37:15 +02:00
README.md Add read-only MCP server exposing workout/lock status 2026-07-10 21:28:09 +02:00
refactor_claude_todo.md Split _ui_flows.py into sick-day and lockout flow mixins 2026-08-15 19:56:16 +02:00
remove_autostart.sh chore: set up as standalone repo 2026-05-28 07:43:06 +02:00
remove_systemd.sh Let the PC see phone workouts again, and stop losing progression on reinstall 2026-08-10 14:39:02 +02:00
requirements.txt Let the PC see phone workouts again, and stop losing progression on reinstall 2026-08-10 14:39:02 +02:00
run.sh chore: set up as standalone repo 2026-05-28 07:43:06 +02:00
todo_fix_pylint_10_prompt.md Add todo_fix_pylint_10_prompt.md: raise pylint to a 10.00 gate 2026-08-15 19:18:39 +02:00
workout-locker.service Drop WorkingDirectory/PYTHONPATH from workout-locker.service 2026-06-22 12:43:58 +02:00
workout-sync.service Let the PC see phone workouts again, and stop losing progression on reinstall 2026-08-10 14:39:02 +02:00
workout-sync.timer Let the PC see phone workouts again, and stop losing progression on reinstall 2026-08-10 14:39:02 +02:00

README.md

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/lock state 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.