feat: cooking history/gallery, unit conversion, nutrition diary, pantry scan, digest cron, nutrition-targeted meal plans

Six M-sized items from HANDOFF.md's new-features backlog:

- Profile tabs: cooking-history stats (total cooked, last-cooked, streak)
  and a "cooked it" photo gallery, both owner-only
- Display-time unit conversion (metric<->imperial) for recipe ingredients,
  respecting each user's unitPref; original value always shown alongside
  the conversion
- Nutrition daily diary: per-day macro totals computed from cooking history
  x recipe nutritionData, compared against user goals
- Pantry scan: real barcode lookup (zxing + Open Food Facts, no API key)
  with an AI-vision fallback for unbarcoded items, always confirm-before-
  insert, both paths tier/rate-limited like other AI features
- Weekly digest email: new followers/comments/ratings + trending recipes,
  sent via a new `cron` Docker stage (alpine+crond+curl) and `digest-cron`
  compose service hitting a bearer-token-protected internal route
- Meal-plan generation can now target a user's nutrition goals as a
  prompt-level nudge (recipes are AI-invented, not DB-sourced, so this
  can't be a hard macro constraint)

Caught a real deploy-breaking issue while adding the cron stage: appending
it after `runner` silently changed the Dockerfile's default build target,
and `web`'s compose config didn't pin one — fixed by pinning `target:
runner` explicitly. Verified with typecheck, lint, and three separate
`docker build --target` runs (runner/cron/migrator) plus `docker compose
config` validation.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

apps/web/app/api/v1/ai/meal-plan/generate/route.ts

@@ -1,6 +1,6 @@
 import { NextRequest, NextResponse } from "next/server";
 import { z } from "zod";
-import { db, recipes, recipeIngredients, recipeSteps, mealPlans, mealPlanEntries, pantryItems, eq, and } from "@epicure/db";
+import { db, recipes, recipeIngredients, recipeSteps, mealPlans, mealPlanEntries, pantryItems, userNutritionGoals, eq, and } from "@epicure/db";
 import { requireSession } from "@/lib/api-auth";
 import { applyRateLimit } from "@/lib/rate-limit";
 import { getDefaultProviderWithKey } from "@/lib/ai/resolve-user-key";
@@ -19,6 +19,7 @@ const Schema = z.object({
   usePantry: z.boolean().default(false),
   pantryMode: z.boolean().default(false),
   difficulty: z.enum(["easy", "medium", "hard"]).optional(),
+  targetNutritionGoals: z.boolean().default(false),
 });
 
 export async function POST(req: NextRequest) {
@@ -56,6 +57,24 @@ export async function POST(req: NextRequest) {
     pantryItemNames = pantry.map((p) => p.rawName);
   }
 
+  // Optionally fetch the user's nutrition goals to nudge the AI toward them.
+  // Silently ignored (no-op) if the user hasn't set any goals — no need to
+  // fail the whole generation over a missing preference.
+  let nutritionGoals: { caloriesKcal?: number | null; proteinG?: number | null; carbsG?: number | null; fatG?: number | null } | undefined;
+  if (parsed.data.targetNutritionGoals) {
+    const goals = await db.query.userNutritionGoals.findFirst({
+      where: eq(userNutritionGoals.userId, userId),
+    });
+    if (goals && (goals.caloriesKcal || goals.proteinG || goals.carbsG || goals.fatG)) {
+      nutritionGoals = {
+        caloriesKcal: goals.caloriesKcal,
+        proteinG: goals.proteinG,
+        carbsG: goals.carbsG,
+        fatG: goals.fatG,
+      };
+    }
+  }
+
   const result = await withAiQuota(userId, session!.user.tier as "free" | "pro", () =>
     generateMealPlan(
       {
@@ -65,6 +84,7 @@ export async function POST(req: NextRequest) {
         days: parsed.data.days,
         pantryMode: parsed.data.pantryMode,
         difficulty: parsed.data.difficulty,
+        nutritionGoals,
       },
       { ...config, userContext: privateBio ?? undefined },
       locale