Animate a print shop's printers stacking finished sheets in one self-contained HTML file

# Animate a print shop's printers stacking finished sheets in one self-contained HTML file Make a small animated scene: a print shop printer sheet stack. 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): `{printers: [{name, x, sheets_out, status: "queued" | "printing" | "done"}, ...]} (canvas px, y down; one entry per spec.json printer; x = the printer's centre; sheets_out = the whole number of finished sheets on its output stack)`. Extra fields are fine. It must describe what is actually drawn. - Time 0 is `performance.now()` 0 (seconds = `performance.now()` / 1000). Each printer has no finished sheets until its own `start_s`; after that one finished sheet lands on its output stack every `sec_per_sheet` seconds, so the first sheet lands at start_s + sec_per_sheet and sheets_out is the number of whole sheet intervals that have passed (rounded down, never rounded to the nearest), until all `sheets` are out at start_s + sheets × sec_per_sheet; the stack then stays at `sheets`. Draw each printer with its output stack growing by `sheet_px` pixels per sheet. `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. `sheet_count`: at every sample more than 0.05 s from that printer's `start_s` or from any moment a sheet lands, each printer's x is within 1.5 px of its spec.json `x`, and its sheets_out is exactly the whole number of finished sheets: 0 before `start_s`, then (seconds since start_s) ÷ `sec_per_sheet` rounded down, never more than `sheets`, and `sheets` once the job is done. 5. `printer_status`: at those samples each printer's `status` is queued before `start_s`, printing until all its sheets are out at start_s + sheets × sec_per_sheet, and done after that; the samples include queued, printing and done. 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.