The ignored device-sync PostgreSQL test now also covers a handoff and a
remote Next onto an episode with an unknown position (the relayed
progress register supplies 1200 s and its generation), and checks that
0.12's operation types fail on a relayed podcast operation and read the
log again after the documented cleanup statement, which the m_0055
backwards operation now shares.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Use the shared music_dht::device_sync types instead of private copies
(byte-identical for v3 content, checked against the 0.12.x types and a
golden fixture) and announce protocol 4, because every v4 element is
kept:
- podcast operations stay in the operation log and are relayed only to
peers that reported v4; their registers and the podcast snapshot
sections are merged with the shared rules into an opaque relay table
and returned in this server's snapshots (m_0055);
- the browser bridge carries PlaybackTrack.source: items that are not
library tracks keep the verbatim wire item, so podcast episodes and
Jam placeholders survive the round trip; the player labels and skips
them instead of dropping them;
- the typed queue is persisted in queue_items_json next to queue_json,
which is still written for rollback (m_0054).
Peer versions come from self-reports (profile_protocol_version); relayed
profiles only raise them and DeviceProfileSet no longer stores this
server's constant. Invites carry the inviter's version and a
DeviceProfileSet announces v4 once. Handoffs of a podcast queue to a
device below v4 are refused with an update message, and its playback
commands are ignored while the queue has podcast items. Jam guests see
podcast items as private placeholders, which are mapped back on their
commands.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>