Go to file
Krzysztof kuhy Rudnicki 84bd550331
Some checks are pending
pre-commit / pre-commit (push) Waiting to run
Tests / test (3.10) (push) Waiting to run
Tests / test (3.11) (push) Waiting to run
Tests / test (3.12) (push) Waiting to run
Migrate diet_guard to gatelock v0.2.0 per-output locking
The gate is laid out once per live output instead of once on the primary,
and claims the screen through an Arbiter at RANK_DIET_GUARD so the wake alarm
and the workout locker can both outrank it.

Three kinds of state needed three different answers. The display fields
already fanned out for free -- GateVars holds root-mastered StringVars bound
to labels. The typed-in fields did not: amount, per, meal name and the four
macro cells were bare tk.Entry widgets, so N copies would have been N
independent forms. They are variable-backed now, which is what makes logging
work from whichever screen the user is actually looking at. The description
box and the suggestion list cannot be shared at all -- tk.Text and tk.Listbox
have no variable -- so those genuinely diverge and reads answer from the copy
the user touched.

The History tab is per-surface too: its grid, budget field and edit button
are driven across every monitor, with the budget likewise variable-backed so
the value cannot differ between screens mid-edit.

Laying the gate out on the primary monitor only was considered and rejected:
not having to hunt for the screen the form landed on is the entire point of
per-output locking.

Tests: the suite hung rather than failed on first run -- diet_guard patches
its own `tk`, but LockWindow builds Toplevels through gatelock's, and real
tkinter over a MagicMock root recurses without bound. `_hermetic_gatelock`
closes that and redirects the runtime dir so no test can stand a production
locker down. Every other test runs single-output, where fan-out is
unobservable, so test_gatelock_fanout runs on two; each assertion was checked
by cropping the fan-out loops to the first surface and confirming it goes red.

_gatelock_ui and _gatelock_calendar were each split in two to stay under the
500-line limit, and GateVars' typed-in fields moved into a nested
GateEntryVars rather than raising pylint's attribute cap.

470 tests, 100% branch coverage, pre-commit clean, no lint suppressions.
2026-07-25 16:56:13 +02:00
.github/workflows Extract diet_guard from testsAndMisc as a standalone repo 2026-06-22 12:18:39 +02:00
app theme.dart: define secondary/tertiary ColorScheme roles 2026-07-22 19:46:07 +02:00
diet_guard Migrate diet_guard to gatelock v0.2.0 per-output locking 2026-07-25 16:56:13 +02:00
docs Add change explanation: desktop-web-build 2026-07-20 17:27:42 +02:00
scripts Gate the companion app in the push hook, and document it properly 2026-07-20 17:01:40 +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 Migrate diet_guard to gatelock v0.2.0 per-output locking 2026-07-25 16:56:13 +02:00
CLAUDE.md Wire theme.dart into the app; replace remaining raw Colors.* literals 2026-07-21 21:50:16 +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
diet-guard-sync.timer Add cross-device log sync (Python half of Milestone 3) 2026-06-22 19:36:27 +02:00
install.sh Add budget-adherence calendar, streaks, and freely-editable synced budget 2026-07-13 21:31:45 +02:00
pyproject.toml Migrate diet_guard to gatelock v0.2.0 per-output locking 2026-07-25 16:56:13 +02:00
README.md Add MCP server exposing diet status + a gated log_meal 2026-07-10 21:36:46 +02:00
requirements.txt Migrate diet_guard to gatelock v0.2.0 per-output locking 2026-07-25 16:56:13 +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)

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.
  • 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.