Use rollback levels
Level 0 is UI-only rollback. Remove visible surfaces first if users are blocked, while keeping database additions in place.
Level 1 is feature-path rollback. Disable action handlers and cron hooks for the affected feature while preserving schema.
Level 2 is schema rollback. Use only when schema itself is causing operational problems and only after backups.
Validation after rollback
Run a production build and verify dashboard, access pages, product pages, and cron route responses before release.
Do not combine rollback with unrelated refactors. Keep rollback commits narrow and reversible.
Tag rollback commits clearly so forward recovery can reintroduce slices in a controlled order.
Source of truth
Detailed rollback steps live in docs/feature-foundations-rollback-playbook.md.
Incremental changes are tracked in docs/feature-foundations-change-log.md.
Keep both documents updated whenever feature foundations, cron behavior, or schema slices change.