v2.18.3

Fixed

A failed Bitbucket call now shows the scopes the token has. The error text was cut at 200 characters, which removed the granted list from a missing-scope 403. Bitbucket scope errors now show the message and both scope lists. Any other error body is cut at 500 characters. GitHub and GitLab summary-comment errors also allow 500 characters, because they share the same helper.
The Bitbucket account lookup warning matches the cause. A failed GET /2.0/user always said the token “likely lacks the Account:Read scope”. That is true for a 403 only. A 401 now says Bitbucket rejected the credentials or the token has no scopes. Any other failure says the cause is not clear. The log and the comment notice give the same advice. The Bitbucket setup guide covers the three cases.
The Bitbucket dismiss help line is no longer shown when the account lookup failed. Verdict polling is off for that run, so a command a reader posted would not take effect. The “Bot account not verified” notice still shows.

See CHANGELOG.md for full technical detail.