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

The first ask on a spawned forge now makes a new app named from the ask and files the ask there as an issue. The earlier tries went red because they also changed the terminal and its test, which this issue rules out, so I reverted both.

What changed

• The form: the first-tell form on / now posts app=new-app (a new NEW_APP_TARGET in src/web/studio/feed.ts) instead of forge, so "What do you want built?" no longer targets the forge's own repository.
• The action: composerTell in src/web/studio/actions.ts calls a new firstAsk in src/actions/first_ask.ts. It makes the app with newAppFromSentence, then files the ask on it through the existing tell path.
• Autonomy: when crewCanRun is true, autonomy is turned on so a builder can start the issue.
• Autonomy failure: if autonomy cannot be set, the person gets a note saying so rather than a silent success.
• The redirect: it lands on the new app's issue. With no credit, the existing no-credit message is shown instead.
• Test: test/first-ask-new-app.test.ts covers the first tell on a spawned forge: one new app, one open issue with the ask's words, and no thought on forge. It also covers autonomy on and off, and a refused empty ask.
• Docs: two lines in docs/features/starter-crew.md.

What I left out

• Terminal: the terminal's own first-tell still keeps a thought and answers "Received." It is off limits here, so it needs a follow-up issue. src/actions/first_ask.ts is ready for it to call.
• Billing and migrations: untouched.

Checks

• The type check and scripts/gate.ts are clean.
• test/first-ask-new-app.test.ts and test/tui-first-tell.test.ts pass (5 tests).
• I did not run the design lint on this final tree. It was clean earlier, before the terminal files were reverted.
• I did not run any other test files; the forge's check runs the full suite on the push.

To try Open / on a fresh forge, write one sentence and press "Tell the crew". You land on the new app's issue.

🤖 Generated with Claude Code

Closes #11342

The first ask on a spawned forge now makes a new app named from the ask and files the ask there as an issue. The earlier tries went red because they also changed the terminal and its test, which this issue rules out, so I reverted both.

What changed

• The form: the first-tell form on / now posts app=new-app (a new NEW_APP_TARGET in src/web/studio/feed.ts) instead of forge, so "What do you want built?" no longer targets the forge's own repository.
• The action: composerTell in src/web/studio/actions.ts calls a new firstAsk in src/actions/first_ask.ts. It makes the app with newAppFromSentence, then files the ask on it through the existing tell path.
• Autonomy: when crewCanRun is true, autonomy is turned on so a builder can start the issue.
• Autonomy failure: if autonomy cannot be set, the person gets a note saying so rather than a silent success.
• The redirect: it lands on the new app's issue. With no credit, the existing no-credit message is shown instead.
• Test: test/first-ask-new-app.test.ts covers the first tell on a spawned forge: one new app, one open issue with the ask's words, and no thought on forge. It also covers autonomy on and off, and a refused empty ask.
• Docs: two lines in docs/features/starter-crew.md.

What I left out

• Terminal: the terminal's own first-tell still keeps a thought and answers "Received." It is off limits here, so it needs a follow-up issue. src/actions/first_ask.ts is ready for it to call.
• Billing and migrations: untouched.

Checks

• The type check and scripts/gate.ts are clean.
• test/first-ask-new-app.test.ts and test/tui-first-tell.test.ts pass (5 tests).
• I did not run the design lint on this final tree. It was clean earlier, before the terminal files were reverted.
• I did not run any other test files; the forge's check runs the full suite on the push.

To try Open / on a fresh forge, write one sentence and press "Tell the crew". You land on the new app's issue.

🤖 Generated with Claude Code

A refused first ask now leaves no app behind, and I've opened #11399 so the terminal does the same. I pushed the changes to the same branch. The type check passes and test/first-ask-new-app.test.ts passes (5 tests); I did not rerun scripts/gate.ts or the design lint.

• Refuse before making the app: firstAsk now checks length against MAX_BODY, the actor (signed in, not an org), the verified email and the from path before it calls newAppFromSentence. A refused ask makes no app, and a retry makes no second one.
• Length check: I used MAX_BODY, the limit tell itself enforces, rather than TELL_MAX. TELL_MAX only truncates what the form can send, so it would not match the refusal tell gives.
• Direction refusals: the checks above are the refusals tell can give for a new app whose owner is the person asking. Direction is covered by the actor check, because the owner can always write there.
• Cleanups:

- The unused autonomous field is removed. - The composerTell comment no longer claims the terminal calls firstAsk. - The first_ask.ts header comment no longer says the terminal calls it either.

• Tests:

- The empty-ask test now asserts the flash words. - A new test asserts that an over-long ask makes no app and flashes TOO_LONG_WORDS.

• Follow-up: #11399 makes the terminal's first ask call firstAsk and updates test/tui-first-tell.test.ts.

🤖 Generated with Claude Code

Left #11342 open: 1 unticked item remain (The forge's own repository is never the target of "What do you want built?".).