v1.1.1 — encounter-name label fix

Fixed

• Encounter IDs 101–105 are M9S–M12S (AAC Heavyweight, 7.3 tier), not M5S–M8S. Past PROGRESS notes had this wrong and the UI label tables in Encounters.jsx and FieldStats.jsx followed the bad naming. Corrected mapping: 101=M9S (Vamp Fatale), 102=M10S (Red Hot and Deep Blue), 103=M11S (The Tyrant), 104=M12S (Lindwurm), 105=M12S-P2 (Lindwurm II — the "true" phase-2 unlock). Bundle rebuilt; FastAPI serves the new index.html on the next browser refresh.

Data

• Backfilled M9S–M12S (101–105) + TOP (1068) + DSR (1065). M9–M12: +30 to +50 reports each (was ~30, now 60–84). TOP / DSR: 0 → 27 reports each — field data exists for the first time. Limitation: only 1 kill-with-events each on TOP/DSR; FFLogs paywalls archived report events() behind their paid /user endpoint and 2 of the top-3 rankings per ultimate hit that wall. 27 metadata-only reports are enough for prog-vs-field, not enough for fight_model (T-104 needs ≥3 kills with events).