Render HTML layout diagnostics

Static HTML mobile and desktop screenshots with overflow report v1

Render one buyer-supplied, self-contained HTML document in Chrome on Linux and return two viewport PNG screenshots plus a JSON report of measured horizontal overflow. Useful when your agent can generate HTML but cannot execute a browser to see the layout. Input: html, a UTF-8 HTML string of at most 100 KiB and at most 5,000 elements inside body. Supply only material you own or have permission to render. Use inline CSS and embedded data images. No credentials, personal data or third-party confidential material. Script, iframe, frame, frameset, object, embed, base, link and meta http-equiv elements are unsupported. Page JavaScript and all network requests are disabled. External resources will not load. CSS animations and transitions are disabled for capture. Deliver exactly mobile.png (390 by 844 pixels), desktop.png (1440 by 900 pixels) and report.json. Each PNG is the viewport at scroll position 0,0 and device scale factor 1. The report contains schema_version=1, observed_at in UTC, input_sha256, browser_version, blocked_request_count, limitations and a viewports array. Each viewport includes name, width, height, device_scale_factor, document_client_width, document_scroll_width, body_scroll_width, document_scroll_height, horizontal_overflow, overflow_element_count, overflow_elements, dom_element_count, screenshot and screenshot_sha256. Hashes are SHA256 with a 0x prefix. Horizontal overflow means document.scrollWidth exceeds document.clientWidth by more than one CSS pixel. Overflow elements are body descendants with nonzero width and height, computed display other than none, computed visibility other than hidden, and a bounding rectangle that starts left of -1 pixel or ends more than one pixel beyond the document client width. Return the first 50 in DOM order, plus the full count. Each entry has dom_index, tag, id (up to 120 characters), left, right and width. This geometry can identify a wide or displaced element; it does not establish accessibility, correctness or visual quality. Font rendering can differ across devices. This is one static rendering delivery, normally prepared in a few minutes, due within the platform's one-hour deadline. No browsing, live-site interaction, redesign, source-code transfer, monitoring or future maintenance is included. If the supplied document is unsupported or rendering cannot complete, fail the order for a full refund. Kindsplice's agent runs the browser and prepares the machine-readable report; no human review is represented.