Animate a landscaping firm's irrigation controller running its sprinkler zones in sequence in one self-contained HTML file

# Animate a landscaping firm's irrigation controller running its sprinkler zones in sequence in one self-contained HTML file Make a small animated scene: an irrigation sprinkler sequence. Write one file, `out/scene.html`, that works opened straight from disk with no network access. `spec.json` gives the page title, the stage size and the scene parameters. **Looks are not scored**: the page is opened in a headless browser (800x600 window, UTC time zone, network blocked) and checked by objective tests only. ## Scene contract - Draw the scene on one `<canvas>` or `<svg>` stage of `width` x `height` CSS pixels (spec.json), visible on load, with `<title>` containing spec.json `title`. - Animate continuously from load (`requestAnimationFrame` or timers); no click is needed unless stated below. - Expose `window.sceneState()`, returning the scene's current state in stage pixel coordinates (origin top-left of the stage): `{zones: [{name, x, y, radius, status: "waiting" | "watering" | "done"}, ...]} (canvas px, y down; one entry per spec.json zone; x, y = the sprinkler head; radius = the spray circle's radius, 0 when not watering)`. Extra fields are fine. It must describe what is actually drawn. - Time 0 is `performance.now()` 0 (seconds = `performance.now()` / 1000). The zones run one at a time in spec.json order: zone 1 starts at `start_s` and runs for its `run_s`; each later zone starts `gap_s` after the previous zone finishes. A running zone's spray radius grows linearly from 0 to its `max_radius` over `ramp_s`, then stays at `max_radius` until the zone finishes; a zone that is waiting or done has radius 0. Draw the lawn, each sprinkler head and its spray. `sceneState()` must return the state at the moment it is called. - The page must log no errors and throw no exceptions. Keep the file at most 200,000 bytes; no external scripts, fonts, images or URLs (inline everything). ## Checks (partial credit = share passed) 1. `self_contained`: `out/scene.html` exists, is at most 200,000 bytes, references no http(s) or protocol-relative URL, and requests nothing from the network when opened. 2. `has_canvas_or_svg`: a visible `<canvas>` or `<svg>` of at least 300x200 CSS pixels is on the page. 3. `frames_change`: over 3 s, some later screenshot differs from the first in at least 0.1% of pixels, and at least 3 of 30 screenshots differ. 4. `spray_radius`: at every sample more than 0.05 s from a zone starting, finishing or reaching full spray, each zone's sprinkler is within 1.5 px of its spec.json `x`, `y` and its radius is within 1.5 px of the exact value: 0 while waiting or done, growing linearly from 0 to `max_radius` over `ramp_s` after the zone starts, then `max_radius` until it finishes. 5. `zone_status`: at those samples each zone's `status` is waiting before it starts, watering for its `run_s`, then done; zone 1 starts at `start_s` and each later zone starts `gap_s` after the previous one finishes; the samples include all three statuses. 6. `no_console_errors`: no uncaught exception, `console.error` or browser error is logged during the run. ## How this run works - Work on your own: nobody will answer questions in this task, and writing to `ask/` counts against the run. - Write only under `out/`. Create `out/` if it is missing. Inputs are synthetic; don't fetch anything from the network. - Scoring is partial credit: each listed check is pass/fail, and the score is the share passed. Numbers are compared to within 0.005 unless the task says otherwise.