A self-contained prompt for a fresh session to finish the last 10 files over the 250-line cap, all Dart. It carries the parts that are expensive to rediscover: - scripts/split_dart_test.py, which works, plus the envelope it works in: one pass from the pristine file, no post-main() declarations, no local function declarations in the preamble. All four remaining test files sit outside that envelope, and the fix (hoist shared fakes into a _fixtures.dart sibling first, as its own commit) is written down. - The three Dart constraints each of which cost a debugging cycle here: setState is @protected so it cannot be called from an extension; extension methods dispatch statically so a method a test fake overrides must stay in the class (this hung four tests on pumpAndSettle rather than failing an assertion); static members need qualifying inside an extension. - 402 as the test-count invariant, and the note that dart analyze is a no-op on test/ so the count is the only signal there. - That the local gatelock (0.5.0) is ahead of the pin (0.4.0), so the popup gate's failure here is environment drift and must NOT be "fixed" in code. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EveB813BQ8abAP68VSqZ5Y |
||
|---|---|---|
| .github/workflows | ||
| docs | ||
| screen_locker | ||
| scripts | ||
| stronglift_replacement | ||
| .gitignore | ||
| .mcp.json | ||
| .pre-commit-config.yaml | ||
| 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-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.