diet-guard/diet-guard-gate.timer

[Unit]
Description=Periodically run the Diet Guard gate check

[Timer]
# Check on a WALL-CLOCK schedule (every 30 min, on the hour and half-hour).
# The 5-hour "log a meal" threshold and the 08:00-22:00 eating window are
# enforced inside gate_is_due(), so the timer only needs to fire often enough to
# notice the boundary; 30 min is plenty.
#
# Why OnCalendar and not OnBootSec/OnUnitActiveSec: the gate is a *blocking*
# oneshot -- it stays up until a meal is logged -- and a monotonic schedule
# computed no next elapse once the service had run (and none at all across a
# reboot), leaving the timer dormant (NextElapse=infinity). OnCalendar re-arms
# every period regardless of how long the gate stayed open, and Persistent
# catches a run missed while the machine was suspended.
OnCalendar=*-*-* *:00/30:00
Persistent=true

[Install]
WantedBy=timers.target
feat(diet_guard): add meal-logging screen-lock gate with trigger fix Add the diet_guard package: a screen-locking meal-logging gate that fires on 4-hour slots (08/12/16/20) and records calories/macros, persisting an autocompleting food bank. - Trigger fix: the systemd timer fires at session start (Persistent=true) before lightdm has written ~/.Xauthority, so the gate crashed with a TclError instead of locking the screen. Add wait_for_display() / _display_is_ready() in _gatelock.py and wire it into _cli._cmd_gate so the gate retries on the next tick instead of crashing; add Environment=XAUTHORITY=%h/.Xauthority to the service as belt-and-suspenders. - Food-bank hardening: a transiently corrupt food_bank.json was warned about on every keystroke and then silently overwritten (data loss). _read_bank now quarantines it via _quarantine_corrupt_bank() (warn-once + timestamped backup) before starting fresh. - Multi-item meals: new _meal.py (MealItem, meal_total, MEAL_SOURCE), remember_meal() + _upsert() in _foodbank.py, and a "+ Add item" control in the gate that logs both the individual items and the composite meal. - Bundle resolve_nutrition's manual macros into a ManualMacros dataclass to stay within the argument-count limit. diet_guard at 100% branch coverage; full pre-commit suite passes. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> 2026-06-10 22:31:18 +02:00			`[Unit]`
			`Description=Periodically run the Diet Guard gate check`

			`[Timer]`
			`# Check on a WALL-CLOCK schedule (every 30 min, on the hour and half-hour).`
			`# The 5-hour "log a meal" threshold and the 08:00-22:00 eating window are`
			`# enforced inside gate_is_due(), so the timer only needs to fire often enough to`
			`# notice the boundary; 30 min is plenty.`
			`#`
			`# Why OnCalendar and not OnBootSec/OnUnitActiveSec: the gate is a blocking`
			`# oneshot -- it stays up until a meal is logged -- and a monotonic schedule`
			`# computed no next elapse once the service had run (and none at all across a`
			`# reboot), leaving the timer dormant (NextElapse=infinity). OnCalendar re-arms`
			`# every period regardless of how long the gate stayed open, and Persistent`
			`# catches a run missed while the machine was suspended.`
			`OnCalendar=--* *:00/30:00`
			`Persistent=true`

			`[Install]`
			`WantedBy=timers.target`