Refresh Restaurants

• New restaurants opened in the last 1-2 years (especially in new lands or resort renovations)
• Permanently closed restaurants (remove from YAML)
• Renamed or relocated restaurants
• Stale booking/menu URLs — Disney periodically restructures their URL patterns

3. Verify URL patterns

For a sample of restaurants (5-10), verify the menuUrl and bookingUrl patterns are still valid:

• Menu URLs follow: https://www.disneyworld.co.uk/dining/[park-slug]/[restaurant-slug]/menus/
• Booking URLs follow: https://www.disneyworld.co.uk/dine-res/restaurant/[short-code]

4. Report findings

Present a structured summary:

TOTAL IN YAML: X restaurants

NEW (not in YAML — should add):
- Restaurant Name — Park/Area — style (table service / quick service / bar)

POSSIBLY CLOSED (verify before removing):
- Restaurant Name — [evidence of closure]

RENAMED:
- Old Name → New Name

URL PATTERN ISSUES:
- Restaurant Name — issue description

MISSING DATA (no description, no tags, etc.):
- Restaurant Name — what's missing

NO CHANGES NEEDED:
- [Areas that look complete and current]

5. Propose new entries

For each new restaurant to add, use this YAML shape:

"Restaurant Name":
  park: "Magic Kingdom | EPCOT | Disney's Hollywood Studios | Disney's Animal Kingdom | Disney Springs | Resort"
  menuUrl: "https://www.disneyworld.co.uk/dining/[park]/[slug]/menus/"
  bookingUrl: "https://www.disneyworld.co.uk/dine-res/restaurant/[code]"
  heroImage: ""
  description: "One sentence description matching the style of existing entries"
  tags: [tag1, tag2, tag3, ...]

Tags should include: service type (table service/quick service/buffet/bar), cuisine, meal periods (breakfast/lunch/dinner), atmosphere descriptors, and relevant franchise if applicable.

6. Apply changes immediately

Do not ask for confirmation. Apply all changes directly to src/data/yaml/restaurants.yaml:

• Add new restaurants in alphabetical order within their park group
• Delete permanently closed restaurants
• Rename entries by updating the key and description
• Fix stale menuUrl and bookingUrl values
• Fill in any missing description or tags fields on existing entries

Then run:

/opt/homebrew/bin/node node_modules/.bin/vite build

Update INTENT.md with a summary of what changed and why, then commit and push.