mr-milchick 3.0.1

## Summary

Describe what changed and why.

## Type of change

- [ ] Bug fix
- [ ] New rule or policy behavior
- [ ] Refactor
- [ ] Documentation
- [ ] Performance
- [ ] Security
- [ ] CI / release / packaging

## Behavioral impact

Does this change affect any of the following?

- [ ] Pipeline pass/fail outcomes
- [ ] Reviewer assignment logic
- [ ] Summary comment behavior
- [ ] Tone classification or rendering
- [ ] CODEOWNERS resolution
- [ ] Planning or execution flow
- [ ] No user-visible behavior change

Explain the impact clearly:

<!--
Examples:
- reviewer routing now prefers CODEOWNERS matches before area fallback
- refine now posts summary comments in more cases
- observe output changed, but execution behavior did not
-->

## Breaking change assessment

- [ ] This is not a breaking change
- [ ] This may be a breaking change for users upgrading Mr Milchick

If potentially breaking, explain why:

## Security impact

- [ ] No security impact
- [ ] Token handling changed
- [ ] GitHub / GitLab API permission usage changed
- [ ] Mutation-capable behavior changed
- [ ] Logging / comment output may expose new data
- [ ] Other security-relevant change

Details:

## Testing

What was tested?

- [ ] Unit tests added or updated
- [ ] Existing tests pass
- [ ] Manual dry-run validation performed
- [ ] Manual mutation-path validation performed
- [ ] CI behavior reviewed
- [ ] Edge cases covered

Testing notes:

## Changelog

- [ ] CHANGELOG updated
- [ ] No changelog update needed

If not needed, explain why:

## Checklist

- [ ] Change is focused and scoped
- [ ] Rule evaluation remains side-effect free
- [ ] Execution remains separated from planning
- [ ] New behavior is deterministic
- [ ] Error handling is explicit
- [ ] Documentation updated where needed

## Additional context

Links, screenshots, logs, rollout notes, or follow-up work.