Original prompt
Write a complete, playable single-file HTML document implementing a 3D Asteroids game using three.js (loaded from the local 'three.min.js' provided next to the HTML - reference it as <script src="three.min.js"></script>; do NOT fetch from a CDN). Create an 800x600 canvas, build a 3D scene with a PerspectiveCamera, a player ship mesh, and several asteroid meshes of varying size that drift across the play area. The ship moves with thrust and momentum (inertia) controlled by arrow/WASD keys and can fire projectiles with SPACE. Asteroids break into smaller pieces when hit and can collide with the ship. Use requestAnimationFrame for the game loop. Show a live score HUD via HTML/DOM overlay. Include Start and Game Over states with a Restart button, and a high-score table persisted in localStorage (top 5 scores, loaded on startup and written on game over). Use only primitive geometries and simple materials - no external models or textures.SCORING & PERSISTENT HIGH-SCORE BOARD (REQUIRED): The game MUST award points for gameplay actions and maintain a persistent high-score table. When a run finishes, prompt the player to enter their name/initials and record it with the score. Save the top 5 scores (name + score) to a local JSON file in the working directory (e.g. high_scores.json), and also write the latest finished run as {"initials": name, "score": number} to /tmp/alpaca_score.json (overwrite it every run) so the arcade scoreboard can pick it up automatically, load and display them on startup and on the game-over screen, and write a new entry whenever a run finishes. Scores must survive restarting the program. Every new game MUST start with the score reset to 0 - never carry over the previous game's score into the next session. Every new game MUST start with the score reset to 0 - never carry over the previous game's score into the next session. SUCCESS CRITERIA: the page must (1) render a genuine 3D scene with visible depth, (2) implement real physics (thrust/momentum, projectile hits, asteroid splitting), (3) run an interactive game loop with a Score HUD, (4) persist a top-5 high-score table with name entry, and (5) auto-start gameplay without any user gesture so the headless renderer captures a non-blank 3D frame. OUTPUT FORMAT: Respond with the COMPLETE, self-contained HTML document in ONE single ```html code block. Do NOT split the code across multiple blocks, do NOT include a thinking summary inside the block, and do NOT place any prose, explanation, or comments between the opening and closing of the code block. The entire document (doctype through </html>) must be inside one fenced code block so it can be extracted and rendered verbatim. OUTPUT REQUIREMENT: Respond with ONLY the raw, runnable source code in a single fenced code block, with the first line starting at column 0 (no leading indentation). Do not include any thinking, explanation, summary, or prose before or after the code, and keep comments inside the code minimal.