Provider evidence expires two hours after issue, so no repo tool could re-verify a release before deploying it later or rolling back to it. verify:promotion --archived keeps every signature, digest and member check and judges freshness at the recorded promotion time; the FE-RB-005 drill takes the extracted release with --release-root. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
19 lines
1.0 KiB
Markdown
19 lines
1.0 KiB
Markdown
# FE-RB-005 — Coherent release rollback
|
|
|
|
Trigger on a release-blocking boot, chunk, render, API, or security defect when
|
|
a safe forward fix is not demonstrated inside the incident window. Select a
|
|
prior immutable release, verify its asset/config/API tuple, atomically switch
|
|
the complete set, perform the provider cache action, and run smoke checks.
|
|
Escalate from the release-cache owner to the release approver/hosting owner.
|
|
The provider recovery target remains TBD until hosting is selected.
|
|
|
|
Close only when compatibility and release-coherence gates pass, critical smoke
|
|
passes, repeated `DEPLOY_MISMATCH` is absent, and the incident timeline records
|
|
the restored release ID. Pointer-switch or cache-purge completion alone is not
|
|
recovery evidence.
|
|
|
|
Verify the prior release before switching to it: `verify:promotion -- --root
|
|
<bundle> --archived` and `drill:runbook -- FE-RB-005 --release-root <extracted
|
|
archive>`. The commands and inputs are in
|
|
[`docs/operations/release-cache-rollback.md`](../operations/release-cache-rollback.md).
|