v0.3.0

Added

• delete_recipe falls back to POST /api/recipes/bulk-actions/delete when
  the row-level delete answers 5xx, which is what a recipe whose rows Mealie's
  ORM cannot cascade does. The result says when the fallback ran. A 404 still
  fails as before, so a typo is never answered by a second attempt.
• MealieError, a ToolError subclass carrying the HTTP status, so a tool can
  branch on the status rather than on message text.
• A spec describing the server as built —
  docs/superpowers/specs/2026-08-10-mealie-mcp-current-state.md. Every tool
  with its endpoint, the caches, the write semantics, and which parts of
  Mealie's API this deliberately does not expose. The 2026-08-09 design
  document is marked superseded; it was a plan, and the code had moved.

Fixed

• Taxonomy objects are trimmed to the keys a write accepts before they go into
  a recipe payload. Foods, units, tags, categories, and tools come off a read
  carrying createdAt, updatedAt, and householdsWithIngredientFood, which
  a write has no business echoing back — Mealie 3.22 tolerates them, but they
  have been reported as 500s elsewhere and Mealie hydrates the row from its own
  id regardless. The same trim applies to the existing tags a merge in
  update_recipe reads back.
• An ingredient line Mealie's parser could not resolve no longer keeps the
  parsed quantity. The whole source line becomes the note, so the amount was
  stored twice and rendered as "500 500 g flour".
• A 5xx now reports FastAPI's detail when the body carries one, instead of
  the raw first 200 characters of JSON.
• The howto said manage_taxonomy(action="list") pages at 200. It pages at 50,
  so anyone sizing a sweep off that number was out by a factor of four.
• The install note told readers to keep the @v0.2.0 pin while every command
  around it used v0.2.1.