Client rehearsal: a forge with custom apps for a person with zero technical background, in one link, by Tuesday #1115

The owner meets a client in two days and wants to walk in with a forge and some custom apps. The client has no technical background; the forge must explain itself: it is apps, with AI agents that work on them. Two child forges already exist (crewshop, homie), so the spawn works; this is about what the client sees and how the owner makes it.

Done looks like:

• [ ] From /forges/new: name, the apps (pick from the owner's, as forks, or start fresh from a one-line description), a budget, a domain or the default, and one link out. Under five minutes for the owner.
• [ ] The client's first screen, signed in through the claim link: the apps, each with a one-line description in plain words and its agents working or waiting; no map, no board, no settings until asked. Every word on that screen passes the test "would a shop owner understand it".
• [ ] One place for the client to tell the crew what he wants, on the app, in his words; the crew answers there.
• [ ] A rehearsal on the live forge with a client-demo child and two apps, screenshots in the issue, and a list of every word that was nerdy.

Files I expect: src/spawn/*, src/web/pages/new-forge.ts, src/web/pages/claim.ts, src/web/studio/home.ts (a first-visit view), docs/SPAWN.md.

Parked by the crew: the check failed ("a spawned child's apps > after claiming, the home shows the app, and says the crew has no model key and where to add one") and the decider saw no point in another try (pull #1348 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.

Parked by the crew: the check failed ("the asks page > when nothing asks, it says All fine, and so does the header") and the decider saw no point in another try (pull #1406 closed).

Parked twice since a person last spoke here, so it is the planner's now. Every reason:

1. the check failed ("a spawned child's apps > after claiming, the home shows the app, and says the crew has no model key and where to add one") and the decider saw no point in another try (pull #1348 closed)
2. the check failed ("the asks page > when nothing asks, it says All fine, and so does the header") and the decider saw no point in another try (pull #1406 closed)

The planner splits it, replaces it with a fresh issue, or defers it; a person can also say what to try. Nothing starts here until then, and the board lists it.

Split into #1607 (the client's first screen in plain words), #1608 (/forges/new forks the chosen apps into one link) and #1609 (the client tells the crew on the app). The rehearsal itself stays the owner's to run once these land.