Skip to content

feat(setup): say when the new owner still has to verify - #126

Merged
juicycleff merged 1 commit into
mainfrom
fix/setup-verification-required
Oct 9, 2026
Merged

juicycleff merged 1 commit into
mainfrom
fix/setup-verification-required

Conversation

@juicycleff

Copy link
Copy Markdown
Contributor

#120 merged one commit short. Its first-run setup follows the verify-first rule from #124: the account setup creates becomes platform-owner when its email is verified, not at sign-up. That leaves the operator who just finished setup in a dashboard they can't administer, with nothing telling them why.

SetupResponse gains verification_required, true while the account's email is unverified. The setup test checks it next to the existing assertions that setup alone doesn't grant ownership and verifying does.

You'll want the dashboard's setup screen to read the field and point the operator at the verification step. That lives in forge-dashboard and isn't part of this PR.

Setup no longer makes its account platform-owner on the spot. Ownership is
claimed when the email is verified, so the operator who just finished setup
lands in a dashboard they can't administer yet. SetupResponse now carries
verification_required, true while the account's email is unverified, so the
dashboard can say why and point them at the verification step.
@juicycleff
juicycleff merged commit c42b29b into main Oct 9, 2026
21 checks passed
@juicycleff
juicycleff deleted the fix/setup-verification-required branch October 9, 2026 23:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant