ci: update AI reviewer action

[joryirving]

Summary

• Updates the AI PR reviewer action to the pushed fix commit.

Validation

• Workflow file sanity-checked locally.

[its-miso]

✅ Automated recommendation: APPROVE

Analysis engine: minimax/MiniMax-M2.7@https://litellm.jory.dev/v1

PR #118 Review: ci: update AI reviewer action

Summary

Updates the AI PR reviewer GitHub Action from version tag v1.0.12 (commit 314812092cf2243a3813501a61ff0794aa5e0c63) to a pushed fix commit 30b2c8a71df038d9658e7f052b0ee67f7f1af120.

Change-by-Change Findings

.github/workflows/ai-pr-review.yaml (1 line)

• Replaced action reference from version-tagged commit to specific commit hash
• Removed inline version comment (# v1.0.12)
• Change is minimal, targeted, and consistent with repository patterns

Sources

• PR ci: update AI reviewer action #118: ci: update AI reviewer action #118
• Modified file: .github/workflows/ai-pr-review.yaml
• Repository history shows consistent pattern of updating this action (prior updates at v1.0.1 through v1.0.6)

Standards Compliance

This PR is a CI infrastructure change and does not touch product code. The applicable standards from AGENTS.md/CLAUDE.md focus on product direction and UX constraints, which are unaffected. The PR follows conventional commit format (ci: prefix) and maintains consistency with existing workflow patterns in the repository.

Linked Issue Fit

No linked issue. This is a routine dependency update to pull in a pushed bug fix, which does not require issue linkage per contributing guidelines (small fixes like CI updates are common candidates for direct updates).

Evidence Provider Findings

None configured for this repository.

Tool Harness Findings

No tool requests were executed. The planned approach was plan_execute_once with zero planned requests. This review is based solely on static corpus analysis.

Unknowns / Needs Verification

1. Missing commit context: The PR body states "pushed fix commit" but does not link to what bug this fixes in the pr-reviewer-action. Without the upstream commit message or linked issue, I cannot verify the fix is relevant or safe.
2. Version tag removal: The # v1.0.12 comment was removed. This reduces human readability—future maintainers cannot quickly identify which version this was without git history.
3. Security note: Moving from a version tag to a bare commit hash trades tag resolution for exact reproducibility. This is acceptable here since both references are from the same organization (misospace) and the action is self-hosted.

Recommendation

Approve. This is a straightforward dependency pin update consistent with the repository's CI workflow patterns. The change is minimal, targeted, and follows conventional commit conventions. The minor concerns (removed version comment, lack of upstream fix context) do not warrant requesting changes for a routine CI update.