epic: podcasts - Deliver Markdown-backed podcast functionality #353

Outcome

Publish approved episode Markdown through reachable archives/details with genuine audio playback.

Verified context

Podcast components and types exist but active routes do not expose them. The detail player simulates progress instead of consuming audio. Editorial verification already belongs to #43.

Scope

Coordinate #361–311 against #43’s approved launch manifest: at least one approved podcast and a clear purpose. Trace selected metadata, written content, genuine audio and equivalent text alternative to approved revisions and rights/credits. Separate editorial clearance from adapter, route and playback evidence. Launch acceptance requires reachable archive/detail content and actual playback validation, not just simulated events or fixture passes. Missing approved media, selection or runnable prerequisites blocks acceptance. Hosting, privacy, feeds and offline decisions remain unresolved.

Acceptance criteria

• Approved Markdown supplies metadata and show notes without duplicate TypeScript narrative.
• Archive/detail/taxonomy links resolve against the same eligible collection.
• Audio controls play genuine approved audio; its equivalent approved text alternative is reachable; unavailable sources are not presented as playable.
• Three child outcomes are verified; editorial and asset sourcing remain separate.

Boundaries and sources

Creation defines work only; it does not start implementation. Preserve unrelated code, protected assets, editorial wording and existing records. Do not fabricate content, identity, media, manuscript chapters, dates or engagement data. Use approved repository-native authoring, validation, preview and publication decisions; do not provision an external CMS or database. Existing editorial verification remains with its current issues. All acceptance criteria remain unchecked until evidenced.

Repository evidence was inspected on develop at 4ecdb26d9655a48bf000a7c89da2f70383edce87. Recheck before implementation; no build or browser tests were run for this draft. Follow repository instructions and applicable Spec Kit requirements. Paths below refer to this repository.

Sources: repository instructions, application, editorial content.

Unanswered clarification questions

These questions refine the author-directed conditional launch requirement; they do not authorise implementation, publication, editorial production, asset sourcing or unresolved hosting/privacy/feed choices.

1. Which approved episode Markdown and genuine audio sources are eligible for publication and playback?
2. Which metadata, show-note and taxonomy mappings are approved for the shared episode collection?
3. How should unavailable or invalid audio be presented without implying that it is playable?
4. Which evidence should demonstrate consistent archive/detail links and actual playback behaviour across the three child outcomes?
5. Who accepts the integrated podcast outcome while confirming that editorial verification and asset sourcing remain separately owned?