Import Format

Generate a travel itinerary in the following exact markdown format for the Dockety trip planner app:

```
# Trip Name (e.g., "Paris 2026")
**Timezone**: Timezone/Identifier (e.g., "Europe/Paris")

## Day 1: YYYY-MM-DD — Short Description
**Timezone**: Timezone/Identifier (only if different from trip default)

- HH:MM | Activity Title
  **Type**: sightseeing / museum / food / outdoors / tour / shopping / entertainment / transport / lodging / errand
  **Address**: Full address
  **Description**: Brief description
  **Commitment**: must do / planned / flexible / if time
  **Reservation**: required / optional / not needed / booked
  **Reservation URL**: https://reservation-url.com
  **Notes**: Any additional notes

- HH:MM-HH:MM | Activity With End Time
  **Address**: Full address

- HH:MM | Next Activity Title
  **Address**: Full address

## Day 2: YYYY-MM-DD — Short Description

- HH:MM | Activity Title
  **Address**: Full address
```

Rules:
- The H1 (#) line is the trip name
- **Timezone** after H1 is optional trip metadata
- Each day starts with ## Day N: YYYY-MM-DD (the date is required, description after the dash is optional)
- Each activity starts with "- HH:MM | Title" (use 24-hour time, or "- Title" if no specific time). Optionally include an end time: "- HH:MM-HH:MM | Title"
- Activity metadata lines are indented with 2+ spaces under the activity
- Only **Address** and **Description** are commonly needed; other fields are optional
- **Type** — assign one per activity: sightseeing (landmarks, viewpoints), museum (museums, galleries), food (restaurants, cafes, bars), outdoors (parks, beaches, hikes, strolls), tour (guided tours, cruises, excursions), shopping (stores, markets), transport (flights, trains, car, walking between locations), lodging (check-in/out), errand (laundry, packing, admin)
- **Commitment** defaults to "doing this" if omitted. Use "maybe" for activities that might be skipped depending on energy/time/weather
- **Reservation** — ONLY include this line when relevant:
  - "booked" = already purchased/reserved (hotels, pre-booked tours, confirmed reservations)
  - "required" = needs to be reserved before the trip (museum tickets, tours requiring advance reservation)
  - "optional" = can pay at the door or reserve optionally (attractions with on-site ticket counters)
  - OMIT the **Reservation** line entirely for activities that don't need reservations: walks, beaches, parks, strolls, free landmarks, meals at casual restaurants, bars, etc. It defaults to "not needed"
- Keep descriptions concise (one line)
- Use simple ASCII characters. Use -> instead of arrows. Use - instead of em dashes in descriptions
- Output ONLY the raw markdown. No preamble, commentary, or explanation before or after. Do not wrap in ``` code fences. The output will be pasted directly into an import tool
- IMPORTANT: Do NOT assume or invent details. If you don't know a specific address, time, or detail, ask the user to confirm before including it. Use placeholder text like "TBD" rather than guessing. Accuracy matters more than completeness — the user will be relying on this itinerary while traveling
- If the user provides an existing itinerary to modify, preserve all original details (addresses, times, notes, reservation URLs) unless the user specifically asks to change them