# Release verification stops at the adapter boundary

Status: accepted (2026-07-14)

omp-spt uses layered verification: deterministic extension, manifest, session, digest/history, and daemon-role tests run on every change; a release additionally requires a real native OMP endpoint proving fresh bringup, attachable TUI, same-node inbound delivery with an explicit outbound reply, local-only ordinary assistant output, busy/idle state, native resume, blocked in-TUI switching, graceful shutdown, and ReadyAgent/LiveAgent behavior. Cross-node messaging is not an adapter release gate: once the adapter has handed the same message contract to spt-core and same-node delivery works, subnet transport is entirely spt-core’s responsibility and exposes no additional harness seam.