utils/gatelock/systemd/evening-gates.service
Krzysztof kuhy Rudnicki 115e050110 gatelock 0.15.0: evening gate chain
Add gatelock.evening_chain: `pending` lists the unpaid rungs (book,
tutor, LeetCode), `run` runs each gate in order before night lockdown.
Also RANK_EVENING_GATE = 150, systemd/evening-gates.service and
install_evening_gates.sh (never enables or starts the unit).

Failure paths:
- pending: unreadable ledger or key, reader error, any exception ->
  exit 2 on stderr. FAIL CLOSED (root enters lockdown).
- pending: free day, sick day, 23:00 or later -> exit 1 (stands down).
- run: a rung it cannot check is unpaid, its gate stays up (closed).
- run: gate fails, or exits 0 with the rung unpaid -> skipped; two in
  a row -> exit 1, never a spin (stops, root enters lockdown: closed).
- run: gate exit 10 -> exit 0; exit 3 (no X) -> exit 3; gate still up
  at 23:00 is killed -> exit 0 (the hard time wins).
- earned_time/freedays/sickdays are an optional `evening` extra, so a
  locker never fails to start over them.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WzxdWYGbnVt12uFXKgNYm8
2026-11-17 21:24:26 +01:00

17 lines
670 B
Desktop File

[Unit]
Description=Evening gate chain: book, tutor, LeetCode before night lockdown
After=graphical-session.target
# Started by root's day-specific-shutdown-check (systemctl --user -M kuhy@
# start) when `python3 -m gatelock.evening_chain pending` exits 0. There is no
# timer and no [Install]: arming it any other way would put a gate up on a day
# nobody asked for one.
[Service]
Type=simple
Environment=DISPLAY=:0
Environment=XAUTHORITY=%h/.Xauthority
ExecStart=/usr/bin/python3 -m gatelock.evening_chain run
# A stopped or finished chain stays stopped: root reads "inactive after it was
# started tonight" as "kuhy ended the evening" and enters lockdown.
Restart=no