Supported environments

The current web shell needs WebGPU to start. Use HTTPS, or a local development server on localhost, and a browser that can create a WebGPU adapter and device. If that check fails, Lolly explains the requirement before opening a tool.

The web-only release approved on 9 October 2026 uses the completed Mac browser checks below. These are results on macOS 27, Apple M4, with the browser's default adapter and graphics settings. They do not establish support for the same browsers on Windows, Linux, Android, iOS, Intel Macs or other GPUs.

Qualification results

The browser corpus checks numerical results on the main thread and in a worker, photo baking, cancellation, device recovery and operation chains. Its browser startup measurement covers the device service and tool mount fence, rather than the complete gallery. The Mac qualification app also checked actual gallery startup, a mounted tool, its embedded content and Content Security Policy. These checks do not certify every presentation clicker, embedded website or native platform.

Release scope

Web artifacts can use the qualified browser rows without waiting for the packaged apps. The signed web build, public web image and verified instance shell select that scope explicitly. This approval leaves native releases held, including the Mac package, until the full required matrix is published.

For a web artifact, run:

node scripts/webgpu-release-gate.ts --scope web
pnpm run check:release-checklist
pnpm run build:web:release

The signed build still requires the matching catalog signing key and public pin. Qualification alone does not publish a build or deploy an instance.

node scripts/webgpu-release-gate.ts and pnpm run check:release keep the full frontend gate. Tauri builds, native package workflows and the YunoHost release command also keep that hold. A pending or missing result cannot pass the gate; environment variables cannot bypass qualification. A tested unsupported result may be recorded as Not supported, but an unrun check stays Pending.

The MCP, certificate service, Penpot service and documentation builds are independent of this frontend matrix. Their release checks continue separately.

Recorded evidence

The Chrome run used source commit 20843cb22d3ad36dfd3d93e518bfd8ee812527a7. The Firefox, Safari and Edge runs used 26799926739fa58bbbf6a8e081f13ab5a8f74617; the required browser corpus and launcher inputs are unchanged between those commits. The Mac qualification app was built from ed6c32571593dba96b0562b47396ff42e2cf3270; its passed execution is not a new current-main build or a fresh-profile startup result. Original failed attempts remain recorded separately.

Retained conformance reports have these SHA-256 digests:

For installation choices, see Install Lolly. For signed artifact production, see the Build Guide.