# Release custody — omp-spt v0.3.21

**Release:** https://github.com/BigscreenVR/omp-spt/releases/tag/v0.3.21 · stable / `latest` ·
`prerelease: false`
**Promoted:** 2026-07-23 by explicit operator decision (see "Promotion basis" below).
**Driver:** emphasys (omp-spt adapter maintainer endpoint).

## Source identity

| Field | Value |
|---|---|
| Manifest version | `0.3.21` (`adapter/omp-spt.toml` canonical) |
| Tag | `v0.3.21` |
| Release commit | `3c7bf80effa7f9bc35ac0ffae639de56f2af5712` |
| Fix commit | `10e2388` — *match delivery stub by identity so echo drift can't drop the body* |
| Requirement | `REQ-HAZARD-DELIVERY-BODY-INTEGRITY` (doc/impl/unit); KNOWN-HAZARD #6 |

## Artifact digests (SHA-256)

| Artifact | Digest |
|---|---|
| `adapter.spt` (hosted asset) | `2a8d26558b4c342123f80cb0e2010ded87795dc7508166193ddd34ffb89ee912` |
| `x86_64-pc-windows-msvc/omp-spt.exe` | `eda46608e2aa84e9e03a3539494c74243925daec8402d0bb33fa33903a656f05` |
| `x86_64-unknown-linux-gnu/omp-spt` | `6f4d7c3dac6337679377d40bd673ade1d08867a60b1ed6fd95a9133757eccc3f` |
| `x86_64-unknown-linux-musl/omp-spt` | `e67930b7b750899e8bdea74aea2e6447e309c9df6babf2f34c590fc8253915d2` |

Archive is reproducible (`SOURCE_DATE_EPOCH=0`). Packager self-validated exact membership,
`-rwxr-xr-x` Linux helper modes, and PE/GNU-ELF/static-musl architectures.

## Deterministic gates (all green, no release-blocking skips)

`sh tests/ci-gates.sh` · `sh ci/run-gates.sh` (RESULT: PASS, VERSION-CONSISTENCY OK: 0.3.21) ·
`node tests/omp-extension.mjs` (OMP-EXTENSION OK) · `traceable-reqs check` (exit 0). The
delivery-body fix itself is covered by three mutation-verified regression tests (echo drift,
same-peer delivery correlation, no-false-injection).

## Tagged acquisition acceptance — all three targets PASS

Each run downloaded the hosted `adapter.spt` at `v0.3.21`, verified its digest, verified the
selected target helper digest, installed via `spt adapter add --release`, and asserted exact
adapter version `0.3.21` and shared-string resolution. Runs used isolated throwaway `SPT_HOME`
(verified not to touch any live registration).

| Target | Host | spt-core | OMP | Selected helper digest | Result |
|---|---|---|---|---|---|
| `x86_64-pc-windows-msvc` | HFENDULEAM (Windows) | 0.41.0 | 17.0.5 | `eda46608…` | RELEASE-ACQUIRE-INT OK |
| `x86_64-unknown-linux-gnu` | kitsubito (Ubuntu glibc) | 0.40.0 | 17.0.1 | `6f4d7c3d…` | RELEASE-ACQUIRE-INT OK |
| `x86_64-unknown-linux-musl` | gravity-linux (musl spt 0.41.0) | 0.41.0 | 17.0.1 | `e67930b7…` | RELEASE-ACQUIRE-INT OK |

The musl record satisfies ADR-0019: gravity's musl-built spt-core **selected and installed** the
archive's musl helper (installed digest == musl member `e67930b7…`), not the GNU helper.

## Install and update paths verified

- Unpinned `spt adapter add --release BigscreenVR/omp-spt` → resolves `latest` → `0.3.21`.
- `spt adapter update omp-spt` from prior stable → `updated 0.3.20 -> 0.3.21`.

## Promotion basis — explicit operator decision

The v1 release-evidence schema (`release/evidence-v1.schema.json`) requires per-target records
with `passed: true` outcomes for fresh / resume / message-reply / lifecycle / shutdown /
ReadyAgent / LiveAgent, each bound to an attached acceptance log. Those outcomes come from the
**interactive** native-endpoint sequence (`docs/CI.md` §1–5: attached live OMP TUI, real model
turns, a LiveAgent Psyche event) and were **not** run for this release. No such logs were
fabricated.

The release operator (Brandon, BigscreenVR) made an **explicit decision to promote v0.3.21**,
accepting as the acceptance basis: the green deterministic gates, three mutation-verified
regression tests covering the exact delivery-body behavior changed by this fix, and passing
tagged-acquisition acceptance on all three supported helper targets — and waiving the full
interactive evidence-record set for this low-risk, delivery-body-only bugfix. This mirrors the
prior explicit-operator-decision precedent recorded for v0.3.4 (F-032).

**Follow-up owed:** the interactive native-endpoint acceptance (`docs/CI.md` §1–5) remains the
standing bar and should be exercised on the next release that can run it, or retroactively as
operator-signed logs, to restore full evidence-record custody.