simonoppowa/OpenNutriTracker

Parent Part of the AI-assisted meal logging feature (#599), staged on feature/ai-assisted-meal-logging. Found during the device acceptance pass, #830. What to build Two own-server disclosure strings carry a doubled comma in four locales: ... und jedes Foto, das du dort auslesen lässt,, an {host} gesendet ... Visible on device in the AI settings dialog as soon as an own-server address is entered. Affected keys, in cs, de, sk and uk — 8 strings: aiAssistDisclosureOwnServerSecure aiAssistDisclosureOwnServerPlaintext English is correct, and the other locales are unaffected. These four are machine-written translations from #838 / #845, which were flagged at the time as wanting a native-speaker check — this is the first thing that check would have caught, so it is worth treating the typo as the cheap part and the review as the point. Per AGENTS.md and #650: edit the ARBs textually, one file at a time, never let a formatter near them, and keep the per-locale key counts moving equally

Problem / motivation The existing iOS widget request (#192) is broad. A contributor needs a bounded first milestone that establishes the required native integration and provides immediate value without also taking on watch faces, interactive controls, or multiple widget families. Proposed solution Implement a read-only iOS home-screen widget that displays today's calorie progress. Acceptance criteria: Add an iOS Widget Extension target using SwiftUI and WidgetKit Configure an App Group shared by the Runner and widget extension Persist today's consumed calories and calorie goal to the shared container whenever relevant app data changes Display consumed calories, goal, and progress in at least the small widget family Show a safe placeholder when no profile or nutrition data is available Refresh the widget after the shared values change Tapping the widget opens OpenNutriTracker Document the App Group/capability setup needed for local development and release signing Add appropria

Problem / motivation When food search returns no matches, the screen offers little guidance about the next useful action. Users can interpret this as a dead end even though they can scan a barcode or create a custom food. This is a focused extraction from #458. Proposed solution Add an actionable empty state to no-result food searches. Acceptance criteria: Distinguish an untouched/empty query from a completed search with zero results For a zero-result search, explain that no matching foods were found Offer actions to scan a barcode and create a custom food Preserve the current query when navigating away and back where practical Do not show the zero-result state while providers are still loading Handle partial provider failures separately from genuine zero results Add stable Semantics(identifier: ...) values to each action Add widget tests for initial, loading, results, partial-failure, and zero-result states Add localized strings to all ARBs and manually maintained generated

Problem / motivation Adding food from the global + action currently asks users to select Breakfast, Lunch, Dinner, or Snack before they can continue. In most cases the current time provides a useful default, making this an avoidable decision in the common path. This is a focused extraction from #458. Proposed solution Preselect a suggested meal type based on the device's local time while keeping every meal type immediately selectable. Acceptance criteria: Define the time ranges for Breakfast, Lunch, Dinner, and Snack in one testable helper Use the device's local time to determine the initial suggestion Visually preselect the suggested meal type when the add-meal flow opens from the global + action Let the user choose a different meal type before continuing Do not change flows launched from a specific meal section; those must retain that explicit meal type Handle boundary times deterministically Add unit/widget tests covering each range, boundaries, and explicit meal-section beh

Problem / motivation Logging a food often requires manually entering a common portion even when users want a simple fraction or multiple of the displayed serving. This adds friction to a frequently repeated action. This is a focused extraction from #458. Proposed solution Add quick-select serving chips to the food detail/logging screen. Acceptance criteria: Show quick choices for 0.5×, 1×, and 2× when a valid serving size is available Include a 100 g choice for foods measured by mass Selecting a chip updates the existing quantity/unit controls and nutrition preview Manual quantity and unit entry continues to work and clears or updates chip selection appropriately Do not show invalid options for foods without the required serving metadata Preserve locale-aware unit labels and conversions Add stable Semantics(identifier: ...) values to each interactive chip Add widget tests for selection, nutrient recalculation, manual override, and missing-serving behavior Remembering the l