Compatibility and evidence

Source implementation, executed tests, candidate packages and live availability answer different questions.

Semwright 1.0.0 is published from source revision 8fa191250ae68274182570c65f067f7a60f85625. Source references were checked 7 October 2026. Historical application proofs retain their original revisions.

Read each kind of evidence separately

Evidence	What it establishes
Implementation	A documented source surface exists
Executed verification	A named run exercised its own revision and environment
Candidate packaging	A package was assembled and tested for a named OS/architecture
Live availability	Your session can reach the configured operation with necessary authority
Public release	Publication has passed its separate policy and authorization gates

None of these automatically establishes the others. Documentation updates do not renew historical certificates.

Engineering state and release state

The frozen source records R16 closed and the v1 engineering line complete for staging. Residual R06/R18 physical or interactive certification remains explicitly deferred post-v1, not converted into executed PASS. Windows external MCP filesystem mounts retain the separate BLOCKED_PORTABLE_PATH_VIRTUALIZATION non-claim.

The normal release policy requires an independent security approval. The independent review is incomplete, and the frozen source honestly retains BLOCKED_PENDING_SECURITY_REVIEW. This public v1 release uses an explicit maintainer publication exception; it does not claim independent security approval.

Native packages are distinct from desktop acceptance

The public release provides six native package targets: Linux x86_64/aarch64, Windows x86_64/ARM64 and macOS arm64/x86_64. Linux also has amd64/arm64 .deb alternatives. The engineering closeout records post-merge distribution verification at 9954c1f95f68305f32f153fe5ab302441845b7ed in run 37146331051.

The final source is covered separately by native distribution run 37569829491, with eight packages and six platform certificates, and exact-candidate certification run 37569834720, with 70 successful jobs. The public manifest records package hashes, sizes and exact source identity. These engineering results do not supply the missing independent security approval.

Package installation tests do not establish physical Hyprland coverage, unlocked Windows desktop interaction, macOS TCC acceptance, signing or notarization. Read the product’s explicit platform and post-v1 matrices.

Application proofs keep their original identity

Surface	Recorded scope
Figma	Editorial Atlas uses Figma 126.5.6 at `3cd86958f70f7a8231d31e492b5505acff19dae0`: authenticated first-party driver, official Plugin API, persisted native objects, prototypes and artifact round-trip. It does not claim every call crossed the public CLI/broker route or certify every Figma surface.
Godot	Parcel Lantern uses Godot 4.7.2 at `9ecf35fd9c3d6fbcbc1f8b72b8d4734c70037ffa`: CLI, daemon, broker/policy, sandbox, Host-mediated loopback and EditorPlugin; semantic mutation, consent boundaries and clean restart.
Linux accessibility	Unknown App Challenge stays pinned to its own receipt and records unavailable capture rather than inventing a screenshot.
Other application drivers	Hosted/native evidence is scoped by the driver’s source README and original verification records. Fixtures are not blanket version or GUI coverage.

The Native SDK guide separately describes portable cooperation tests and the narrower Linux real-Host profile. Those tests do not certify all native desktop operations.

Inspect your environment

Use setup’s printed doctor command and capability discovery against your intended broker. Missing authority, runtime prerequisites or application semantics cannot be resolved by treating another environment’s certificate as permission.

Source: engineering closeout, release-readiness record, release policy, platforms and post-v1 backlog, source references checked 7 October 2026.