maestro-revert

This document is an operational procedure for identifying and reverting commits associated with a track. It does not contain explicit malware or obfuscated malicious code. However, it prescribes destructive repository and external-issue-tracker operations (git revert, git commit, br update, running CI) that carry moderate operational risk if executed incorrectly or without proper safeguards (backups/branches, authorization checks). Treat this as non-malicious but high-impact operational tooling: require confirmations, backups (create branch/tag), and credential checks before running any commands. Review and run in a controlled environment.