Animate an auto repair shop's service bays raising, holding and lowering cars on their lifts in one self-contained HTML file

# Animate an auto repair shop's service bays raising, holding and lowering cars on their lifts in one self-contained HTML file Make a small animated scene: a service-bay lift. 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): `{lifts: [{name, x, y, phase: "down" | "rising" | "raised" | "lowering"}, ...]} (canvas px, y down; one entry per spec.json bay; x, y = the car's position)`. Extra fields are fine. It must describe what is actually drawn. - Time 0 is `performance.now()` 0 (seconds = `performance.now()` / 1000). Each bay's lift stays down until its `start_s`, rises for `rise_s`, holds for `hold_s`, lowers for `rise_s` and then stays down. Draw the floor, each lift and its car. `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. `lift_heights`: at every sample more than 0.05 s from a lift changing phase, each car is within 1.5 px of its exact position: x = its bay's `x`; y = `floor_y` while down, moving linearly from `floor_y` to `top_y` over `rise_s` while rising, `top_y` while raised, and moving linearly back to `floor_y` over `rise_s` while lowering. 5. `lift_phases`: at those samples each lift's `phase` is down before `start_s`, rising for `rise_s`, raised for `hold_s`, lowering for `rise_s`, then down again; the samples include all four phases. 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.