A new forge's first ask makes a new app from the ask and files it there as an issue #11342

Replaces part of #11278. Cause found on main: the first-tell form in src/web/pages/next-steps.ts posts app=forge (FORGE_TARGET), and composerTell in src/web/studio/actions.ts only keeps it as a thought and answers "Received." Nothing is filed, so nobody takes it.

Done:

• [x] The first-tell form on a spawned forge posts to a target that means "a new app" (not forge); the handler creates the app with the existing newAppFromSentence in src/actions/apps.ts (named from the ask) and files the ask as an issue on it, assigned the way any other tell on an app is (reuse tellFrom).
• [x] When the crew can run (crewCanRun), the issue is startable by a builder: autonomy on, nothing in front of it.
• [x] The redirect lands on the new app, not back on the card.
• [ ] The forge's own repository is never the target of "What do you want built?".
• [x] A test posts the first tell on a spawned forge and asserts: one new app, one open issue on it with the ask's words, no thought kept on forge; it fails on today's main.

Keep it to these files plus one test file (add it to scripts/gate.ts if the gate still lists files). Do not touch billing, migrations, the TUI or docs beyond one line in docs/features/starter-crew.md. Reference work: branch mason/11278-on-a-new-forge-with-included-credit-the (fe0e467101a1) — its pulls went red by spreading across 20+ files; take only what this needs.

Parked by the crew: the check stayed red through 2 automatic tries (pull #11350 closed; its branch scout/11342-a-new-forge-s-first-ask-makes-a-new-app at 1510997512ac keeps the work so far). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.

try 1: docs/features/starter-crew.md, src/actions/first_ask.ts, src/tui/screens/dashboard.ts, src/web/pages/next-steps.ts, src/web/studio/actions.ts, src/web/s… try 2: test/tui-first-tell.test.ts try 3: src/tui/screens/dashboard.ts, test/tui-first-tell.test.ts

Reviewed pull #11390 at its head: ticked The first-tell form on a spawned forge posts to a target that means "a new app" (not forge); the handler creates the app with the existing newAppFromSentence in src/actions/apps.ts (named from the ask) and files the ask as an issue on it, assigned the way any other tell on an app is (reuse tellFrom).; When the crew can run (crewCanRun), the issue is startable by a builder: autonomy on, nothing in front of it.; The redirect lands on the new app, not back on the card.; A test posts the first tell on a spawned forge and asserts: one new app, one open issue on it with the ask's words, no thought kept on forge; it fails on today's main.. left open: The forge's own repository is never the target of "What do you want built?". — The page form is fixed, but the terminal first ask still keeps a thought on forge; #11399 covers it..

Left open after pull #11390 landed: 1 unticked item remains (The forge's own repository is never the target of "What do you want built?".). The planner files each as its own issue and closes this one; a person may close it, tick what is done, or say what is left. Until then the crew does not pick it again.