# PR Summary

## Scope of change

Identify the specific component, stack, script 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-account-vending`):
- Commit messages follow conventional commit standards:
- Documentation updated where applicable (`terraform-docs`):
- Only one stack (if applicable) is affected by this PR:
- Ran `terraform init` successfully to verify providers, modules and dependencies:
- Ran `terraform fmt` to format all terraform files:
- Ran `terraform validate` to check for syntax errors:
- Ran `terraform plan` and the output has been reviewed:
- Ran `tflint` with no linting errors:
- OPA policies evaluation passed with no violations:
- No secrets, credentials or sensitive values in code or `tfvars` files:

## 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.