[alexcastgonz (pcbeingused333)]

Motivation and Context

finish_reason_from_google_ai_to_semantic_kernel only mapped SAFETY to FinishReason.CONTENT_FILTER. Gemini also ends a response for RECITATION, BLOCKLIST, PROHIBITED_CONTENT and SPII (and the image variants available across the supported google-genai range), and for those the message came back with finish_reason=None, indistinguishable from an unrecognised value or an unfinished response.

Description

• SAFETY, RECITATION, BLOCKLIST, PROHIBITED_CONTENT, SPII, IMAGE_SAFETY and IMAGE_PROHIBITED_CONTENT map to FinishReason.CONTENT_FILTER.
• STOP and MAX_TOKENS are unchanged; other reasons (OTHER, MALFORMED_FUNCTION_CALL, ...) still return None.
• A parametrized unit test covers the new reasons; its 6 cases fail on main and pass with the change. tests/unit/connectors/ai/google passes (158).
• The deprecated vertex_ai connector is left as is.

Contribution Checklist

• The code builds clean without any errors or warnings
• The PR follows the SK Contribution Guidelines
• All unit tests pass, and I have added new tests where possible
• I didn't break anyone 😄

This change was made with Claude Code; the tests were run against main and the branch.

[Copilot]

🟢 Approval recommended

The focused mapping change preserves existing behavior, includes corresponding regression coverage, and has no identified blocking issues.

No open issues 🎉

What changed in this PR

Expands Gemini finish-reason handling so content-blocked responses are reported as CONTENT_FILTER rather than None.

Changes:

• Maps six additional finish reasons to CONTENT_FILTER.
• Adds parameterized regression coverage for each added reason.
• Preserves other mappings and leaves the deprecated Vertex AI connector unchanged.

File	Description
python/​tests/​unit/​connectors/​ai/​google/​google_ai/​services/​test_google_ai_utils.py	Tests all six added content-filter reasons.
python/​semantic_kernel/​connectors/​ai/​google/​google_ai/​services/​utils.py	Groups content-filter reasons and checks membership.

_{Review effort: Balanced}

[alexcastgonz (pcbeingused333)]

Eduard van Valkenburg (@eavanvalkenburg) thanks for the approval. This was dropped from the merge queue by the merge-group run 40323553321, where "Python Pre-Merge Integration Tests - Agents" failed on an empty JSON response from Azure (azure.core DecodeError). The PR only touches google_ai/services/utils.py and its unit test, and its own checks are green, so it looks unrelated. Could you add it back to the queue when you have a moment?