guard

To prevent accidental deployments during a codebase freeze, you need a decision gate that reads the `.freeze` indicator to confirm repository status. This blocks non-critical merges and pushes to protected branches while surfacing freeze metadata.

Yes, you can push a hotfix during an active release freeze. The system classifies the requested action and permits essential changes like hotfix or release artifacts with a warning, while continuing to block non-critical updates.

A code freeze indicator is a `.freeze` file that signals an active repository lock. When checked before deployments, it provides metadata including the freeze reason, timestamp, branch, and duration to enforce release policies.

Check freeze metadata before merging by reading the `.freeze` indicator. The system displays contextual guidance including the freeze reason, timestamp, branch, and duration, while clearly stating the allowed change types during the freeze period.

No, the freeze gate does not block all pushes to protected branches. It enforces exception rules that allow only hotfix or release artifacts to proceed while blocking non-critical updates during the freeze window.

After checking the freeze status, suggested follow-up commands include `/unfreeze` or `/hotfix` depending on the required action. These commands help manage the repository state after evaluating the freeze metadata.