check_scope workflow is not reliable enough

[RitikaPahwa4444]

1. It detected out-of-scope changes in one run and detected the same changes to be within the scope
2. For changes that are out of scope, it should ideally add a comment but failed here: https://github.com/commons-app/apps-android-commons/actions/runs/20496688099/job/58897360413.

For point 1, we need to see the areas of improvement: prompt or model, or both?

[RyukXO-code]

This looks like a combination of multiple issues,

The prompt likely needs to be more explicit about what counts as out of scope
The model also seems too non determined, since the same diff was classified differently across runs.

And the GitHub Actions step that should post comments when something is out of scope failed, which makes debugging impossible.
So I think we need improvements both in the prompt,model configuration and in the CI step that provides the review comments.

[JairoTM-es]

Hi!
I’m a new contributor and I’d like to work on this issue as one of my first open-source PRs.

I checked the failing run linked in the description and saw that the github-script step fails with a 403 (“Resource not accessible by integration”) when trying to post the out-of-scope comment. I can work on fixing this by updating the workflow permissions and reviewing the prompt/model configuration.

Please let me know if I can proceed.

[RitikaPahwa4444]

Sure @JairoTM-es, thanks :)