Go to file
Krzysztof kuhy Rudnicki da8822006f Let the phone set the eating window and meal count
The first edit surface, landing after the sync layer so a schedule set here
reaches the PC rather than leaving the two devices deriving different slots.

Three dropdowns -- first meal, last meal, meals per day -- and a live preview
of the checkpoints they derive. Setting 08:00, 20:00 and 5 shows
08:00 · 11:00 · 14:00 · 17:00 · 20:00, which is asserted in the screen test
rather than only in the model's.

Dropdowns rather than showTimePicker: that returns a TimeOfDay with minutes,
and slots are whole hours on both devices by design. They also make the
invalid states unrepresentable instead of validated -- "last meal" offers only
hours after "first", and "meals per day" only counts the window has whole
hours for. MealSchedule.normalized() still clamps, but that is the defence
against corrupt synced data, not the input contract.

Saving re-runs the due-slot check, because reminder ids are slot hours: a
schedule change orphans the ids it no longer contains, and waiting for the
next background tick would leave a stale nag on screen for up to 15 minutes.

The UI is a `part` mixin like settings_kcal_goal.dart -- settings_screen.dart
was at 238 of the 250-line cap and is now at 247.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0159b4E5hh512jYUeaJVNxfM
2026-08-16 14:56:12 +02:00
.github/workflows Enforce the shared 250-line file cap 2026-08-15 16:35:01 +02:00
app Let the phone set the eating window and meal count 2026-08-16 14:56:12 +02:00
diet_guard Sync the meal schedule as sched: fields on the budget record 2026-08-16 14:49:08 +02:00
docs Automate CLAUDE.md's structural rules, then cut it to 189 lines 2026-08-15 16:39:57 +02:00
packaging/aur packaging/aur: track the current release tag 2026-08-10 07:18:53 +02:00
scripts Fix check_patch_targets' own fail-open: put the repo root on sys.path 2026-08-15 21:27:24 +02:00
.gitignore Add CI-mirror pre-push gate + requirements-sync check 2026-07-11 17:58:49 +02:00
.mcp.json Add MCP server exposing diet status + a gated log_meal 2026-07-10 21:36:46 +02:00
.pre-commit-config.yaml Split _state.py and _tk_fakes.py; make the food-log redirect fail closed 2026-08-15 20:21:26 +02:00
CLAUDE.md Make PC sync event-driven; retire the 15-min timer 2026-08-15 19:21:30 +02:00
DESIGN_AUDIT_TODO.md Add a design-rules audit against the new safe-design-rules checklist 2026-07-21 15:25:20 +02:00
diet-guard-gate.service Extract diet_guard from testsAndMisc as a standalone repo 2026-06-22 12:18:39 +02:00
diet-guard-gate.timer Extract diet_guard from testsAndMisc as a standalone repo 2026-06-22 12:18:39 +02:00
diet-guard-sync.service Add cross-device log sync (Python half of Milestone 3) 2026-06-22 19:36:27 +02:00
install.sh Make PC sync event-driven; retire the 15-min timer 2026-08-15 19:21:30 +02:00
LICENSE Add MIT LICENSE 2026-08-09 22:49:29 +02:00
pyproject.toml Use gatelock's shared button and WidgetGroup 2026-08-15 14:23:11 +02:00
README.md Show weekly and monthly average intake on both devices 2026-08-09 14:59:40 +02:00
requirements.txt Use gatelock's shared button and WidgetGroup 2026-08-15 14:23:11 +02:00

diet_guard

A log-to-unlock gate: locks the desktop until a meal is logged once a meal slot (08:00 / 12:00 / 16:00 / 20:00) has elapsed without one, and tracks a sealed daily calorie/macro budget.

Install

bash install.sh

This installs the package + dependencies into system Python's user site-packages (the systemd service runs /usr/bin/python directly, not a venv — see CLAUDE.md), installs the systemd user timer, seals your daily budget, and locks the budget file immutable.

Usage

python -m diet_guard init          # one-time: compute and seal today's budget
python -m diet_guard gate --demo   # test the lock window (safe, closeable)
python -m diet_guard averages      # weekly/monthly average kcal vs budget

Averages

averages prints the mean kcal/day for this week, last week, this month and last month, each labelled under / slightly over / very over.

Three rules make the number honest, and all three are mirrored in the phone app and the gate's History tab:

  • the mean is over logged days only -- a day you forgot to log is not a zero-calorie day, and averaging it in as one would make every gap in the log read as "well under budget";
  • the yardstick is the mean of the budgets that applied on those same days, not today's budget, so editing the budget never retroactively reclassifies a past week (same reason the calendar uses .budget_history);
  • today is excluded -- every period ends at yesterday, because a half-logged today drags the mean far enough to flip the band. On a Monday "this week" therefore reports no logged days yet rather than a flattering number.

The band boundaries are the calendar's own (at or under budget / up to 20% over / more than 20% over), so a period and its day cells can never disagree about what "over" means.

The timer runs the gate automatically every ~30 minutes; no manual invocation is needed once installed.

MCP server

An optional Model Context Protocol server lets an MCP client (Claude Code and its subagents) query today's intake and log meals as typed tools instead of shelling out to the CLI. It runs in its own venv (~/.venvs/diet-guard-mcp) so the mcp SDK never touches the dependency-light system/CLI python path.

Tools:

  • get_status — today's consumed kcal + macros, the consumption band (on track / approaching limit / OVER BUDGET, or none when no budget is sealed), plus due / logged / current meal slots.
  • list_today — today's logged meals (description, kcal, macros, source, slot).
  • get_slots — the day's fixed meal slots and the current one.
  • get_averages — average kcal/day for this/last week and this/last month, each with its band (under / slightly_over / very_over). Returns the intake and the band only — never the period's average budget.
  • log_meal(description, grams=, kcal=, protein=, carbs=, fat=, slot=, confirm=False) — gated write: with confirm=False it previews the resolved nutrition and target slot and mutates nothing; only confirm=True appends the entry. The gate is intrinsic — never add this tool to a permission allowlist, since a client's auto-approve mode would otherwise bypass the human confirmation.

The read tools deliberately never expose the raw daily budget number (only the qualitative band), nor the sealed .budget file, the shared HMAC key, or the sync token — the budget stays hidden by design.

Setup:

bash scripts/setup_mcp.sh   # create the venv and install diet_guard[mcp]

Then restart Claude Code in this repo and approve the project MCP server (registered in .mcp.json).

Development

python -m venv .venv && .venv/bin/pip install -r requirements.txt
.venv/bin/pre-commit install && .venv/bin/pre-commit install --hook-type pre-push
.venv/bin/python -m pytest diet_guard/tests/ --cov=diet_guard --cov-branch --cov-fail-under=100

See CLAUDE.md for scheduling details and production deployment gotchas, and docs/design.md for the original feature spec.