v2.13.2

Fixed

  • A compute-phase skip (“no changed files” / diff too large) crashed instead of posting cleanly when AI_REVIEW_MODE was left unset (issue #927). Reproduced live on a review run against an already-merged PR. The skip path now defaults an empty review_mode to "quick" before dispatching, the same way the normal path already does.
  • Bitbucket: post_findings failed with “no summary comment to attach findings to” on a brand-new (first-ever) summary comment (issue #930), even though post_summary had just successfully created it. Reproduced live on a fresh bot identity’s first-ever post to a test PR. post_findings now falls back to a direct by-id fetch of the comment post_summary already resolved, instead of relying solely on a list endpoint that can lag behind a comment this same run just created.
  • A full documentation-accuracy pass corrected a batch of stale claims accumulated since v2.12.x across docs/, README.md, CONTRIBUTING.md, SECURITY.md, CONTEXT.md, and action.yml: stale env var defaults, an undercounted analyzer count, an incomplete VcsProvider protocol reference, a missing fail-on-findings default in two example workflows, and more. No code behavior changed. See CHANGELOG.md for the full list.

See CHANGELOG.md for full technical detail.