Risk classification fails on every re-review.
The comment then says “Risk could not be assessed, so high risk was applied as a precaution”, and auto-approval is withheld. The failed reviews include release-only PRs, although .gitar/config/approve.md explicitly allows unavailable risk for those files. An organization-level criterion plus a gitar review run (2026-11-05 14:24) gave the same result. On a first review, the bot edits its comment about 6 s after it posts it to add the risk label. On a re-review, that edit does not happen. The first failure was on 2026-10-29, before .gitar/ files existed.