Feature Request: Report 'Success' status when no configuration changes are detected #408

When a repository enforces CLOWarden as a required status check in GitHub branch protection rules, PRs that do not touch CLOWarden configuration files (e.g., documentation or governance updates) are permanently blocked. Because CLOWarden does not run or emit a status for these files, the required check remains perpetually "Expected," forcing repository administrators to manually override protections to merge.

Current Behavior

1. A PR is opened with changes exclusive to non-CLOWarden files (i.e. no changes in config.yaml).
2. GitHub branch protection expects a status report from CLOWarden.
3. CLOWarden does not trigger or report any status (since its config was unchanged).
4. The PR cannot be merged without an admin override.

Expected Behavior

If a PR does not modify any files relevant to CLOWarden, the tool should still emit a successful status check to GitHub. This ensures branch protection requirements are satisfied and allows non-config PRs to be merged seamlessly without admin intervention.