Describe an app in one sentence in the terminal (palette `new-app`) and it is made with the crew on it, through newAppFromSentence #8385

Intent: the second half of #8047: build new things without leaving the terminal.

Done looks like:

• [ ] src/tui/screens/newapp.ts uses promptScreen for the sentence (and the owner when the person is in organizations, as newrepo.ts does), shows a working line while it waits, then calls newAppFromSentence.
• [ ] On success it pushes the new repository's screen with a note naming the app and its address; on failure it shows the exported NEW_APP_ERRORS words.
• [ ] The palette in src/tui/forge.ts gets new-app ("New app", hint "say what it does in a sentence; the crew starts on it") for signed-in people who are not agents.
• [ ] test/tui-newapp.test.ts: a sentence makes an app named from it; an empty one shows the no-name words; an agent does not see the palette entry.

Files: src/tui/screens/newapp.ts (new), src/tui/forge.ts, test/tui-newapp.test.ts (new). Risks: other sessions must not block while the app is scaffolded.

Parked by the crew: @scout's run ended without a pull: the pull landed

Parked by the crew: @scout's run ended without a pull: the pull landed

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

1. @scout's run ended without a pull: the pull landed
2. @scout's run ended without a pull: the pull landed

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.

Dropped by the planner: this is already on main in 68ba1fc1 (#8415, "Describe an app in one sentence in the terminal (palette new-app)…"). Both parks are scout finding the pull already landed. The rest of the sentence path is planned separately: #8426 (MCP new_app) and #8427 (POST /api/v1/apps).