fix: preserve autoQuest and autoBoss settings across prestige

Resolves #51 — after a prestige the post-prestige state was built from
initialGameState which hard-codes both flags to false, so auto-quest and
auto-boss would silently turn off mid-run even if the player had them
enabled. buildPostPrestigeState now carries the live values forward so
automation preferences survive the reset.

apps/api/src/services/prestige.ts

@@ -5,6 +5,7 @@
  * @author Naomi Carrigan
  */
 /* eslint-disable max-lines-per-function -- buildPostPrestigeState requires constructing a large composite state object */
+/* eslint-disable complexity -- buildPostPrestigeState has many optional fields that each add a branch point */
 import { initialGameState } from "../data/initialState.js";
 import { defaultPrestigeUpgrades } from "../data/prestigeUpgrades.js";
 import type {
@@ -239,8 +240,17 @@ const buildPostPrestigeState = (
 
   const prestigeState: GameState = {
     ...freshState,
+
     // Achievements are permanent — earned achievements survive all prestiges
     achievements: currentState.achievements,
+
+    /*
+     * Preserve automation preferences across prestige — the player explicitly
+     * opted into these settings and would not expect them to silently reset.
+     */
+    autoBoss: currentState.autoBoss ?? false,
+
+    autoQuest:  currentState.autoQuest ?? false,
     // Boss statuses reset for gameplay, but first-kill claimed flag is preserved
     bosses:     bossesWithBountyClaimed,
     lastTickAt: Date.now(),