Status

v0.7.3 client repin

v0.7.3 is the current public release. v0.7.3 advances the pinned client to OMP 18.2.3 for the two eligible GPU routes below. RTX 5090 and RTX 4090 runtime image/package bytes, model, serving settings and host-memory floors remain those of v0.7.2. Runtime measurements are carried evidence, not fresh throughput.

Lane	Form	Context ceiling	Notes
RTX 5090	Windows 11 + Docker Desktop/WSL2 Linux container	131,072	Durable container; vision available
RTX 4090	Native Windows 11 service	131,072	MTP3 profile; DirectStorage checkpoints; text-only

RTX 3090 is deferred for v0.7.3. Its separately linked historical v0.7.2 route remains on OMP 18.0.9, not qualified with the new client. New-client qualification waits for its host’s return.

Fresh client and documented-route acceptance

The published macOS arm64, Windows x64 and Linux x64 clients all passed live inference; all three provider-free hosted qualifications are public. The Linux live run used Ubuntu under WSL2, not a separately qualified non-WSL Linux OS or a managed-install readiness claim from diagnostics.

24 documented steps passed: RTX 5090 host 2, macOS client 10, Windows client 5, and RTX 4090 native 7, on frozen product source 096c8b88. Pre-cut substitutions are recorded and all hosts were restored. Documented routes · Client qualification.

The authority now uses the client’s existing durable-checkpoint capability rather than the rejected process-restart-continuation name; this vocabulary fix adds no runtime behavior.

Known caveats

One active request per lane (max concurrency 1); not a serving farm.
Carried v0.7.2 evidence: both target 126K-token RTX 5090 sessions resumed in 5.96 s and 23.57 s. The combined probe process also reported three unsaved predecessor sessions at shutdown, and a separate control lost warm reuse on 2 of 8 continuations/forks. This is not universal durability or warm reuse; automatic checkpoints remain best effort. Exact-source evidence and limits.
Host/NAS replicas are supported; restore requires the same binary, artifact, profile, and session credentials. Transport is not cross-GPU migration or automatic failover. Evidence and limits.
Use the exact Oh My Pi client pinned by the release manifest; do not run omp update over a lane install.

Machine-readable truth: v0.7.3 manifest · compatibility · release lifecycle

Updated 2026-09-18: fresh OMP 18.2.3 client/route acceptance; carried v0.7.2 runtime qualification.