fix: propose an organization slug from the first name, not the possessive sentence

[fclairamb]

One spec, implemented in isolation and cleared by an independent audit before being archived to specs/done/2026/09/.

The problem

v0.25.0 shipped a pre-filled create form on /no-org: a brand-new account is offered "Florent's organization". The card submits with no slug and the server derives one from the display name — but the display name is a localized sentence, so the slug became the sentence, truncated at 20 characters:

Locale	Proposal	Slug the user got
en	Florent's organization	florents-organizatio
fr	L'organisation de Florent	lorganisation-de-flo
de	Organisation von Florent	organisation-von-flo
es	Organización de Florent	organizacin-de-flore

Three things wrong with that on the one screen whose entire job is "here is an organization for you, click Create":

• Every personal org in a locale shares a prefix — the boilerplate leads, and the part that identifies the person sits exactly where the cap cuts.
• The name is what gets truncated. A Florent and a Florence on a French install both become lorganisation-de-flo, the second with a collision suffix on top.
• Non-Latin names vanish entirely. 李雷's organization normalized to s-organization.

The UI also showed this slug in the "Will be reachable as…" line and seeded the Advanced field with it, so anyone wanting a better address started by deleting florents-organizatio by hand.

The fix

The display name is unchanged — the localized possessive was a deliberate choice and stays. What changes is where the slug comes from: the first name, proposed by a new pure helper, shown in the preview, and sent to the server as a hint.

POST /api/v1/orgs gains an optional slugBase. The distinction from slug is the point:

• slug stays strict — taken literally, 422 if invalid, 409 if taken, never fixed up. Unchanged.
• slugBase is a hint — normalized, suffixed 2/3/… on collision, and silently ignored when unusable. It never answers 422 or 409.

That is what keeps the guarantee v0.25.0 set out to give: a newcomer who accepts the proposal never meets an error they cannot act on. Sending slug: "florent" strictly would hand the second Florent a 409; retrying florent2 from the browser would re-implement the server's collision handling with a race. One optional field is smaller than either.

李雷 now falls back to the seeded random name (bright-falcon) rather than losing the name entirely.

Deliberately unchanged

The strict slug contract, Slugify's 20-character cap (the input was wrong, not the cap), and the org's localized display name.

QA

Backend build, lint and full test suite green; dash0 build, lint and 1377 unit tests green. dash0 ESLint holds at its 42-error pre-existing baseline with none new.

The E2E was run, not just authored — the /no-org block in create-org.spec.ts now asserts the exact previewed slug, that Advanced seeds it, that Create with nothing typed lands on that exact org address, and that the display name is still the possessive sentence. Backend tests cover the hint's precedence, normalization and collision suffixing, with positive controls proving the strict path still answers 409 and 422.

🤖 Generated with Claude Code