fix: adventurer unlocks not applied by force-unlock tool

The force-unlock debug route now scans completed quests for adventurer
rewards and ensures those tiers are marked as unlocked in game state.
The UI and API response type both surface the new adventurersUnlocked
count alongside existing zone/quest/boss/exploration counts.

Closes #88

apps/web/src/components/game/debugPanel.tsx

@@ -51,11 +51,15 @@ const DebugPanel = (): JSX.Element => {
       if (result.explorationUnlocked > 0) {
         parts.push(`${String(result.explorationUnlocked)} exploration area(s)`);
       }
+      if (result.adventurersUnlocked > 0) {
+        parts.push(`${String(result.adventurersUnlocked)} adventurer tier(s)`);
+      }
       const total
         = result.zonesUnlocked
         + result.questsUnlocked
         + result.bossesUnlocked
-        + result.explorationUnlocked;
+        + result.explorationUnlocked
+        + result.adventurersUnlocked;
       const message
         = parts.length === 0
           ? "Everything looks correct — no missing unlocks were found."

apps/web/src/context/gameContext.tsx

@@ -558,6 +558,7 @@ interface GameContextValue {
    * @returns Counts of what was corrected.
    */
   forceUnlocks: ()=> Promise<{
+    adventurersUnlocked: number;
     bossesUnlocked:      number;
     explorationUnlocked: number;
     questsUnlocked:      number;
@@ -2104,6 +2105,7 @@ export const GameProvider = ({
         localStorage.setItem("elysium_save_signature", data.signature);
       }
       return {
+        adventurersUnlocked: data.adventurersUnlocked,
         bossesUnlocked:      data.bossesUnlocked,
         explorationUnlocked: data.explorationUnlocked,
         questsUnlocked:      data.questsUnlocked,
@@ -2116,6 +2118,7 @@ export const GameProvider = ({
           : "Failed to force unlocks",
       );
       return {
+        adventurersUnlocked: 0,
         bossesUnlocked:      0,
         explorationUnlocked: 0,
         questsUnlocked:      0,