Always validate release workflow changes with targeted regression tests

For release/publish workflow changes, the user consistently expects defensive handling of malformed or changed state and regression tests covering it. Preserve required cleanup actions even when optional inputs are absent or invalid, bind approvals/promotions to current live issue state, fail closed on authorization or attestation inconsistencies, and verify security-sensitive cases such as self-approval. Export or structure entry points for testability when needed, then add focused tests that assert both permitted behavior and skipped API/file operations.