Rollback Guide

When rollback is needed

Rollback may be needed after broken links, invalid JSON, missing index coverage, unsafe claims, incorrect version labels, or a bad publish that changes expected files.

Files to check first

/release-snapshot-v1-0-2.json
/backup-manifest.json
/site-manifest.json
/master-index.json
/health.json
/validation-log.md
/llms.txt
/discovery.md
/sitemap.xml

How to identify bad publish symptoms

HTTP 404 or 500 on expected files.
Invalid JSON or JSON-LD.
Missing sitemap, llms, or discovery links.
Version mismatch between master index, site manifest, health, and validation log.
Unsafe downstream completion language.
Shopper CTA pointing away from https://www.pricerightrv.com/.

How to use release snapshot and backup manifest

Use the release snapshot to identify the stable baseline version. Use the backup manifest to identify expected files by lane and backup priority.

What counts as restored

Core files fetch with HTTP 200.
Required JSON parses.
Changed files contain expected verification phrases.
Health and validation log reflect the restored baseline or approved patched state.

What must not be claimed without verification

Do not claim CRM, CMS, Google Sheets, Apps Script, webhook, form, alert, email, SMS, social, paid media, inventory, routing, or downstream status without destination-system evidence.

Last updated: 2026-06-12T10:19:06Z

# Rollback Guide ## When rollback is needed Rollback may be needed after broken links, invalid JSON, missing index coverage, unsafe claims, incorrect version labels, or a bad publish that changes expected files. ## Files to check first - `/release-snapshot-v1-0-2.json` - `/backup-manifest.json` - `/site-manifest.json` - `/master-index.json` - `/health.json` - `/validation-log.md` - `/llms.txt` - `/discovery.md` - `/sitemap.xml` ## How to identify bad publish symptoms - HTTP 404 or 500 on expected files. - Invalid JSON or JSON-LD. - Missing sitemap, llms, or discovery links. - Version mismatch between master index, site manifest, health, and validation log. - Unsafe downstream completion language. - Shopper CTA pointing away from https://www.pricerightrv.com/. ## How to use release snapshot and backup manifest Use the release snapshot to identify the stable baseline version. Use the backup manifest to identify expected files by lane and backup priority. ## What counts as restored - Core files fetch with HTTP 200. - Required JSON parses. - Changed files contain expected verification phrases. - Health and validation log reflect the restored baseline or approved patched state. ## What must not be claimed without verification Do not claim CRM, CMS, Google Sheets, Apps Script, webhook, form, alert, email, SMS, social, paid media, inventory, routing, or downstream status without destination-system evidence. Last updated: 2026-06-12T10:19:06Z