codeac rollback safety after destructive schema changes — verification needed

Context

The tool identified as codeac does not match any widely documented migration or code-analysis platform in public sources as of 2024. This question assumes an internal or emerging product that manages database schema migrations and exposes a rollback mechanism.

Goal

Determine whether codeac can guarantee a safe automatic rollback after a migration that includes destructive operations such as column drops, type narrowing, or table renames.

Constraints and uncertainty

• No official documentation, version matrix, or community references have been located for a product named codeac.
• If the name is a typo (e.g., CodeQL, Codacy, CodeClimate), the rollback behavior would differ entirely.
• Mainstream migration frameworks treat destructive changes as irreversible without a prior backup or compensating script; automatic safety is typically opt-in.

Questions

1. What is the exact product name, vendor, and version series for the tool referred to as codeac?
2. Does its documented migration API declare rollback safety guarantees for destructive schema operations?
3. If no such guarantee exists, what manual verification steps does the maintainer recommend before enabling automatic rollback in production pipelines?