Same task. Four agents. May the leanest win.

Build a living coral-reef aquarium on HTML5 canvas: at least THREE visually distinct fish species (different silhouettes, sizes and colors, drawn with code — bodies, tails, fins, eyes), where at least one species swims as a SCHOOL with flocking behavior (separation + alignment + cohesion) while others cruise independently and turn around believably at the glass. Add swaying kelp, rising wobbling bubbles, animated godrays from the surface, a sandy floor with a crab that scuttles by occasionally, and coral silhouettes. Include a "Feed" button that drops food flakes which nearby fish turn to chase, and a day/night lighting toggle with a smooth transition. requestAnimationFrame, fills the window, resizes correctly. Requirements that override everything else: write a SINGLE file named exactly `index.html` in the current working directory and create NO other files. The file must be fully self-contained — no external images, fonts, stylesheets, scripts, fetches, or network requests of any kind. Do not ask questions and do not explain the code afterwards; when the file is written you are done.

Build a night fireworks show over a bay on HTML5 canvas: rockets launch with glowing trails and explode into at least FOUR distinct burst types (peony sphere, drooping willow, ring, and crackling glitter) using real particle physics — gravity, drag, and fade-out. Below, dark water REFLECTS the bursts (blurred and dimmed); behind, a city skyline silhouette with tiny lit windows and a starfield. The show runs automatically with varied timing and builds to a dense multi-launch FINALE roughly every 20 seconds. Clicking anywhere launches a rocket that bursts at the click point, and an intensity slider (1-10) scales the launch rate. requestAnimationFrame, fills the window, resizes correctly. Requirements that override everything else: write a SINGLE file named exactly `index.html` in the current working directory and create NO other files. The file must be fully self-contained — no external images, fonts, stylesheets, scripts, fetches, or network requests of any kind. Do not ask questions and do not explain the code afterwards; when the file is written you are done.

Build an animated clockwork orrery (a mechanical model of the solar system) in a brass-and-mahogany steampunk style, drawn entirely with code (SVG or canvas): at least SIX interlocking gears with visible drawn teeth where MESHING gears counter-rotate at speeds inversely proportional to their tooth counts, articulated brass arms carrying at least four planets (plus one moon) around a golden sun, a swinging pendulum, and an engraved base plate with rivets and ornamental flourishes. Include a speed control (slider or crank, 0.2x-5x) and a pause/resume control. Smooth animation via requestAnimationFrame or SMIL; fills the window; resizes correctly. Requirements that override everything else: write a SINGLE file named exactly `index.html` in the current working directory and create NO other files. The file must be fully self-contained — no external images, fonts, stylesheets, scripts, fetches, or network requests of any kind. Do not ask questions and do not explain the code afterwards; when the file is written you are done.

Build a playable retro hardware-style synthesizer: a clickable on-screen piano keyboard spanning at least TWO octaves (white and black keys, also playable from the computer keyboard with a visible key map), voice controls (waveform selector across sine/square/sawtooth/triangle, attack and release envelope sliders, a filter cutoff slider, master volume), and a 16-step drum sequencer with at least kick, snare and hi-hat rows — all sound synthesized with WebAudio, no audio files. Include play/stop transport with a tempo slider (60-180 BPM), a live oscilloscope or spectrum visualizer on canvas driven by an AnalyserNode, and a lovingly styled hardware-panel look (wood side panels, brushed metal, LED step indicators). Pressed keys and the running step must light up. Requirements that override everything else: write a SINGLE file named exactly `index.html` in the current working directory and create NO other files. The file must be fully self-contained — no external images, fonts, stylesheets, scripts, fetches, or network requests of any kind. Do not ask questions and do not explain the code afterwards; when the file is written you are done.

Build a polished neon-arcade Breakout game on HTML5 canvas: a paddle controlled by BOTH mouse movement and left/right arrow keys, a glowing ball whose bounce angle depends on where it strikes the paddle, and at least SIX rows of bricks with per-row neon colors where the top rows take two hits (with a visible damage state). Add particle debris when bricks shatter, a subtle screen shake on impacts, a trailing glow on the ball, a HUD with score, lives (3) and level, falling powerups (wider paddle and multiball), and win/game-over screens with a restart control. The ball launches from the paddle on click or Space; before launch the scene must already be alive (ball riding the paddle, bricks pulsing). requestAnimationFrame, fills the window, resizes correctly. Requirements that override everything else: write a SINGLE file named exactly `index.html` in the current working directory and create NO other files. The file must be fully self-contained — no external images, fonts, stylesheets, scripts, fetches, or network requests of any kind. Do not ask questions and do not explain the code afterwards; when the file is written you are done.

The current directory contains `sales.csv` — six months of 2025 order data for the fictional gadget maker "Klein & Sons" with columns order_id,month,product,region,units,unit_price_eur. INSPECT THE FILE and build a beautiful self-contained dashboard (index.html) that presents YOUR analysis of it: (1) a KPI row showing total revenue in euros, the best-selling product by revenue, the strongest region by revenue, and the best month by revenue — these numbers MUST be computed from the actual file, and the revenue total shown as an exact integer; (2) a revenue-by-month chart; (3) a revenue-by-product breakdown; (4) one insight you found interesting, stated in one sentence. Embed the aggregated data inline (hand-built SVG or canvas charts, no libraries). Leave `sales.csv` untouched; write only `index.html` and create no other files. The file must be fully self-contained with no network requests. Do not ask questions; when the file is written you are done.

The current directory contains `access.log` — one day of Apache-style access logs (30 Jun 2026) for the fictional SaaS "Meridian Outfitters". Something bad happened that night. PARSE THE FILE and build a beautiful self-contained incident-report dashboard (index.html) presenting YOUR forensic findings: (1) a KPI row with the total number of requests in the log, the attacker IP address (the source of the failed logins), the EXACT count of failed (HTTP 401) POST /api/login attempts, and the hour (UTC) the attack happened; (2) a requests-per-hour timeline chart that makes the attack window visually obvious; (3) a short reconstructed timeline of the attacker's behavior including what they did BEFORE the burst; (4) one recommended mitigation, stated in a sentence. All numbers MUST be computed from the actual file. Hand-built SVG or canvas charts only, no libraries. Leave `access.log` untouched; write only `index.html` and create no other files. The file must be fully self-contained with no network requests. Do not ask questions; when the file is written you are done.

The current directory contains `index.html` — a small "Orbital Lander" canvas game that is BROKEN: it never boots and has several distinct bugs. Debug and FIX IT IN PLACE so the game fully works: the scene renders and animates, Start/Reset works, holding SPACE fires the thruster, gravity pulls the lander down, and landing gently on the green pad wins while crashing shows the crash message. Do NOT rewrite the game from scratch and do NOT restructure working code — find the bugs and repair them, keeping the existing functions, IDs and the ZV-RESCUE-BASE marker comment exactly where they are. You may fix small cosmetic defects you notice. Keep it one self-contained file, create no other files, no network requests. Do not ask questions; when the game works you are done.

The current directory contains `index.html` — the "Meridian Ledger" FY2025 finance dashboard. It is BROKEN: it renders nothing, and even once it renders, several of its computed figures are WRONG (they disagree with the LEDGER data in the file and with each other). Debug and FIX IT IN PLACE so the page renders and every KPI, chart bar and table row is arithmetically correct and mutually consistent. Do NOT rewrite the page and do NOT restructure working code — find the bugs and repair them, keeping the existing functions, IDs, styling and the ZV-LEDGER-BASE marker comment exactly where they are. Keep it one self-contained file, create no other files, no network requests. Do not ask questions; when the dashboard is correct you are done.