- Shipped
- August 25, 2026 at 2:49 PM UTC
- Author
- Kamo
- Commit
- 8930d2c
The org-creation wizard is eleven steps long and the alias was only checked when the form was submitted, so someone who picked a name another organization already held was told at the very end, on an org that could not be created. GET /org/alias-available answers the same question the write paths enforce — taken globally and case-insensitively, or all digits — so the wizard and the server cannot disagree. If they did, the field would say "available" for something create then refuses, which is the failure this removes. Session-guarded. The answer is one boolean about a name the caller typed, which create would tell them anyway, but there is no reason to hand an unauthenticated caller a way to enumerate which aliases are in use. Advisory, not a reservation: two people can be typing the same alias at once and both be told it is free. The unique index and the create check settle that; this only narrows the window to something that does not matter in practice. 964 tests pass.