- Shipped
- August 25, 2026 at 12:45 AM UTC
- Author
- Kamo
- Commit
- b9b8d69
**************** scopes by provider, and that was right while an alias was only ever resolved as (security_provider_id, alias) — the pair behind a <alias>.<parentdomain> host. Two orgs under different providers could share one without ambiguity. An organization can now be named directly by its alias, with ?org=, and that lookup has no provider to scope by. A repeated alias makes the reference ambiguous platform-wide, so OrgResolutionService refuses it rather than picking one — which leaves BOTH organizations unreachable by alias. The live estate already contains repeats (four orgs share "acme-corp", two share "kia-kaha"), which is why the resolver refuses; this is what stops more being created. excludeId lets an organization keep its own alias while other fields are saved; pass null when creating. 1597 tests pass.