mirror of
https://github.com/kuhyx/screen-locker.git
synced 2026-11-10 19:07:16 +01:00
Krzysztof kuhy Rudnicki
186bfcabc4
The phone is lost, so no workout can be recorded and enforcement has been disarmed since 2026-08-21. This gives the PC a first-class way to do the workout, reusing the existing app rather than reimplementing the progression rules a second time -- two implementations would guarantee the divergence the "same weights everywhere" requirement forbids. Storage: sqflite has no Linux plugin, so main() installs sqflite_common_ffi's factory, which runs the same schema and migrations against the same SQL. It was already a dev dependency driving the test suite; this only promotes it. Auth: the account password in ~/.config/crdt-sync no longer authenticates (verified: HTTP 400 INVALID_LOGIN_CREDENTIALS). The PC fleet has been running on the cached refresh token all along, so the desktop credential store reads that same 0600 file -- the Dart and Python credential JSON keys are already identical -- and passes null instead of the stale password. This also avoids google_sign_in, which ships no Linux implementation. Lock mode: --lock-mode makes the window the lock surface. There is no Dart API for this, so the runner sets override-redirect and takes an exclusive gdk_seat_grab. Two details cost a debugging cycle each and are commented in place: override-redirect must be set BEFORE the first map, or the window stays mapped and never repaints; and gtk_window_fullscreen() only ASKS the window manager, which cannot see an override-redirect window -- so the geometry is set from the monitor directly, otherwise a strip of live desktop is left uncovered at the edge of a larger screen. The grab is acquired by retry rather than by asking the supervisor to release first: the Python locker keeps its grab while this window maps on top, so the screen is covered continuously instead of exposing the desktop for the whole of Flutter's cold start. Verified against the live data: pulls all 7 exercises from Firebase (Bench 17.5x12, RDL 27.5x8, Row 25x6, Situp 10x31 -- the real weights, not factory defaults), leaves the remote progression byte-identical, and mints its own device id rather than reusing the phone's. A Tk client is refused the grab while the lock holds it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DfJC1Wu1SEgJ6X49k5Jqtg |
||
|---|---|---|
| .github/workflows | ||
| docs | ||
| prompts | ||
| screen_locker | ||
| scripts | ||
| stronglift_replacement | ||
| .gitignore | ||
| .mcp.json | ||
| .pre-commit-config.yaml | ||
| arm.sh | ||
| 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-locker.timer | ||
| 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.