Compatibility and evidence
This website describes revision 963f0ceecb22ccfadf66b0937524fb30a6269030, reviewed on 22 September 2026. It is a development snapshot, not a release candidate certification.
Keep three kinds of information separate
Section titled “Keep three kinds of information separate”Implementation means a source path exists. Verification means a named test ran against a specific revision and environment. Availability means your current session can reach an operation with the necessary configuration and consent. None of these automatically implies the other two.
Observed development gates
Section titled “Observed development gates”The GitHub check results for the reviewed revision were inspected. Required source, Rust x86_64/ARM64, dependency, coverage, fuzz and native integration jobs had successful conclusions. This website task did not rerun the Rust workspace.
| Surface | Evidence boundary |
|---|---|
| Chromium | A passing native Chromium gate; not every website, version or race condition. |
| LibreOffice | A passing driver gate and documented real headless Writer/Calc/PDF operations; not the entire UNO API. |
| Blender | A passing Blender 4.5.14 LTS driver gate with documented sandboxed operations and a small render; not all add-ons or GUI workflows. |
| KiCad and MLT | A passing combined gate; fake IPC or semantic fixtures do not certify real editor interoperability. |
| X11 | A passing X11 backend gate; not a complete Linux desktop matrix. |
| Other Linux routes | Read the specific backend and live-session notes; do not infer universal Wayland support. |
| Windows and macOS | Product direction; not advertised as available by this site. |
Source documents can lag behind code
Section titled “Source documents can lag behind code”Some overview documents still contain older verification statements. The website does not convert those contradictions into a blanket support label. Read the integration-specific source and the exact check results together. Driver pages summarize their limits separately.
Inspect your own environment
Section titled “Inspect your own environment”Use computerctl doctor and capability discovery against the intended broker. A runtime status is a local observation, not independent security review or proof of production readiness. Packaging, installation validation and a live application matrix remain distinct work.
Evidence: native integration run, quality run, dependencies, coverage and fuzz, and the frozen source revision.