mirror of
https://github.com/kuhyx/wake-alarm.git
synced 2026-11-22 01:22:20 +01:00
On 2026-09-19 the phone was powered off after the bathroom tag and nothing on the PC noticed: every finished session was published and nothing read it. Now wake-alarm distils the phone's morning into an HMAC-signed ~/.local/state/wake_alarm/morning_session.json (wake-alarm-session.timer, 07:00-11:00 every 2 min) that screen-locker and leetcode-guard read to defer their locks -- provisionally until min(start + 90 min, 09:30) while the session is live, until 11:00 once it completed inside that cutoff, and not at all for a session finished later (the phone switched on at noon completes the legs then; that must un-lock nothing). The phone publishes the session at start as well as at finish (current_session, cleared with the finish stamp), so the PC can tell "started, not finished" from "never started". A required 1-5 energy tap joins the weigh-in and ships as latest_energy with a PC reader mirroring _weight (the shared half is _field_reader). Also fixes the vmbox harness, red since the 2026-09-11 home-tidy: the guest tree lives at ~/wake-alarm, and the INSTALL-OK grep matched vm's echo of the command line. Takes Flutter 3.47.5. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Tp54ewdXRLaimUuT8LgYyn
17 lines
556 B
SYSTEMD
17 lines
556 B
SYSTEMD
[Unit]
|
|
Description=Wake Alarm morning-session refresh, every 2 min through the morning
|
|
Documentation=https://github.com/kuhyx/wake-alarm
|
|
|
|
[Timer]
|
|
# Every two minutes from 07:00 to 10:58, then once at 11:00 (the carrot's end)
|
|
# so the last rewrite lands on the boundary. ~121 Firebase reads/day.
|
|
OnCalendar=*-*-* 07..10:00/2:00
|
|
OnCalendar=*-*-* 11:00:00
|
|
AccuracySec=1s
|
|
# A PC booted mid-morning refreshes at once; the consumers wait up to 30 s
|
|
# for exactly this catch-up before treating the file as stale.
|
|
Persistent=true
|
|
|
|
[Install]
|
|
WantedBy=timers.target
|