v2.18.2

Fixed

A Bitbucket review comment no longer shows two “Summary” headings. The summarizer starts its text with a Summary heading, and the comment added its own above it. One heading is now removed, and comments that were already posted are cleaned on the next run. The GitHub job summary had the same doubled heading and is fixed too.
The Bitbucket comment text for Code Insights annotations now follows the findings list. It said “above” and sat before the list. It now always says “findings” and uses “is” or “are” to match the count.
The Bitbucket headline count now matches the list. When some findings are outside the diff, the headline shows both numbers, for example “1 in the diff, 2 total”.
A failed Bitbucket account lookup is now visible. If GET /2.0/user fails, the review cannot tell which comments are its own. It then posts a new summary comment on each push and reviews the full diff. The run now logs a WARNING with the HTTP status, and the comment carries a short notice. The cause is usually an API token without the Account:Read scope (read:user:bitbucket). The Bitbucket setup guide and the starter pipeline now list that scope. The review still does not trust unverified comments.

Findings comments now link to the dismiss instructions. GitHub comments link to the slash command reference. Bitbucket comments link to the dismiss section of the setup guide, and only when AI_BITBUCKET_VERDICTS is on. The link is on its own line before the footer.
An invalid policy.yml is now reported in the review comment. The review still runs with the default settings. The comment now says policy.yml ignored: and gives the reason. The error for a policy named quick or full now suggests a new name and extends:.

Base image and tool updates. The ubuntu:26.04 base image digest, the docker/dockerfile digest, and the ruff image tag are updated.
Comment layout. The Bitbucket changes above change the text of the comment. A script that reads the comment text may need an update.

See CHANGELOG.md for full technical detail.