# Build 14 — voice playback and retained direct messages

## Scope and verification

An explicit play gesture creates/resumes an AudioContext before asynchronous
work. Encoded audio is decoded in memory; no audio is sent to another provider.
Only one decoded player is active. Visible-player DOM survives chat refreshes;
leaving the chat, locking, hiding or deleting disposes playback. Decode failures
are visible. New recordings prefer supported AAC/MP4 with Opus fallback.

The original native HTML player and actual VoiceCapture recordings also played
in the iOS 27 simulator. Thus neither a universally broken codec nor the precise
physical failure cause has been proven. Device acceptance is required.

Direct message retention uses an authenticated null expiration. Existing
rosters remain unchanged; groups with finite expiry cannot bypass their limit.
Undelivered content retains a bounded delivery deadline of at most seven days.
The relay deletes delivered payloads after ACK. Old `/api/inbox` clients do not
receive the new retained direct envelopes, avoiding destructive rejection;
updated clients use `/api/inbox/retained`. Update both conversation participants.
The old endpoint continues delivering ordinary and retained-group messages.

90 unit tests include signed retained direct text/attachment, peer history,
manual deletion, relay ACK cleanup, legacy-client suppression and finite group
limits. Browser bridge tests cover iOS/Android/web choice, sync persistence,
retained then timed sending and signature/deadline agreement. These are not
physical iPhone/Android playback proofs.

## Requested next work

After Android and iOS updates: a technical pre-audit of protocol/key handling,
PIN/recovery, deletion and peer history, metadata/push, group authorization,
attachment surfaces and update integrity. Use disposable identities only.
Report reproducible findings and limitations; do not label the author's review
an independent audit or guarantee forensic deletion/absolute privacy.
