First phase of syncing phone-logged manual/off-app workouts to the PC so they count toward the unlock. This phase only establishes the cross-language wire contract; no behavior change to existing flows. - _manual_workout.py: build_sync_payload(draft, date) = build_entry fields + a `kind="manual_workout"` discriminator + the workout's own `date`; and manual_sync_record_id(date, start) -> stable `manual:<date>T<HH:MM>` id. A StrongLifts session payload has no `kind`, so an ingesting PC can route on it and never mistake a manual for a verified session. - test_manual_workout.py: TestSyncWireFormat pins the exact literal payload as the cross-language contract (the Dart workout_app test will reproduce the same literal byte-for-byte; neither side's own round-trip test catches drift from the other). - workout_app/lib/models/manual_workout_constants.dart: hand-maintained mirror of the 7 MANUAL_WORKOUT_* constants + the kind value (Python stays source of truth; the shared fixture is the drift tripwire). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PM3auNTifaVgcXWDizZrjH |
||
|---|---|---|
| .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.