Renaming a project no longer fails with a 400 error

Renaming a project triggered a 400 error in a frustrating way: the URL would update to the new slug before the save call finished, then the save call would fail because the API was still looking for the previous identifier in the URL. The result was a vague "something went wrong" toast and a name that didn't actually save.

We fixed the underlying logic so the URL keeps the stable identifier while the displayed slug updates in the background. Renaming a project just works now — type the new name, save, done. Your slug updates correctly on the public side without breaking the admin URL you're standing on.

Bonus: if something genuinely does fail during a project save, we now surface the specific server error instead of a generic message. If the slug collides with another project, you'll see exactly that — not a code.