mirror of
https://github.com/kuhyx/screen-locker.git
synced 2026-11-11 13:27:41 +01:00
Krzysztof kuhy Rudnicki
6a07dc56aa
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
Tests / flutter-coverage (push) Waiting to run
Tests / web-coverage (push) Waiting to run
release-apk / release (APK) (push) Waiting to run
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
53 lines
2.6 KiB
Markdown
53 lines
2.6 KiB
Markdown
# 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.
|
|
|
|
## Shutdown time
|
|
|
|
Every day starts at **19:00** from 2026-10-01, 20:00 before it (`base_hour()` in
|
|
`screen_locker/_shutdown_base.py`)
|
|
and bonuses push it later, capped at 23:00: the first counted workout +2h,
|
|
each further one +1h, an accepted LeetCode submission that day +1h (flat,
|
|
read from leetcode-guard's ledger, once per day), and a credited paper-book
|
|
reading session of 20+ pages / 20+ minutes +1h (flat, read from
|
|
[book-guard](https://github.com/kuhyx/book-guard)'s ledger, once per day, keyed
|
|
on when the reading ended). The config is re-derived from
|
|
those sources on each new day, so nothing has to be "remembered" across reboots.
|
|
|
|
A RunnerUp run is credited from its TCX export, found in the WebDAV drop
|
|
directory RunnerUp uploads to on this machine (`~/data/cloud/RunnerUp/`, plus
|
|
`processed/` once endurain-import has taken it) or, when a phone is adb-visible,
|
|
in `/sdcard/Documents/RunnerUp/`. The 15-minute `workout-sync.timer` scans both,
|
|
so a run finished after 20:00 pushes the hour later without the phone being
|
|
plugged in; the per-minute shutdown check then lifts the night lockdown on its
|
|
own once the hour is past "now" (digital-wellbeing's check script).
|
|
|
|
## 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:
|
|
|
|
```bash
|
|
./scripts/setup_mcp.sh
|
|
```
|
|
|
|
Registration lives in the checked-in [`.mcp.json`](./.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`.
|