Update ai-code-review.yml

[roger-zhangg]

Which issue(s) does this change fix?

updated reviewer still comment the same unexist issue: #8913
Now this time the issue is clear that agent confused the develop branch as the final state. Updated the prompt to make it understand the diff is the actual thing that he needs to review, develop branch is just for reference.
Tested: roger-zhangg#17

Why is this change necessary?

How does it address the issue?

What side effects does this change have?

Mandatory Checklist

PRs will only be reviewed after checklist is complete

• Review the generative AI contribution guidelines
• Add input/output type hints to new functions/methods
• Write design document if needed (Do I need to write a design document?)
• Write/update unit tests
• Write/update integration tests
• Write/update functional tests if needed
• make pr passes
• make update-reproducible-reqs if dependencies were changed
• Write documentation

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[github-actions]

Code Review Results

Reviewed: 09c3cd5..f550448
Files: 1
Comments: 0

✅ No issues found. The changes look good.

The PR updates the pinned commit SHA for the roger-zhangg/sam-pr-reviewer GitHub Action. The action continues to be pinned by full commit SHA (security best practice), the # v1 tag comment is preserved for readability, and no other workflow configuration is altered.