notificationscripts/  — RECONSTRUCTED booster folder (the live jsapp copy is gone; server closed)

HOW THIS WAS BUILT
- Common files (identical across engines) taken from the MGM (booksecurereservation) backup:
    BoosterNotification.js  = latest version, 2026-07-02  (contains MGM's IDs -> update per engine)
    BoosterVisitorSessionHandlingScript.js, BoosterDemandSearchDataCaptureScript.js = shared
- BoosterScript.js (loader) = auto-generated per engine by substituting the engine folder name
    into the MGM loader template. VERIFY the paths/loader style before deploying.
- BoosterBooking.js = engine-specific. Included where we had a real backup; MISSING flagged otherwise.

PER-ENGINE STATUS
  booksecurereservation  COMPLETE (real MGM files; correct IDs already)
  leisurehotels          COMPLETE-ish (its own authentic loader/notification/booking, May 2026)
  simplotel              BoosterBooking = real Simplotel backup; rest = shared (update IDs)
  staah                  BoosterBooking = real Staah backup; rest = shared (update IDs)
  amritara / synxis / bookingwhizz   shared files only; BoosterBooking MISSING (see note in folder)

TODO for you
  1. In each engine's BoosterNotification.js: set that engine's IDs (see _UPDATE_IDS_HERE.txt).
  2. Verify each BoosterScript.js loader (path + whether it needs the getAccKey fallback like leisurehotels).
  3. Provide BoosterBooking.js for amritara/synxis/bookingwhizz (and any engines not listed here).

NOTE: this covers only engines found in backups. If jsapp had MORE booking engines, they are NOT here —
add their folders + BoosterBooking files once you have the complete engine list.