Use these procedures as task-oriented reference. They describe public capabilities and verification steps, not private implementation. UI labels can vary by version.
Use a meal with known ingredient quantities.
Check raw/cooked preparation for each selected food.
Confirm the serving basis and units before entering the quantity.
Include meaningful added ingredients such as oils or sauces.
Review missing nutrient fields separately from measured zeros.
Correct the log consistently before comparing it with another day.
The meal quantities and reference entries are internally consistent.
A database value is not a lab measurement of the actual meal. Verify allergens from ingredient labels rather than relying only on a generated plan.
Physically check the items you intend to use.
Review stored quantities and expiry dates.
Correct consumed or discarded items.
Plan meals around available ingredients.
Inspect suggested purchases against the cupboard.
Confirm quantities before buying.
The list reflects actual stock rather than stale records.
An expiry entry does not establish food safety. Correct the underlying pantry record if suggestions repeatedly include an item already present.
Record app/version, device/OS, selected mode, input conditions and the smallest failing step. Distinguish expected behavior from the observed result. Use synthetic examples and omit credentials or private records.
Documentation index · Capabilities and limits · Support and sources