The account screen of a forge you just started
Where a person who started a forge from the home arrives, and how their first ask is sent (#11510).
/welcome
The page that made the forge (forge-made) sends the person to /welcome on their new forge, with the one-time code in the address fragment, which a server never sees. The screen says "Make your account": a username and one button, Create your passkey. A passkey is the device's fingerprint, face or PIN, with nothing to remember; the browser offers this device or, by its own QR code, a phone (no authenticatorAttachment is asked for, a resident key is preferred, user verification is required). The person is the admin of that forge and signed in. The words say nothing of a sender, a founder or a claim; the screen is welcomePage and welcomeSubmit in src/web/pages/claim.ts, sharing the form, the code check and the one-link-once rules with /claim, which stays for a link someone else sent.
There is one way in, never a choice between two. A browser that cannot make a passkey, or runs no script, is shown a password field instead ("This browser cannot create a passkey, so choose a password."). A passkey that could not be made on this device (cancelled, or no authenticator) brings the password out under the button. The page never says whether passkeys are on or off.
No email is asked for on a forge that sends no mail (mailConfigured, src/actions/verify.ts), and an address posted anyway is not read. On a forge that does send mail the field is there and optional. Either way the link is the proof: the account is made verified, so nothing later waits on a verification mail. Recovery without mail is a second passkey: while the owner signs in with exactly one passkey and no password, the first screens say so in one line with the way to add another (secondPasskeyLine, src/web/pages/next-steps.ts). The everyday account's form drops its email field on such a forge too.
The "Link code" field is filled and hidden by a few lines of script when the address carries the code; without JavaScript it stays visible, with a hint, so the screen still works.
An unknown, used or already-owned link says so in the same plain words as /claim and points back to the home.
The first ask
On a new forge's first screen the box under "What do you want built?" sends on Enter; Shift+Enter makes a newline, and so does Enter while composing text or with a modifier held (firstAskJs, src/web/pages/next-steps.ts). Without JavaScript Enter makes a newline and the Tell the crew button sends. No hint is printed about the key, since it would be false without the script. The line under the box says what pays for the crew and names no second next step: the box is the one thing to do.
The everyday account
An admin with no everyday account and no recorded choice is asked in one line of the home's needs-you row: "You are signed in as the admin. Make an everyday account" (EVERYDAY_NEED, src/web/pages/home_flow.ts). It is never a form on the home. The line opens /settings/everyday (everydayPage, src/web/pages/everyday.ts): why, a username, Make it with a passkey, and Keep using admin, which is remembered (keepAdmin) and ends the asking. No email on a forge that sends no mail; never a password. On a spawned forge the first-login card's step is the same link and the same way to decline.
An everyday account that opens an admin-only route is refused in two sentences that name the admin account (adminRefusal, src/core/everyday.ts): "This is admin-only, and you are signed in as carol, your everyday account. Sign in as alice to open it, or stay carol for everything else." The page (everydayRefusedPage) answers 403 with Sign in as alice, which signs this session out and opens sign-in (POST /settings/everyday/to-admin), and Go home, which keeps the everyday account. The API's not_admin message and MCP's refusal of an admin tool say the same words. A stranger never sees this: they get the route's usual answer, so the admin's name stays private. Test: test/admin-everyday-refusal.test.ts.
The terminal
The terminal does not reach /welcome: it is the screen where the first account is made, and the terminal needs an account to sign in. Once there is one, the first ask is the terminal's own first screen (crewFirstText).
A forge that sends no mail
A forge with no mail configured (neither MAIL_SMTP_URL and MAIL_FROM under Secrets nor the boot settings) cannot ask a newcomer to prove an address. So an unverified account there may fork a public repository and open a pull, and nothing else that costs: creating a repository, running agents and the rest still wait for Verify by the owner (requireVerified; the relaxed check is mayContribute, src/actions/verify.ts). The new-account cooldown and the daily fork and pull limits still hold. /settings/accounts and the terminal's People screen say so and mark who is unverified. With mail configured, an unverified account is refused fork and pull as before (#12106).