Operate Pulsar documentation
Use the scheduled workflow to build, link-check, and probe the public documentation origin. It does not collect reader analytics; deployment history and public HTTP responses provide the operational evidence.
Watch the release signals
| Signal | Expected result | Response when it fails |
|---|---|---|
| Scheduled quality run | Build, links, budgets, and generated artifact pass | Triage the failing repository-owned check before Cloudflare deploys the next Git revision |
| Apex response | HTTPS, canonical host, secure headers, and a rendered route | Check DNS, custom-domain attachment, and Pages deployment history |
www response | 301 to the apex with the same path and query | Restore the Cloudflare Redirect Rule |
| Preview response | X-Robots-Tag: noindex | Stop preview promotion and correct the Pages header rule |
| Release revision | Matches the Cloudflare Pages deployment for main | Promote the previous known-good deployment |
Validate a production deployment
- Confirm Cloudflare Pages deployed the intended
mainrevision and retain its deployment URL in private evidence. The GitHub workflow verifies the source; it does not deploy Pages. - Fetch
/, one guide, one reference page,robots.txt,sitemap.xml,/404.html, and a.htmlalias. Confirm the response status, canonical host, redirect target, cache policy, and security headers. - Confirm a pull-request deployment exposes
X-Robots-Tag: noindexbefore sharing its URL. - Run the scheduled uptime probe after DNS activation. A failed public probe blocks launch approval rather than becoming a waived warning.
Recover safely
Promote the prior known-good deployment in Cloudflare Pages, then repeat the response checks. The deployment history promotion is the rollback mechanism; it preserves the checked artifact and avoids an emergency local rebuild.
Boundaries
Cloudflare DNS, access to the existing Pages project and zone, custom-domain attachment, Pages build settings, and the Redirect Rule are administrator-owned controls. The repository can validate its artifact but cannot prove those external settings until an authorized deployment and public probe run.