fix(recommendations): prefer requested changes over clean mergeability

[philluiz2323]

Summary

• classify targeted PRs with CHANGES_REQUESTED as rejected before considering clean mergeability
• normalize cached review decision / mergeable state strings defensively
• add regression coverage for CHANGES_REQUESTED + clean conflicting signals

Fixes #475.

Tests

• npm.cmd exec vitest run test/unit/recommendation-outcomes.test.ts
• npm.cmd run typecheck

[ghost]

Note

Gittensory Gate skipped

PR closed before full evaluation. No late first comment was created.

Signal	Result	Evidence	Action
Gate result	⚠️ Skipped	#476 is no longer open.	No action.

---

Checked by Gittensory, a quiet PR intelligence layer for OSS maintainers.

[superagent-security]

Superagent didn't find any vulnerabilities or security issues in this PR.

[JSONbored]

@philluiz2323 this is ready from my side.

A few notes:

• The outcome classifier now correctly treats requested-changes review state as stronger than clean mergeability.
• The normalization around review decision and mergeable state makes the behavior more robust than the old direct string comparison.
• The regression coverage is focused on the exact bug.

No code changes requested.