Deploy docs with GitHub Pages

[Seth Juarez (sethjuarez)]

Summary

• replace the manual Azure Container Apps web deploy with a GitHub Pages artifact deploy
• build the Astro/Starlight site from web and deploy web/dist via actions/deploy-pages
• trigger deployment on manual dispatch and on main pushes that change the web app or deploy workflow
• add web/public/CNAME for prompty.ai

Validation

• verified pinned action tag SHAs for actions/configure-pages@v5.0.0, actions/upload-pages-artifact@v4.0.0, and actions/deploy-pages@v4.0.5
• cd web && npm run build (291 pages built, internal links valid)
• git diff --check

Required repository/domain setup

Before the first successful deploy, a repo admin should set Settings → Pages → Build and deployment → Source to GitHub Actions. The repo currently reports Pages source as branch publishing from main /.

For prompty.ai, configure the apex domain DNS for GitHub Pages:

• A 185.199.108.153
• A 185.199.109.153
• A 185.199.110.153
• A 185.199.111.153
• optional IPv6 AAAA records from GitHub Pages docs

Then set/verify the custom domain as prompty.ai in repo Pages settings and enable HTTPS once DNS verifies.