JugoUI

## v1.0.54 "Midnight 12.0.7" (2026-06-18)

### Changed
- **Retail TOC updated to Patch 12.0.7** (`## Interface: 120007`,
  client build 12.0.7.68235). The addon is no longer marked as "outdated."
- Corrected stale `X-Version-Name` entries in all TOC files to match the
  current release name.

---

## v1.0.53 "Silent Start" (2026-06-18)

### Changed
- **Removed ESC menu button.** Any interaction with the secure `GameMenuFrame`
  (child frame, hook, anchor, skin) tainted its `callback()` and triggered
  `ADDON_ACTION_FORBIDDEN` upon logging out—an issue that could not be
  cleanly resolved across all clients.
- **Silent login chat.** No more version, bug, or warning lines when logging in.

### Added
- **JugoUI under ESC → Options → AddOns.** Dedicated entry with an
  "Open JugoUI Settings" button that launches the settings window. Uses the
  official `Settings`/`InterfaceOptions` API (taint-free). Alternatively,
  use `/jugo` as before.

---

## v1.0.52 "True to Standard" (2026-06-14)

### Changed
- **Classic/MoP/TBC now use standard Blizzard action bars.** The custom secure
  bars utilized Retail-style action paging, which maps incorrectly on these
  clients (causing items to be dragged into the wrong slots) and could not
  be reliably fixed without test access. **Retail retains the JugoUI custom bars.** A native Classic-style bar overhaul remains
  an option for a future project.

---

## v1.0.51 "Movable" (2026-06-14)

### Fixed
- **Action bars movable again via "Unlock"**: The drag overlay is now positioned
  OVER the buttons (previously, the buttons intercepted the drag input → bar immovable).
- This allows rows to be pulled apart—which also fixes the
  "spell lands in the wrong slot" issue occurring when dragging from overlapping rows
  (where a top-layer row would intercept the drop).

---

## v1.0.50 "Slot Hit" (2026-06-14)

### Fixed (Classic/MoP)
- **Custom bar buttons mapped to the wrong action slot** (drag/click registered on
  a different button—affecting all bars). Cause: buttons set
  `useparent-actionpage` but not the `action` attribute (1–12). Retail falls
  back to the button ID, whereas Classic/MoP does not. Now explicitly set.
- Action bars are assigned **distinct frame levels** so that, with overlapping rows,
  a drop clearly hits the topmost/correct button.