Why
The setline Cloudflare Worker was deleted on 2026-08-16, so the canonical hostname now returns HTTP 530. Everything that references it — the landing page's canonical tag, sitemap.xml, robots.txt, llms.txt, /api/ai, and the Privacy and Support links inside the iPhone app — points at a hostname that does not answer.
An App Store submission needs a working Privacy Policy URL, so this blocks release.
What is already done
public/CNAME claims setline.significanthobbies.compublic/.nojekyll keeps the markdown mirrors and dotfiles intact.github/workflows/pages.yml publishes public/ on pushes that touch it
Remaining steps, in order
- Enable Pages from Actions. Repository Settings → Pages → Source: GitHub Actions. Without this the workflow has nowhere to deploy.
- Merge to
main, which triggers the workflow and produces the first deployment.
- Add the DNS record in whichever zone serves
significanthobbies.com:
CNAME setline → significant-hobbies.github.io
- Wait for the certificate. Settings → Pages shows the custom domain check and issues HTTPS automatically. This usually takes minutes.
- Verify:
curl -sI https://setline.significanthobbies.com/ | head -1 # expect 200
curl -s https://setline.significanthobbies.com/api/ai | head -c 80
curl -sI https://setline.significanthobbies.com/privacy | head -1 # expect 200
- Update the fleet catalog once it answers: set
portfolio.deployed and readyToBeShared back to true with a dated reason, and set status from undeployed to live.
Known limitation to accept
GitHub Pages cannot set a Content-Type, so /api/ai is served with whatever type GitHub infers for an extensionless path. The body is valid JSON carrying every field the agent-indexing standard requires, and a test asserts that. If a strict consumer ever rejects it, the fix is a .json path — not a return to Cloudflare.
The security headers the Worker used to set (X-Frame-Options, X-Content-Type-Options, Referrer-Policy) are also gone, as GitHub Pages does not support custom headers. For a static brochure site with no cookies, forms or authentication, this is an accepted trade.
Why
The
setlineCloudflare Worker was deleted on 2026-08-16, so the canonical hostname now returns HTTP 530. Everything that references it — the landing page's canonical tag,sitemap.xml,robots.txt,llms.txt,/api/ai, and the Privacy and Support links inside the iPhone app — points at a hostname that does not answer.An App Store submission needs a working Privacy Policy URL, so this blocks release.
What is already done
public/CNAMEclaimssetline.significanthobbies.compublic/.nojekyllkeeps the markdown mirrors and dotfiles intact.github/workflows/pages.ymlpublishespublic/on pushes that touch itRemaining steps, in order
main, which triggers the workflow and produces the first deployment.significanthobbies.com:portfolio.deployedandreadyToBeSharedback to true with a dated reason, and setstatusfromundeployedtolive.Known limitation to accept
GitHub Pages cannot set a
Content-Type, so/api/aiis served with whatever type GitHub infers for an extensionless path. The body is valid JSON carrying every field the agent-indexing standard requires, and a test asserts that. If a strict consumer ever rejects it, the fix is a.jsonpath — not a return to Cloudflare.The security headers the Worker used to set (
X-Frame-Options,X-Content-Type-Options,Referrer-Policy) are also gone, as GitHub Pages does not support custom headers. For a static brochure site with no cookies, forms or authentication, this is an accepted trade.