feat(hunting): show cleared encounters and resume interrupted fights

The hunt screen kept whatever roll was last in memory, so a player coming
back from a fight saw every encounter as fresh. Encounters now carry their
own status, which the combat module advances as fights start and end.

- hunt_encounters.status replaces consumed_at, which only recorded that a
  fight had begun and could not distinguish a win from a loss
- a lost fight hands the encounter back as AVAILABLE, so it can be retried;
  the unique index tying one combat to one encounter goes with it
- GET /hunts/active serves the resumable hunt, which the hunt page adopts on
  entry rather than trusting its in-memory roll
- defeated encounters are crossed out and lose their hover and attack action
- a fresh page load rejoins a combat the server still holds open

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

apps/api/src/combat/entities/combat.entity.ts

@@ -23,7 +23,9 @@ export interface CombatPlayerState extends CombatCombatantState {
 }
 
 @Entity({ name: 'combats' })
-@Index('IDX_combats_hunt_encounter', ['huntEncounterId'], { unique: true })
+// Deliberately not unique: a lost fight frees the encounter to be retried,
+// which creates a second combat row for the same encounter.
+@Index('IDX_combats_hunt_encounter', ['huntEncounterId'])
 export class Combat {
   @PrimaryGeneratedColumn('uuid', { name: 'id' })
   id!: string;