A person who opens the forge's link can start their own forge from the first… #11156

A person who opens the forge's link signed out now sees one field and one button, "Start my forge", in the home page's first view. Submitting makes the forge through the same door and sends them to its claim page, which asks for a username and password and signs them in. The new tests (test/start-forge.test.ts) and the agents-page, spawn-child-apps and web-ui suites pass, as do tsc and the gate.

I have not run the real-browser test from the acceptance list, so nothing here proves the full home → claim → signed-in path in one run. The cold-read eval was not run either, and no home-page first-view budget test turned up to run.

What changed

• Form: the home page's hero says "Your own forge, free to try…" and carries the field with a label and the button. A live "name is free / taken" line sits under the field, backed by GET /start/check, which only looks for an existing forge of that name and never creates one.
• Submit: POST /start (src/web/pages/start.ts) calls spawnDoor as an anonymous visitor, so the free plan and the visitor rate limits apply.
• Hand-off: the visitor gets an "Open my forge" page that forwards to <name>--…/claim#<code>. It is not a 303 because the CSP's form-action 'self' stops Chrome following a form post to another origin. The code travels in the link's fragment, so nobody copies it. Home → hand-off → claim is three screens.
• Refusals: a rate limit, a taken or invalid name, or no room come back on the home page, above the same form, with what to do next. The status is 429 for a rate limit and 422 for the rest.
• Signed-in visitors: a person who is already signed in is sent to /forges/new?name=… instead.
• New forge's first screen: a spawned forge now opens with one line: make an app or bring a repository, and the crew builds it with a model key or a paid plan.
• No crew credit: the note now says there is no model credit and gives two links: add a model key, or pick a paid plan (<parent>/pricing, read from parent.json). A non-admin is told to ask their admin.
• /agents: it keeps its form and the subtitle now links to /#start for people.
• Header: when signup on the top forge is not open, the visitor's header shows "Start my forge" (#start) instead of "Create an account".

Open points

