Go to file
Krzysztof kuhy Rudnicki f79b3c69cf
Some checks are pending
dependency freshness / dependencies on newest stable (push) Waiting to run
md-naming / markdown naming convention (push) Waiting to run
pre-commit / pre-commit (push) Waiting to run
Tests / test (push) Waiting to run
Tests / lock-popup-safety (push) Waiting to run
release-apk / release (APK) (push) Waiting to run
Take the freshness gate's four bumps: flutter_secure_storage 11.1.1, sqflite 2.4.4, sqflite_common_ffi 2.4.3, @types/node 26.5.1
Pre-push ci-mirror was red at HEAD on exactly these four; the lock was
regenerated with the pinned Flutter 3.47.4 (which also moves
flutter_secure_storage_platform_interface to 2.1.0 transitively).

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FcU5dCcUNHMAMzUNChdrrJ
2026-09-13 09:54:32 +02:00
.github/workflows Take the freshness gate's ten bumps: Flutter 3.47.4, mcp 2.2.0, React 19.3, node 24.21 2026-09-12 19:52:30 +02:00
docs Re-point paths for the ~ reorganisation (home-tidy) 2026-09-11 18:46:28 +02:00
prompts Re-point paths for the ~ reorganisation (home-tidy) 2026-09-11 18:46:28 +02:00
screen_locker Key every workout day on the LOCAL calendar day, not UTC 2026-09-13 09:50:06 +02:00
scripts Key every workout day on the LOCAL calendar day, not UTC 2026-09-13 09:50:06 +02:00
stronglift_replacement Take the freshness gate's four bumps: flutter_secure_storage 11.1.1, sqflite 2.4.4, sqflite_common_ffi 2.4.3, @types/node 26.5.1 2026-09-13 09:54:32 +02:00
web Take the freshness gate's four bumps: flutter_secure_storage 11.1.1, sqflite 2.4.4, sqflite_common_ffi 2.4.3, @types/node 26.5.1 2026-09-13 09:54:32 +02:00
.fvmrc Take the freshness gate's ten bumps: Flutter 3.47.4, mcp 2.2.0, React 19.3, node 24.21 2026-09-12 19:52:30 +02:00
.gitignore Serve the lock decision, its history and its health at 127.0.0.1:8770 2026-08-29 22:50:19 +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 Take gatelock 0.8.1: nested LockConfig 2026-09-12 19:52:38 +02:00
AGENTS.md Tell "could not check" apart from "no workout", and stop double-granting bonuses 2026-08-24 13:07:20 +02:00
arm.sh Make disarming survive the install scripts, not just systemd 2026-08-22 12:54:13 +02:00
CLAUDE.md Adopt crdt-sync v0.9.0's bundled sync_log signature 2026-08-21 14:28:14 +02:00
early-bird-workout-check.timer Re-arm the locker, and make a disarmed enforcer impossible to miss 2026-08-17 16:47:25 +02:00
install_autostart.sh chore: set up as standalone repo 2026-05-28 07:43:06 +02:00
install_systemd.sh Take gatelock 0.8.1: nested LockConfig 2026-09-12 19:52:38 +02:00
install.sh Re-point paths for the ~ reorganisation (home-tidy) 2026-09-11 18:46:28 +02:00
pyproject.toml Take gatelock 0.8.1: nested LockConfig 2026-09-12 19:52:38 +02:00
README.md Add read-only MCP server exposing workout/lock status 2026-07-10 21:28:09 +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 Take gatelock 0.8.1: nested LockConfig 2026-09-12 19:52:38 +02:00
run.sh Reconcile the venv on launch, so a pin bump cannot sit unnoticed 2026-08-23 06:56:26 +02:00
screen-locker-web.service Serve the lock decision, its history and its health at 127.0.0.1:8770 2026-08-29 22:50:19 +02:00
TODO-file-length-250.md Re-point paths for the ~ reorganisation (home-tidy) 2026-09-11 18:46:28 +02:00
TODO-finish-dart-250.md Re-point paths for the ~ reorganisation (home-tidy) 2026-09-11 18:46:28 +02:00
TODO-pylint-to-ten.md Add the removal marker to every TODO file 2026-08-24 15:56:24 +02:00
workout-locker.service Close the four gaps that let a decided lock never reach the screen 2026-08-30 15:24:45 +02:00
workout-locker.timer Close the four gaps that let a decided lock never reach the screen 2026-08-30 15:24:45 +02:00
workout-sync.service Re-point paths for the ~ reorganisation (home-tidy) 2026-09-11 18:46:28 +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

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.