confirmMealMutationDraft
ChatGPTApply only the latest displayed proposal explicitly approved in a separate later user turn. Never call in the proposal turn, for ambiguous yes, cancellation or a superseded proposal. Keep draftId internal.
createMealDeleteDraft
ChatGPTPrepare deletion of one identified meal; show the meal and date, then ask for explicit approval in a later turn. Does not delete it.
createMealEditDraft
ChatGPTPrepare an edit proposal for one identified saved meal; does not apply the edit. Include a complete five-nutrient snapshot for every item, recomputing it when food or quantity changes. Show old/new values and ask for explicit approval in a later turn. Food names are immutable.
getDietProfile
ChatGPTRead the user's explicitly saved dietary approaches before tailored meal reflection or when asked. Never infer a profile from meals or health details.
getHelp
ChatGPTRead product help for questions or confusion. Answer only what returned sourced facts/FAQ establish; unsupported details remain unconfirmed. Never automatically collect a complaint or question. No question text is sent or stored by getHelp.
getMeals
ChatGPTRead saved meals in a bounded interval. Follow nextOffset until null. Never write while reading. When sharing a timeline link, copy the returned timelineUrl exactly; never invent or rewrite its domain or path. If absent, do not guess a fallback URL.
getTimeline
ChatGPTRead recent saved meals only when requested; use getMeals for a date range. When sharing a timeline link, copy the returned timelineUrl exactly; never invent or rewrite its domain or path. If absent, do not guess a fallback URL.
previewFeatureRequest
ChatGPTOpen a review ONLY when the user explicitly wants to send a feature request. Supply only the selected request text, never the surrounding conversation, health details, secrets or third-party information. Preserve the original wording; do not silently summarize. No request is saved. The user must review/edit the exact text and press Send in the widget. Cancellation saves nothing. If the widget is unavailable, explain that submission is unavailable; never send on the user's behalf.
previewHelpQuestion
ChatGPTOpen review ONLY when the user explicitly wants to send a product question to improve help/FAQ. Do not automatically collect unresolved questions. Preserve the selected original wording, without conversation history, sensitive or third-party information. Use a known topic only when relevant; otherwise unanswered. No DB storage until the user reviews/edits and presses Send in the widget. Never promise an answer or invent one.
recordMeal
ChatGPTCall once, without an extra save confirmation, only for an unambiguous first-person report of food already consumed. Prefer all five estimated nutrition values and their food-only basis when available. Unknown nutrition may be omitted or null; never invent values to satisfy validation. Never call for advice, plans, quotations, third-party reports, fiction, or when the user says not to record. Never send conversation text or health details. Reuse idempotencyKey only for an identical retry after an uncertain outcome. When sharing a timeline link, copy the returned timelineUrl exactly; never invent or rewrite its domain or path. If absent, do not guess a fallback URL.
submitFeatureRequest
ChatGPTApp-only action for the user's Send button. Save the exact reviewed text once. Never invoke from model conversation.
submitHelpQuestion
ChatGPTApp-only Send button action for the exact reviewed help question. Never invoke from model conversation. Store separately from feature requests.
updateDietProfile
ChatGPTSave only dietary approaches the user explicitly asks to remember. Never infer them from a meal, diagnosis, symptom, medication or treatment. An empty list clears the profile.