Animate an online order's parcel moving along its delivery route with depot stops in one self-contained HTML file

# Animate an online order's parcel moving along its delivery route with depot stops in one self-contained HTML file Make a small animated scene: a parcel delivery tracker. 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): `{parcel: {x, y}, status: "in_transit" | "at <stop name>" | "delivered"} (canvas px, y down)`. Extra fields are fine. It must describe what is actually drawn. - Time 0 is `performance.now()` 0 (seconds = `performance.now()` / 1000): the parcel leaves the first stop at time 0. Leg i runs from stops[i] to stops[i + 1] at leg_speeds_px_s[i]; after legs that end at an intermediate stop it waits dwell_s[i] seconds there before leaving. It stays at the last stop once it arrives. Draw the route, the stops and the parcel. `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. `route_position`: at every sample, the parcel is within 1.5 px of its exact position on the route: straight legs between consecutive `stops` at each leg's `leg_speeds_px_s`, waiting `dwell_s` at each intermediate stop. 5. `tracking_status`: at every sample more than 0.05 s from an arrival or departure, `status` is in_transit while moving, at <stop name> while waiting at an intermediate stop, and delivered after reaching the last stop; at least one sample falls inside a stop. 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.