🏰 Tower Defense — model shootout

D-1  loop-watchdog rollback desynced the QSA indexer ("pos 2864 but 2932 ingested") → 500
D-2  speculative verify + QSA active at 2051 tokens → error laundered into finish_reason="stop"
D-3  prompts > 8192 tokens refused twice (PLE cap off by one vs the 8193 chunk; 65536-slot n-gram row cache)
D-4  continuation prefill chunks faulted CUDA_ERROR_MISALIGNED_ADDRESS; engine lingered with a dead context
D-5  ATLAS_QSA_MAX_TOKENS default 32768 aborted decode mid-stream

Branch assist/flashnext-longform-fixes (7 commits on 4df6e609):
  ple: derive the n-gram row cache from the serve config; clamp ATLAS_PLE_MAX_TOKENS up          (D-3)
  qsa: size the indexer from --max-seq-len instead of a fixed 32768                               (D-5)
  scheduler: report engine aborts as finish_reason "error"; log cuBLASLt fallbacks                (D-2b)
  scheduler: stop the loop once a GPU fault is latched                                             (D-4 aftermath)
  rollback: rewind QSA/PLE aux state with the SSM state, or decline                                (D-1; restore path works, cursor 1 token behind — open)
  scheduler: latch MTP off before a sequence can cross the QSA inert bound                        (D-2a)
  mhc: align the prefill GEMM scratch sub-buffers; odd slabs faulted the GEMM                     (D-4 root cause)

D-4 root cause: hc_pre_gemm packed its BF16 scratch as raw byte products; inj_pre is lay*8 bytes, so an ODD
prefill chunk (1,117 tokens, or the default 8,193) put up_wt 8 bytes off a 16-byte boundary and the tensor-core
GEMM faulted. Found with CUDA_LAUNCH_BLOCKING=1 (compute-sanitizer was ~100x too slow to reach the chunk).
Verified: the failing 13,397-token prompt prefills at 4,096 and 8,192 chunking; ATLAS2 ran end to end with defaults.

Build a complete, polished single-file HTML5 tower-defense game (index.html: all CSS and JS inline, canvas-based, no external assets or libraries). Requirements:
- 20x12 grid map with a fixed winding enemy path (visually distinct road) and buildable cells
- 3 tower types: Gun (fast, single-target), Cannon (slow, splash AoE), Frost (slows enemies). Each has cost, range, and 2 upgrade levels (better damage/range/fire-rate). Towers can be sold for 70% of invested cost.
- Enemies: normal, fast, tank; a boss every 5th wave. Health bars above enemies. HP/speed/count scale each wave.
- Economy: start with 100 gold and 20 lives; kill bounties; wave-completion bonus; a leaked enemy costs 1 life (boss costs 5).
- UI: top bar (gold, lives, wave, score); tower shop panel with prices; click a shop tower then click the map to place (show range preview and valid/invalid cell highlight); click a placed tower to select it and show upgrade/sell panel; Start Wave button plus auto-start toggle; game speed x1/x2 button.
- Targeting: enemies closest to the exit first. Render projectiles. Show splash radius on cannon impact and a frost visual on slowed enemies.
- Win after beating wave 20; lose at 0 lives. Proper end screens with a Restart button.
- Polish: hover states, particle effects on kills, hit flashes, clean modern dark theme.
Output the COMPLETE index.html in one ```html code block. No placeholders, no TODOs — fully working code only.

Below is your current index.html for the tower-defense game. 1) Review it for bugs: logic errors, undefined variables, broken event handlers, targeting/pathing mistakes, economy bugs, rendering issues — fix them all. 2) Ensure every item of the original spec is implemented: 3 tower types with 2 upgrade levels + sell; 4 enemy types incl. boss every 5th wave; wave scaling; gold/lives/wave/score UI; place/select/upgrade/sell interactions with range preview; start-wave + auto-start + speed toggle; closest-to-exit targeting; projectiles + splash + frost visuals; win at wave 20 / lose at 0 lives with restart; particles and polish. 3) Balance: tune costs, bounties and wave scaling so waves 1-20 are beatable but challenging. 4) Polish: particles, hit flashes, nicer end screens. If the file below is cut off mid-code, complete it properly. Output the COMPLETE final index.html in one ```html code block.

Current file:
```html
{FILE}
```

Your single-file HTML5 tower-defense game below fails to load. The browser console shows this error:

    Uncaught SyntaxError: Unexpected token ')'

Find and fix the error. Also scan the whole file for any other syntax mistakes (unbalanced brackets/parentheses, broken statements) that would prevent it from running. Do not redesign anything — make the minimal corrections needed so the game runs. Output the COMPLETE fixed index.html in one ```html code block.

Current file:
```html
{FILE}
```

Sampling: temperature 0.7, top_p 0.8, max_tokens 26,624 per round, thinking disabled
(chat_template_kwargs: enable_thinking=false — mandatory: with thinking on, models burned
the entire budget reasoning; prod produced 52K chars of thought and zero code).

Protocol: each config got the same Round-1 build prompt, then Round 2 received its own
full file back for review/fix/balance/polish. The harness extracted the single ```html
block from each response; the last complete file became the published game.

Config A shipped with `flashColor='#ff4d9d');` — one stray parenthesis that killed the
whole game on load. Given only its file plus the console error, it regenerated all 50 KB
byte-identical except that character. Verified with node --check before republishing.

Serving: prod runs live on spark:8000; Flash-Next configs run on :8001 with prod stopped
(128 GB unified memory is one pool — CPU offload frees nothing while another model is
resident). Publishing: spark → orange ~/sites/bench → orange Caddy (handle_path /bench*)
→ wg umbilical → edge Caddy (TLS) → you.

Speed note: prod got FASTER on this task than on short prompts (49 vs 38.6 tok/s) —
long uninterrupted code generation is ideal for DFlash2 speculative decoding. Flash-Next
slowed as context grew (24.6 → 19.4 tok/s).