refactor: record setup per workspace instead of per person

[davemooreuws]

Setup is now recorded on the workspace (setup_completed_at), not the person. /me still carries it, as setupCompletedAt on each workspace. So this doesn't do what SUGA-1954 asked as written: the ticket assumed only /onboarding read the per-user flag, but the workspace page also read it on every load, and still needs that answer.

• First setup and "New workspace" are now one flow at /onboarding?workspace=<slug> (previously /onboarding/new).
• Opening an unfinished workspace sends anyone who may finish it (manageProviders) back to setup. Someone invited part way through gets the workspace as it is. If permissions fail to load, the page shows an error instead of opening the workspace.
• / opens a workspace whose setup is finished, if there is one, rather than the last one chosen. An unfinished workspace opens when asked for by its address or the switcher.
• Cancel deletes the workspace being set up while its setup is unfinished, if the person may delete it (its owner), including after a reload. Before, it deleted only a workspace made on the same page.
• The name step writes ?workspace=<slug> before saving the workspace, so a reload during the save comes back to it instead of saying the name is taken.
• Someone who already has workspaces and opens a bare /onboarding now starts setting up a new one.
• The migration adds workspace.setup_completed_at, marks existing workspaces as set up from created_at, and drops user.onboarding_completed_at.

Closes SUGA-1954

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Updated (UTC)
✅ Deployment successful! View logs	sugabots-website	1fb8ac2	Oct 09 2026, 01:08 AM