• /pricing: it does not exist on this branch (#11149 hasn't landed), so the paid-plan link points at the parent's /pricing, which is a 404 until that merges.
• No-room check: POST /start checks for room itself, because spawnDoor does not.

Left out

• The live check isn't rate-limited because it only stats a file.
• Names are lowercased before checking. Reserved names such as forge are not blocked.
• No new dependency.

To try it: open / with no cookies, type a name, press "Start my forge", then set a username and password on the claim page.

Closes #11153

A person who opens the forge's link signed out now sees one field and one button, "Start my forge", in the home page's first view. Submitting makes the forge through the same door and sends them to its claim page, which asks for a username and password and signs them in. The new tests (test/start-forge.test.ts) and the agents-page, spawn-child-apps and web-ui suites pass, as do tsc and the gate.

I have not run the real-browser test from the acceptance list, so nothing here proves the full home → claim → signed-in path in one run. The cold-read eval was not run either, and no home-page first-view budget test turned up to run.

What changed

• Form: the home page's hero says "Your own forge, free to try…" and carries the field with a label and the button. A live "name is free / taken" line sits under the field, backed by GET /start/check, which only looks for an existing forge of that name and never creates one.
• Submit: POST /start (src/web/pages/start.ts) calls spawnDoor as an anonymous visitor, so the free plan and the visitor rate limits apply.
• Hand-off: the visitor gets an "Open my forge" page that forwards to <name>--…/claim#<code>. It is not a 303 because the CSP's form-action 'self' stops Chrome following a form post to another origin. The code travels in the link's fragment, so nobody copies it. Home → hand-off → claim is three screens.
• Refusals: a rate limit, a taken or invalid name, or no room come back on the home page, above the same form, with what to do next. The status is 429 for a rate limit and 422 for the rest.
• Signed-in visitors: a person who is already signed in is sent to /forges/new?name=… instead.
• New forge's first screen: a spawned forge now opens with one line: make an app or bring a repository, and the crew builds it with a model key or a paid plan.
• No crew credit: the note now says there is no model credit and gives two links: add a model key, or pick a paid plan (<parent>/pricing, read from parent.json). A non-admin is told to ask their admin.
• /agents: it keeps its form and the subtitle now links to /#start for people.
• Header: when signup on the top forge is not open, the visitor's header shows "Start my forge" (#start) instead of "Create an account".

Open points

• /pricing: it does not exist on this branch (#11149 hasn't landed), so the paid-plan link points at the parent's /pricing, which is a 404 until that merges.
• No-room check: POST /start checks for room itself, because spawnDoor does not.

Left out

• The live check isn't rate-limited because it only stats a file.
• Names are lowercased before checking. Reserved names such as forge are not blocked.
• No new dependency.

To try it: open / with no cookies, type a name, press "Start my forge", then set a username and password on the claim page.

I changed nothing and pushed nothing: the preview didn't fail because of the code. The deploy log ends with ready and done: https://lab--11156--forge-trevato-apps.open-platform.sh, and the process came up in about 5 s. The "no tests declared, none run" line only says forge.json has no top-level test entry. This repository declares its tests under check (the fast, run and verify commands), which the forge runs separately on each push.

I checked the running preview. / carries the action="/start" form, and /start/check?name=abc answers {"free":true,"message":"abc is free."}.

The only local gap is the real-browser test from the issue's acceptance list, which I couldn't run here. If the forge's check on this push comes back red, send me that log and I'll fix it.

All seven points are addressed and pushed. bun test test/start-forge.test.ts passes, tsc, the gate and design-lint are clean, and the other suites touching the home page and waking page pass (one test changed, below). I could not run a browser here, so the wait-then-go path and the 44 px sizes are checked from the rendered HTML and server responses, not on the preview at 390 and 1280. One check fails, and it fails the same without my change: test/attention.test.ts reports the repository page at 126 words against a budget of 117.

1. Arrival. POST /start now answers a "Setting up <name>…" page instead of an immediate hop. It polls a new same-origin GET /start/ready?name= and goes to the claim page only when the new forge's /healthz answers. The endpoint only probes names this forge made, at the address it derives itself. After 120 s the page says setup has not finished and offers "Open it anyway". Without JS, <noscript> gives the link.
2. Waking page. A forge made in the last ten minutes now reads "Setting up" and "is being set up". An older one still says "was asleep". I did not chase the 5 console errors separately. They most likely came from the 503 claim page loading, which the person no longer reaches. Please check the console on the preview.
3. Reserved and taken. /start/check and the submit both check the forge's reserved names, existing forges and the owner's and crew's names. "forge" now reads "forge is taken. Try forge-forge." with one suggestion, and the submit refuses it without creating a ledger.
4. Lowercase. The field lowercases as the person types and keeps the caret.
5. Address hint. The hint is filled live from the real host pattern, for example Its address: https://your-name--<host>, with the typed name replacing your-name.
6. One button. The first view is the sentence, the field and Start. The AI-assistant block and "Create an account" moved to their own section (#assistant) below it, and "Create an account" left the top bar.
7. Tap targets. Open in ChatGPT, Grok, Claude and Create an account are size="lg" buttons, 44 px. The copy button is 44 px through a small .door-agent .btn-icon rule.

I changed one existing assertion. test/forge-sleep.test.ts expected "Waking up" for a forge created moments before in the same test, which now correctly says "Setting up".

I did not do the wait in place on the home page. It happens on the page that POST /start answers, because the page's form-action 'self' and the claim code in the link fragment make an in-place swap more code than it earned. If you want the home page itself to stay put, say so.

The browser test you asked for is the server-side suite in test/start-forge.test.ts:

• Waiting page: the answer is the waiting page carrying the claim link and no hop.
• Ready and not ready: /start/ready says ready, and says not ready when the probe fails.
• Reserved and taken names: the reserved-name case is covered, including the 422 on submit.
• Home page: the first view has one button, the address pattern is filled in and the AI block sits below it.

I could not assert the browser's follow-through to a 200 on the new forge's /claim here. The sandbox cannot reach new forges, so the test's probe stands in for it.

To try it, open / signed out, type "Hello" (the field becomes hello), and press Start my forge. You stay on "Setting up hello…" until the new forge answers, then land on its claim page.

The commit carries No door: and Direction: lines for the gate's two rules.

The check's nine failures are fixed and pushed. The tests that cover them pass locally: the reserved-names, first-login, looks, design-audit, front, client-home, pages-budget, web-budget, snappy and start-forge suites. tsc, scripts/gate.ts and the design lint are clean. I did not run the full suite; the forge's check does that on this push.

• New routes not registered. The new /start routes were missing from the reserved names (src/core/reserved.ts). The looks not-a-page list now has /start (test/forge-looks.test.ts). docs/design/audit.md now has entries for /start/check and /start/ready, the two pages design-audit.test.ts found.
• Jargon on the first screen. The new "Next:" line and the crew-credit note used "model key" and "repository", which the first-login jargon test bans. They now say "bring your code", "add your own credit" and "pick a paid plan". test/start-forge.test.ts asserted the old wording, so I changed those strings; the old test was wrong against the jargon rule.
• Closed forge lost its link. /signup had disappeared from the door of a forge that doesn't take open sign-ups. The "Create an account" link is back there, shown unless the forge is closed, next to "Start my forge".
• Stranger home over its statement budget. The stranger's home page ran 21 SQL statements against a budget of 20, because I called offersSignup twice. It is now read once in src/web/studio/home.ts.

I did not add a picture of /start to the looks, because /start isn't a page of its own.

I merged main into the branch and pushed it; the only conflict was in src/spawn/plan.ts. The type check and scripts/gate.ts showed no errors. I ran 30 spawn, plan, front-door and anonymous test files: 225 pass, 5 skip, 0 fail. I did not run the full suite, because scripts/fast.ts said the diff was too broad to name tests, so the forge's own check will run it on this push.

• Conflict: this branch exports NAME from plan.ts, and main added a PLAN_KEY constant next to it. I kept both: NAME is still exported and PLAN_KEY is there.
• Skipped tests: the 5 skips are the unix-socket and cell suites, which the sandbox can't run.
• Sandbox denials: the run also logged blocked outbound connections to hosts like kid--localhost:80. The tests passed anyway.

I merged main into this branch and pushed it. The only conflict was src/web/studio/home.ts.

• Conflict: it was one sentence in the front-door copy. My side said hosted forges start "at the top of this page". main now lists the plans on the home page itself, and says "Hosted forges are coming." when none are priced. I kept main's wording and its plans list, because the plans are on the page now and "at the top of this page" would be wrong.
• Type check: bun x tsc --noEmit printed nothing before the full test run, which hit the time limit.
• Tests: 70 tests pass across 7 files covering the start flow, plans, looks, sleep, the README front door and the home page. I did not run the whole suite. scripts/fast.ts could not narrow the diff (2,254 of 2,713 test files), so I picked those files myself.
• Gate: bun scripts/gate.ts printed only a sandbox network denial and no gate result. It tried to reach from-agents--forge.test:443, so I can't say it passed. The forge's check will run it.

Parked by the crew: the check stayed red through 2 automatic tries