The podcast page

/podcasts is a standing page with a holding line on it. What it needs deciding:

• Whether an episode is an entry with audio attached, or something with its own shape. There is no kind field any more (SC-6), so nothing labels a page an episode — an entry carrying an audio file simply is one. A file in src/content/entries/ with an audio URL in its frontmatter would inherit routing, the sitemap and share cards for free.
• Whether the entry template grows a player. A plain <audio> element costs nothing and works everywhere; anything more is a decision about how much of the page the audio is.
• Whether there is a feed. Worth settling early. Episodes in podcast apps need an RSS feed with <enclosure> URLs, which makes the blob URLs public, permanent and quoted in someone else's database. A URL that has to survive that is a different commitment than one that only has to survive this site.
• Whether the page becomes a section index like Model Behavior once there are episodes to list, rather than the standing page it is now.

Nothing should be built until there is a first episode to build around.

Closed — the page is done, the podcast is not

/podcasts is built and standing. It says there is nothing to hear yet, which is true, and it will say something else when there is.

Everything else above — where episodes live, what an episode is, whether there is a player or a feed — is not this ticket and never really was. That is a podcast, not a page, and it gets its own project rather than trailing behind the launch as an open item nobody is working on. Low priority until there is something recorded.

The back end for it is being developed separately.

Closing this keeps the board honest: a ticket that stays open because a much larger thing has not happened yet stops being a task and becomes a reminder, and the board is not for reminders.

SC-20 still stands up the blob store, because that is launch work — somewhere for audio to live, whenever audio arrives.