[PM-40493] Claimed Domain Account Delete Check

[rr-bw]

🎟️ Tracking

PM-40493

📔 Objective

Adds a claimed-domain check to DeleteAsync({single param}), so that both endpoints are covered by the one check:

• DELETE /accounts - Delete() (was already covered)
• POST /accounts/delete-recover-token - PostDeleteRecoverToken()

📸 Screenshots

[github-actions]

🤖 Bitwarden Claude Code Review

Overall Assessment: APPROVE

This PR moves the claimed-domain guard from AccountsController.Delete into UserService.DeleteAsync(User), so both the authenticated DELETE /accounts path and the anonymous POST /accounts/delete-recover-token path are covered by a single check. I traced every caller of IUserService.DeleteAsync / UserManager<User>.DeleteAsync across src, util, and bitwarden_license — the only two are the controller actions named in the description, and the org-admin path (DeleteClaimedOrganizationUserAccountCommand) deletes through IUserRepository.DeleteManyAsync, so it is unaffected. In the token overload the guard runs after VerifyUserTokenAsync, which keeps the claimed/unclaimed state from being observable without a valid delete token. The error surface for DELETE /accounts is unchanged, since the controller previously threw the same BadRequestException(new CannotDeleteClaimedAccountError().Message).

Code Review Details

No findings.