New `furumi_library::podcasts::PodcastStore` in its own podcasts.sqlite3:
- user_version migrations in immediate transactions; version 1 is the
prototype schema of the original podcast PR, version 2 renames its tables
to legacy_* and imports feeds, episodes and fetch state with contract
ids; unimportable rows go to legacy_quarantine; newer or foreign files
are refused before anything is written;
- catalog (podcasts, feed aliases, seasons, episodes), subscription, share
and progress registers, listening sessions and local-only fetch state;
- local actions that apply and return podcast sync operations, remote
operation and snapshot application through the music-dht materializers
and merge functions, bounded snapshot export;
- RSS refresh ingestion with stable episode ids and alias learning that
never touches personal state, and queries for the UI.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Add PODCASTS.md as the normative podcast contract: identity and URL
canonicalization, the no-GUID rule, synced versus local versus public
data, operation kinds and merge rules with examples, snapshot recovery,
version gating for peers below v4, Jam privacy and the reserved
playback_rate. Update PLAYBACK_PROTOCOL.md, ARCHITECTURE.md, the crate
READMEs and CHANGELOG.md.
Bump music-dht to 0.6.0 and furumi-library to 0.3.0: new public enum
variants and struct fields are breaking changes for 0.x, and
furumi-library re-exposes music-dht types.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Port the tolerant RSS 2.0 / RSS 1.0 / Atom parser of the original
furumi-tui podcast work into music_dht::podcast::feed behind the
optional podcast-feed feature (quick-xml, encoding_rs, url). Episode
identity depends on what the parser extracts, so it must be shared by
all clients.
The port keeps its robustness (BOM and declared encodings, entities,
mismatched tags, depth and size limits, lenient dates, http(s)-only
media) and adds itunes:season, itunes:episode, itunes:episodeType,
guid isPermaLink and itunes:new-feed-url. Missing GUIDs stay absent
instead of falling back to the enclosure URL, and parsed items produce
identity hints and contract metadata.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>