Domain Create

Generated

This page is generated from qa/customer/specs/domain-create.md — the source of truth. Edit the spec, not this page.

Last run: not yet recorded (run the replay suite to populate status).

Overview

On the onboarding first-workspace step, the customer names a workspace and chooses a published world from the picker, then creates the workspace (POST /orgs/{org}/domains). When at least one world is published the picker is populated and a successful create lands the success state. When no world is published yet, the step renders the world cold-start empty state instead of a picker — never an error toast.

Preconditions

• The stack is running in replay mode at the customer base URL.
• SUPABASE_ANON_KEY is resolvable (the org-less signup mints the onboarding user).
• A published world may or may not exist in the seeded fixture — the scenarios branch on the picker’s populated/empty state, which is the AC9 cold-start contract.

Scenarios

1. Reach the first-workspace step

• Mint an org-less session, land on /auth/onboard, create the org
• Expected: The “Create your first workspace” step renders.

2. Populated picker → create a workspace

• When the world picker is present, name the workspace, choose the first published world, and submit
• Expected: The success state renders (“You’re all set” with the go-to-dashboard action); no error state shows. (Skipped when no world is published — see scenario 3.)

3. No published world → world cold-start, not an error

• When the world picker is absent (no world published), observe the step
• Expected: The “no published world is available yet” empty state renders — never an error toast. (Skipped when a world IS published — the complementary branch of scenario 2.)

Test Data

Label	Value	Notes
Org-less user email	qa-orgless-@spectral.local	Minted fresh per run
Workspace name	QA Workspace	Free text; slug derived client-side
World	(first published world)	From GET /orgs/{org}/available-worlds