Update to CrumbPass

{
  "description": "Safely performs bulk CrumbPass restaurant menu price and availability changes. Use when an owner asks to increase or decrease prices across a category or set of dishes, or mark multiple dishes available or unavailable.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 221
    }
  ],
  "name": "bulk-operations",
  "skill_md_contents": "---\r\nname: bulk-operations\r\ndescription: Safely performs bulk CrumbPass restaurant menu price and availability changes. Use when an owner asks to increase or decrease prices across a category or set of dishes, or mark multiple dishes available or unavailable.\r\n---\r\n\r\n# Bulk operations\r\n\r\n1. Read `get_menu` first. Match the owner's request to exact category and dish names; clarify any ambiguity.\r\n2. For price changes, call `adjust_menu_prices` without `confirm`. It returns every affected old and new price without changing the menu.\r\n3. Present the full change list and currency to the owner. Ask for explicit approval.\r\n4. Re-call `adjust_menu_prices` with exactly the approved targeting and `confirm: true`.\r\n5. For availability changes, state the exact dishes affected from `get_menu`, obtain explicit approval, then call `set_menu_availability` with `confirm: true`.\r\n\r\n## Guardrails\r\n\r\n- Do not silently round prices; explain the requested rounding rule before applying it.\r\n- Do not use an empty category or guessed dish name.\r\n- If the owner asks to change “everything,” show the scope and ask them to confirm the full list first.\r\n"
}