# Lumina Resorts Conflict Report

Status: **NEEDS REVIEW BEFORE PRODUCTION NEXT IMPLEMENTATION**

## Checks completed

- Stitch MCP access: PASS
- Screen list: PASS — 15 screens
- HTML/code extraction: PASS — 15/15 saved
- Placeholder scan: PASS — no `{{DATA:*}}` placeholders found in extracted HTML
- Initial route pairing: PASS with assumptions documented in `route-map.md`

## Potential conflicts / decisions needed

1. **Multiple UI kit/design-system screens**
   - `895fbd55ca5645d7b1985bfaddf10013` — `Lumina Resorts | UI Kit & Design System`
   - `ee8b136b214b4e7e9c310972ab9b624c` — `Lumina Resorts | Master UI Kit`
   - `26ab4811cfcb48438546e7a213d6af39` — `Lumina Resorts - Mobile UI Kit`
   - Decision: treat all as design-system reference only, not public pages, unless user says otherwise.

2. **Mobile/desktop classification is inferred from exported HTML titles/content**
   - Stitch direct resource returned screen IDs without human labels.
   - Pairing in `route-map.md` is based on page titles/H1/H2 and mobile-like markup.
   - Decision needed: approve the proposed route map or correct any pairing.

3. **Footer/nav wording differs in case/style across pages**
   - Some pages use uppercase footer links, some normal title case.
   - Recommendation: production Next should use one shared header/footer based on the UI kit + desktop canonical nav: Rooms / Location / Gallery / Facilities / Contact.

4. **Demo hotel content**
   - Current phase says `use Stitch content for now`; production static copy/images should therefore preserve Lumina demo content initially.
   - CMS/content replacement is deferred to later phase.

## Recommendation

Proceed only to raw reference publication now. For production Next implementation, first approve:

- Route map in `route-map.md`
- Shared header/footer behavior
- UI-kit screens as reference-only
- Demo content remains for static first pass