# PR Summary

## What does this PR do?

Provide a clear and concise summary of the changes in this PR and why they are being made.

## Scope of change

Identify the specific policy, rule or directory this PR affects.

## Type of change

Choose one that best describes this PR and delete the rest.

- `feat`: new feature or capability
- `fix`: bug fix or correction
- `chore`: maintenance, tooling, dependencies
- `docs`: documentation changes
- `refactor`: restructuring without behaviour change
- `revert`: reverting a previous commit

## Checks before merging

Fill in Pass or Fail for each item. Write NA if the check does not apply to this PR.

- Branch name is prefixed with the primary type of change (e.g. `feat/add-tagging-policy`):
- Commit messages follow conventional commit standards:
- Documentation updated where applicable:
- `opa fmt` check passed with no formatting errors:
- `opa check` passed with no errors:
- Policy catalog validation passed with no violations:
- Updated `catalog.json` to reflect the change:
- No secrets, credentials or sensitive values in code:

## Notes for the reviewers

Call out anything that needs special attention, known limitations, deliberate trade-offs, or context that is not immediately obvious from reading the code.