feat: pantry notes/categories, ingredient-alias matching, cook-log edit/delete, fork-list popover (v0.83.0)

Pantry: notes + category fields (collapsible grouping like the shopping list), a "Merge duplicates" cleanup action, and fixed quantity display precision (was showing raw decimal(10,4) strings like "0.3333 kg" everywhere — pantry, shopping list, print views, Markdown exports).

Ingredient-alias matching: the ingredients table (canonical name + aliases) existed but was never populated or used. Seeded ~10 bilingual EN/FR staples and wired resolution into pantry add/edit, can-cook scoring, auto-deduct-on-cook, and shopping-list pantry-awareness, so "sel"/"sel fin"/"table salt" are recognized as the same ingredient.

Cook log: entries from "Mark cooked" can now be edited and deleted (previously log-only, no fix-a-mistake path). The "Cooked N times" text is a hover tooltip listing every date and opens a full manage sheet on click.

Also: the "Forked by N others" backlink is now a click-to-open popover instead of an always-inline list.

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

apps/web/app/api/v1/pantry/[id]/route.ts

@@ -2,6 +2,7 @@ import { NextRequest, NextResponse } from "next/server";
 import { z } from "zod";
 import { db, pantryItems, eq, and } from "@epicure/db";
 import { requireSessionOrApiKey } from "@/lib/api-auth";
+import { findIngredientIdByName } from "@/lib/ingredient-match";
 
 type Params = { params: Promise<{ id: string }> };
 
@@ -18,15 +19,23 @@ export async function PUT(req: NextRequest, { params }: Params) {
     rawName: z.string().min(1).max(200).optional(),
     quantity: z.string().nullable().optional(),
     unit: z.string().nullable().optional(),
+    notes: z.string().max(500).nullable().optional(),
+    aisle: z.string().max(50).nullable().optional(),
     expiresAt: z.string().datetime().nullable().optional(),
   }).safeParse(body);
   if (!parsed.success) return NextResponse.json({ error: "Validation error" }, { status: 400 });
 
   const data = parsed.data;
+  // Renaming can change which canonical ingredient this item resolves to
+  // (e.g. "sel" -> "sel de table") — re-resolve whenever rawName changes,
+  // rather than leaving a stale link from the item's original name.
+  const ingredientId = data.rawName ? await findIngredientIdByName(data.rawName) : undefined;
   await db.update(pantryItems).set({
-    ...(data.rawName && { rawName: data.rawName }),
+    ...(data.rawName && { rawName: data.rawName, ingredientId }),
     ...(data.quantity !== undefined && { quantity: data.quantity ?? undefined }),
     ...(data.unit !== undefined && { unit: data.unit ?? undefined }),
+    ...(data.notes !== undefined && { notes: data.notes ?? undefined }),
+    ...(data.aisle !== undefined && { aisle: data.aisle ?? undefined }),
     ...(data.expiresAt !== undefined && { expiresAt: data.expiresAt ? new Date(data.expiresAt) : undefined }),
   }).where(eq(pantryItems.id, id));