One meal screen, and every fix happens on it

apps/mobile/src/app/meal.tsx is a plate from the moment the estimate lands to the day the meal is deleted: no id means the plate in the scan store, id means a meal in the log. Amounts, swaps, additions and the one question are all in place, in components/meal/.

It replaced seven screens, and the bug the old rule guarded against went with them: a database pick reached from inside a scan used to router.replace to the Search screen, which logged a one-item meal and dropped the user on Today with the scan discarded and the photo already paid for.

Nothing inside the meal screen navigates to find a food now. If a second route for editing a meal appears, that bug has a way back.