Update to 웨딩플로우

{
  "description": "신혼여행 설문, 여행지 추천, 여행 일정, 여행 취향, 저장된 허니문 추천을 보거나 설문을 저장할 때 사용한다. Use for a WeddingFlow honeymoon survey and its saved destination or schedule. Do not use for the overall wedding budget or dress rental.",
  "included_files": [],
  "name": "honeymoon-plan",
  "skill_md_contents": "---\nname: honeymoon-plan\ndescription: 신혼여행 설문, 여행지 추천, 여행 일정, 여행 취향, 저장된 허니문 추천을 보거나 설문을 저장할 때 사용한다. Use for a WeddingFlow honeymoon survey and its saved destination or schedule. Do not use for the overall wedding budget or dress rental.\n---\n\n# WeddingFlow honeymoon survey\n\nAnswer in Korean. Saved recommendations come from the survey record returned by WeddingFlow. Do not present a destination, price, or itinerary as saved unless the tool returned it.\n\n## Tools\n\n| Intent | Tool |\n| --- | --- |\n| My surveys | `get_api_v1_honeymoon_survey` |\n| One survey | `get_api_v1_honeymoon_survey_by_survey_id` |\n| Shared survey | `get_api_v1_honeymoon_survey_open_by_survey_uuid` |\n| Save a survey | `post_api_v1_honeymoon_survey` |\n\nThe shared lookup uses `path_params.survey_uuid`. Do not guess a UUID.\n\n## What the user can set\n\nRead existing surveys before creating another one. Confirm the answers, then send only these fields in `body`:\n\n- `start_date`: `YYYY-MM-DD`\n- `nights`: integer\n- `budget`: integer won\n- `experience_or_relax`: experience-focused or rest-focused, in the user's words\n- `famous_or_unique`: famous places or unique places\n- `priority`: list of preferences such as food, shopping, rest, activities, hotel stay, scenery, short flight, culture, language, and safety\n\nDo not send `destination`, `recommend`, `schedule`, `expected_cost`, `precautions`, `end_date`, or any model-cost field. Those are produced by WeddingFlow. After a successful save, read the survey again and summarize only the fields that came back.\n\nDo not retry a failed POST. Wedding-budget totals are a different skill; mention that skill if the user wants the honeymoon line of the overall budget changed.\n\nIf authorization is required, use the host OAuth flow. Never ask for a token.\n"
}