feat(meal-planner): structured output for add_recipe_to_meal_plan (v0.11.1)

Map verified mpcreateByRecipeId response (a00.r.r dish object) to the
same field layout as get_meal_plan entries. is_from_recipe_box is always
true since this tool only creates recipe-box entries.

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

SPEC.md

@@ -734,9 +734,23 @@ POST https://api.familywall.com/api/mpcreateByRecipeId
 | `type` | ja | Mahlzeiten-Typ: `BREAKFAST`, `LUNCH`, `SNACK`, `DINNER` |
 | `clientOpId` | nein | Optionale Client-seitige Idempotenz-ID (wird weggelassen) |
 
-**Response-Struktur:** TBD — Tool liefert Raw JSON zur Verifizierung (→ v0.11.1).
+**Response-Struktur:**
+```
+a00.r.r                     → vollständiges dish-Objekt
+  .metaId                   → neue Dish-ID (z.B. "dish/16282169_20009811")
+  .date                     → Datum (z.B. "2026-04-18")
+  .type                     → Mahlzeiten-Typ (BREAKFAST/LUNCH/SNACK/DINNER)
+  .name                     → Rezeptname
+  .recipeId                 → verknüpfte Rezept-metaId
+  .familyId                 → Kreis-metaId
+  .accountId                → Ersteller-accountId
+  .sortingIndex             → Sortierung (numerischer Timestamp als String)
+  .rights.canUpdate         → "true"
+  .rights.canDelete         → "true"
+a00.cn                      → "mpcreateByRecipeId" (Endpoint-Echo)
+```
 
-**Verifiziert am:** 2026-04-17 (Parameter aus JS-Bundle; Response TBD)
+**Verifiziert am:** 2026-04-17 via FW_DEBUG=1
 
 ### Weitere Meal Planner Endpoints (nicht implementiert)