Add ATProto episode publishing with GitHub Actions

[Copilot]

Adds full ATProto integration so podcasts using this template can publish their show and episodes to the federated web via standard.site. Each episode is an individual document record.

Changes

Publishing scripts (scripts/)

• publish-episodes.ts — Publishes episodes as standard.site documents. Supports incremental (new only, default) and --backfill (all episodes) modes. Uses cursor-based pagination to fetch all existing documents before diffing, avoiding the 100-record ATProto API limit.
• create-publication.ts — One-time setup script to create the publication record and output the STANDARD_SITE_PUBLICATION_RKEY.

GitHub Actions

• publish-episodes.yml — Runs after the daily "Rebuild Astro Site" workflow completes, publishing any new episodes. Also supports workflow_dispatch.
• backfill-episodes.yml — Manual-only workflow (workflow_dispatch with confirmation input) that publishes all existing episodes.

Schema resilience

• itunes_episodeType is optional(string()) in the Valibot schema — a missing or unexpected field won't crash unattended CI runs.

npm scripts

"publish:episodes": "tsx scripts/publish-episodes.ts",
"publish:episodes:backfill": "tsx scripts/publish-episodes.ts --backfill"

Required GitHub Actions secrets

Secret	Description
ATPROTO_HANDLE	Bluesky handle
ATPROTO_APP_PASSWORD	App password
STANDARD_SITE_URL	Podcast site URL
STANDARD_SITE_PUBLICATION_RKEY	Publication record key
STANDARD_SITE_DID	ATProto DID (for verification endpoint)

Documentation

• README expanded with full setup guide, env var table, and workflow instructions.
• CLAUDE.md updated with new environment variables.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
starpod	Error		Jun 7, 2026 6:09am

[argyleink]

@copilot here's a couple comments, tend to them or defend why it's better as is

[argyleink]

may need better instructions?

[Copilot]

Replaced with env vars and added setup instructions in CLAUDE.md under Environment Variables — includes where to find your DID and how to get the publication rkey. Fixed in 51f2d0b.

[argyleink]

cant this pull from config, or config pull from this? should only need written once

[Copilot]

Moved to environment variables (STANDARD_SITE_DID and STANDARD_SITE_PUBLICATION_RKEY) — matching the existing DISCORD_WEBHOOK pattern. Values are set once in .env, endpoint reads directly from import.meta.env. No more placeholder config in starpod.config.ts. Fixed in 51f2d0b.

[argyleink]

@copilot The move to env was good but now there's a lack of documentation to guide someone to use the feature. Where other env vars are described and explained, explain the standard ones and include a link to the standard.site for additional information. In the readme also explain what being a standard publication means and why you'd want to enable it through the config.

Also, does the site work fine without the env vars? The plugin doesn't need put into the Astro config still?

[Copilot]

@copilot The move to env was good but now there's a lack of documentation to guide someone to use the feature. Where other env vars are described and explained, explain the standard ones and include ...

Added a full "standard.site (ATProto Federation)" section to the README (9291cb1) explaining what it is, why you'd want it, a table with env var descriptions and where to find the values, and a link to the plugin docs.

To your questions: Yes, the site works fine without the env vars — the .well-known endpoint returns a 404 when they're not set. And no, the plugin doesn't need to go into astro.config.mjs — it's only used as a library import in the endpoint file, not as an Astro integration.