Status

Current qualified release

v0.3.0 — support is qualified for exact combinations, not platform families. Historical qualification does not transfer; a build from main carries no qualification.

Claim	Current
Qualified release	v0.3.0, immutable GitHub Latest
Signed qualification candidate	`v0.3.0-prealpha.3`; independently qualified, runtime-equivalent
Stable hosts	Debian 13 (trixie) x86-64 · macOS 26.6.1 arm64 (`Mac14,3`)
Stable client	Chrome `152.0.7977.75` on Android 17 (Pixel 10 Pro)
Remote path	Tailscale Serve over tailnet HTTPS, TUN-mode client, Funnel disabled
OMP baseline	Exact patched `v18.1.14`, Bun `1.4.0`; stock OMP is insufficient
Rollback predecessor	`v0.2.1`, with its separately activated exact patched OMP `v17.4.1`

Known limits — part of the claim

TUN mode is mandatory. With userspace-networking tailscaled every tailnet peer arrives as a loopback peer, and the gateway fails closed rather than believing an identity header.
Never enable Tailscale Funnel. There is no supported public-Internet path.
Android radio transitions can wedge Chrome's process-wide network stack while Android stays healthy; the PWA retries and, after 45 s of visible failure, opens force-stop/reopen help.
Background Web Push is implemented and capability-free but outside the stable core claim.
Windows passes source acceptance but is not advertised until exact signed artifacts repeat the lane.
Untrusted local accounts are out of scope: a direct loopback caller can forge non-cryptographic identity headers on a shared shell host.
Portal Tunnel and self-hosted or proxied relays are unsupported; the gateway keeps OMP's existing end-to-end-encrypted relay.

Machine-readable truth: stable release lock · upstream lock · compatibility matrix · release ledger (authoritative where they disagree)

Stable v0.3.0 approved 2026-09-09; OMP v18.1.14 baseline observed 2026-09-08.