Queue a whole podcast from its own page, not just a topic

[ralyodio]

A podcast's own page had a play control on every episode and no way to take the whole show. QueueAll.jsx already existed and was wired into TopicPlayer alone; /api/queue spoke add-topic and remove-topic and nothing else. So "queue all" was reachable from a topic and not from the feed that the episodes actually belong to.

What changed

• QueueAll names either a topic or a feed. Same form, same endpoint, same toggle — one branch decides which query the server re-runs. A second component would have drifted from this one.
• /api/queue learns add-feed / remove-feed, alongside the topic pair and on the same terms: the form names the feed rather than carrying fifty guids, and the endpoint re-queries.
• playableEntries / entryLanes / alreadyQueued move into lib/queue.js, and the feed page's literal 50 becomes FEED_QUEUE_LIMIT.

Why the shared helper

The button names the feed instead of carrying its episodes, so the page and the endpoint each work out what the press covers separately — and would disagree the moment either changed its mind about what counts. Both call the same function over the same query at the same limit, so the count on the button and the rows the press adds are the same set by construction.

Blog posts are excluded rather than queued to Read: the control says play, and quietly filling somebody's reading queue with fifty essays is not what they pressed. A feed with nothing playable draws no button at all, which is every blog in the directory.

Verified

Against production data, rendering the real pages:

• /niche-pursuits-podcast-find-your-next-niche-business-idea renders Queue all 10, posting add-feed with the feed's slug, noting the Listen lane.
• A blog page (/oregonwinepress-com) renders no queue-all markup at all.
• /topics/business/play still posts add-topic with topic=business and Queue all 50 — unchanged.
• The endpoint accepts add-feed (401 sign-in-required when signed out) and still rejects an unknown action with 400 bad-action.

pnpm -r test green across all 12 workspaces (apps/web 258, +4 new covering the filter, the lane set and the already-queued count), and pnpm build succeeds.

Not in this PR

While looking into the same page I confirmed why it shows no byline, which turned out to be unrelated: CRAWL_AUXILIARY_WRITES=0 is set on rssamplifier-poller, and that one flag gates both the topics block and the credits block in crawlFeed. It is the deliberate throughput trade apps/poller/src/index.js:108 describes, not a bug, so nothing here touches it.

🤖 Generated with Claude Code