Upgrade, Rollback, and Recovery Operations
Preflight, migration, verification, rollback, and re-upgrade decisions.
Keep source, image, schema, and data recovery decisions separate.
Source boundary
Source boundary: AutoCore current main 7a504f6e430c16d4fcb03ebdea3cc3fb7816df60, checked against immutable v1.0.0-rc.1 at 9edfb109f44cc80385784c694b96392cfc04e70f.
The release line documents supported upgrade paths, immutable image lineage, migration verification, and rollback planning. Database restore is not an automatic companion to application rollback.
Text alternative: verify the target and backup gate, activate an immutable image, check health and routes, and consider application-image rollback only after schema compatibility review. Database restore is separate.
| Check | Source-backed expectation |
|---|---|
| Scope | Do not overwrite Generation 1 or force a migration to resolve an uncertain release state. |
| Evidence | Use placeholders, timestamps, release identity, route, status, and request ID where relevant. |
| Safe action | pnpm verify:full |
| Stop condition | Unknown authorization, destructive impact, secret exposure, or conflicting evidence. |
Verification
Run the safe check, record its result, and compare the outcome with the documented contract. If the result depends on external configuration or provider availability, mark it as configuration-dependent rather than claiming a product guarantee.
pnpm verify:full
Safety boundary
Examples are non-production and use placeholders. Do not deploy, reset, force a migration, create secrets, activate providers, replay sensitive work, or expose private data from this page.