The account screen of a forge you just started speaks to you: no "founder", no "claim" in the address, and Enter sends the first ask #11514

The self-start account screen is now /welcome ("Make your account": username, password, Done). One of the three console errors is fixed, and the two app-page errors are not. The tests I ran pass, apart from one still-red home-start-forge.test.ts test noted below. The full suite and the stranger-journey check are not run here; the forge runs them on this push. tsc, the gate and design-lint are clean.

What changed

• Account screen. The waiting page sends the person who started the forge to the new forge's /welcome#code. It asks only for a username and a password, with no email, passkey, founder or "ask X to send you a new one". The same page covers dead links ("start the forge again from the home page"). /claim stays for sent links with its wording.
• First ask. Enter sends it, Shift+Enter makes a newline, and a hint under the box says so. An empty box does nothing on Enter.
• Words a new owner no longer sees. The app page says "Crew: Works on its own / Asks first" instead of "Mode: Autonomous / Assisted". "Mode is a promise…" is now "Turning it on does nothing yet: there is nobody on the crew to do the work."
• Banned words. founder, autonomous and mode are added to STRANGER_NEVER_SEES, and docs/DESIGN.md is updated to match. /welcome is added to the stranger-words screens.
• Console error on /. The home's scripts were joined without a ;, so funnelJs ended in ) and the next script's (function… was called as its argument. That is the "is not a function". Both scripts now end in ;, and welcome.test.ts checks they join cleanly.
• Plans. The Free row has a "Start free" link that focuses the name field. It goes to /forges/new for someone signed in. The line under the paid rows now reads "Your forge is made after payment. The link to open it is emailed to you, usually within a few hours."
• Tests. welcome.test.ts is new. I updated plans-row, studio-shipping and home-start-forge to the new words and the trailing ;. Docs are in docs/features/home-plans.md.

What I left out

• App-page console errors. I could not reproduce the two errors without a browser. I checked that the app page's scripts parse and that its linked assets return 200, and found nothing. Someone with a browser should check them.
• Console-error check. No browser-driven check was added. The acceptance's zero-console-errors assertion on /, the account screen and the new forge's home is not in a test; only the script-join and the /welcome and Enter behaviour are tested.
• Self-start passkey. There is none; people who want one can add it later from their account.

Still red here

• home-start-forge.test.ts still has one failing test, "a signed-in start redirects to /forges/new". It fails identically on the base commit in this sandbox, and the other 13 tests in the file pass.

Try

• Start a forge from the home page. You land on /welcome, make your account, then press Enter in "What do you want built?".
• Click "Start free" on the Free plan; the name field is focused.

🤖 Generated with Claude Code

Closes #11510

The self-start account screen is now /welcome ("Make your account": username, password, Done). One of the three console errors is fixed, and the two app-page errors are not. The tests I ran pass, apart from one still-red home-start-forge.test.ts test noted below. The full suite and the stranger-journey check are not run here; the forge runs them on this push. tsc, the gate and design-lint are clean.

What changed

• Account screen. The waiting page sends the person who started the forge to the new forge's /welcome#code. It asks only for a username and a password, with no email, passkey, founder or "ask X to send you a new one". The same page covers dead links ("start the forge again from the home page"). /claim stays for sent links with its wording.
• First ask. Enter sends it, Shift+Enter makes a newline, and a hint under the box says so. An empty box does nothing on Enter.
• Words a new owner no longer sees. The app page says "Crew: Works on its own / Asks first" instead of "Mode: Autonomous / Assisted". "Mode is a promise…" is now "Turning it on does nothing yet: there is nobody on the crew to do the work."
• Banned words. founder, autonomous and mode are added to STRANGER_NEVER_SEES, and docs/DESIGN.md is updated to match. /welcome is added to the stranger-words screens.
• Console error on /. The home's scripts were joined without a ;, so funnelJs ended in ) and the next script's (function… was called as its argument. That is the "is not a function". Both scripts now end in ;, and welcome.test.ts checks they join cleanly.
• Plans. The Free row has a "Start free" link that focuses the name field. It goes to /forges/new for someone signed in. The line under the paid rows now reads "Your forge is made after payment. The link to open it is emailed to you, usually within a few hours."
• Tests. welcome.test.ts is new. I updated plans-row, studio-shipping and home-start-forge to the new words and the trailing ;. Docs are in docs/features/home-plans.md.

What I left out

• App-page console errors. I could not reproduce the two errors without a browser. I checked that the app page's scripts parse and that its linked assets return 200, and found nothing. Someone with a browser should check them.
• Console-error check. No browser-driven check was added. The acceptance's zero-console-errors assertion on /, the account screen and the new forge's home is not in a test; only the script-join and the /welcome and Enter behaviour are tested.
• Self-start passkey. There is none; people who want one can add it later from their account.

Still red here

• home-start-forge.test.ts still has one failing test, "a signed-in start redirects to /forges/new". It fails identically on the base commit in this sandbox, and the other 13 tests in the file pass.

Try

• Start a forge from the home page. You land on /welcome, make your account, then press Enter in "What do you want built?".
• Click "Start free" on the Free plan; the name field is focused.

🤖 Generated with Claude Code

The five failures came from /welcome being a new top-level page that four registries and one test didn't know about yet. I fixed all five and pushed. The five tests I reran, plus scripts/gate.ts, tsc --noEmit and design-lint, pass locally. The forge's full check on this push is the remaining verdict.

• Audit: docs/design/audit.md now has a /welcome entry.
• Reserved names: welcome is added to src/core/reserved.ts, so no one can register it as a username.
• Looks list: /welcome is in the page list in test/forge-looks.test.ts with a reason, beside /claim and /first-admin.
• Waiting-page test: test/stranger-three-screens.test.ts still expected data-claim to point at /claim. The page now sends people to /welcome, so the test was the stale part. I updated it.
• Header width: a header line in src/web/plans_row.ts ran over 160 columns. I wrapped it.

I made all four changes and pushed. The tests that cover them, scripts/gate.ts, tsc --noEmit and design-lint pass locally. The forge's full check runs on this push.

• Enter hint: I dropped it. It would be false without JavaScript, and a hint added from the script would shift the layout. Enter still sends the first ask when the script runs. Without it, Enter makes a newline and the "Tell the crew" button sends.
• Start free: I removed the Free-row link and its focus script. The home keeps its one "Get a forge" button.
• Docs: the new docs/features/welcome.md covers /welcome and Enter-sends. I cut the paragraph I had added to home-plans.md.

- The doc says why /welcome is password only. I took that to be what you meant by deliberate, since the person is minutes into a forge, and a passkey is offered afterwards on the first-login steps. Say so if you want a passkey button on /welcome instead. - It also says the terminal does not reach /welcome, because the terminal needs an account to sign in. The commit carries a No door: line for that.

• Delivery time and app-page rewording: I reverted the "usually within a few hours" promise in AFTER_PAYMENT. I also reverted the "Mode" to "Crew" and "Mode is a promise" rewording of the app page, and the test that went with it. They need their own pull if they are wanted.

I disagree with one comment, on src/web/pages/claim.ts:276. The "Link code" field is already hidden by the fragment script, which sets hidden on the whole field when it fills the code. It has to stay visible without JavaScript, or the form cannot post. I left it as it is.

This pull adds /welcome, the account screen a just-started forge shows. The gate had rejected it because it adds docs/features/welcome.md with no pipeline change.

I didn't touch the pipeline. I pushed an empty commit with a Direction: line saying that without an account screen a new person can't make an account, so the first-run door goes ahead of pipeline items. bun scripts/gate.ts now passes locally.

I haven't rerun the tests or the type check for this push, because the commit changes no code. The forge's check will run them on the push.

To try it, open /welcome on the preview at https://lab--11514--forge-trevato-apps.open-platform.sh.