Contact page has too little real content for agent trust checks

Context

An is-agentic.com scan of whiskey.fm (95/100 overall — this platform already does a lot right for agent discoverability: llms.txt, markdown twins, OpenAPI, agent-friendly 404s) flagged one "trust anchor" gap:

About, Privacy pages verified - missing: Contact
Publish real /about, /contact, and /privacy pages with at least 500 characters of content each. These are the pages AI agents check to verify your business is legitimate before recommending you.

Current state

packages/starpod/src/pages/contact.astro is just an <h1>, one ~130-character paragraph, and a client-hydrated form:

<h1>Get in touch</h1>
<p>
  Have a question for us or a topic you would like us to cover on the show?
  Reach out here and we'll be in touch soon!
</p>
<ContactForm client:load />

That's true for every site built on Starpod, not just whiskey.fm — this is a template issue.

(Side note while investigating: I couldn't find a /privacy route anywhere in the repo, and whiskey.fm/privacy 404s live, despite the scan reporting Privacy as "verified" — that check result may be unreliable/stale on its own. Flagging in case it's useful, but the actionable gap here is Contact.)

Proposed fix

Add enough real static copy to contact.astro to clear the ~500-character bar and give agents/crawlers something substantive without JS, e.g.:

• A sentence or two on what kinds of messages are welcome (guest pitches, sponsorship, feedback, corrections)
• A direct fallback contact method (an email address) for clients that can't or won't fill out a JS form — ContactForm is client:load, so a no-JS agent/crawler sees the static copy only
• Maybe a link to the show's socials/hosts (already on /about) for people who'd rather reach out there

Could be baked into the shared template with configurable copy via starpod.config.ts, since the "what should go here" text is site-specific.

🤖 Filed with Claude Code

Start with packages/starpod/src/pages/contact.astro and inspect how ContactForm is hydrated. Then read starpod.config.ts to see whether site-specific contact copy can be configured in the shared template. Done means the contact page has substantive static copy for crawlers, explains welcome messages, and provides a no-JavaScript fallback contact method.