An admin stops running a repository as an app from the terminal's Deploys screen with `X`, after typing its name, as Settings' Stop running as an app does #8032

Intent: spin an app down from where you watch it; today only Settings (/settings/app/disable, through disableApp in src/actions/apps.ts) does it, and the Deploys screen (src/tui/screens/deploys.ts) can stop an environment but not stop running the repository as an app.

Done looks like:

• [ ] A repository admin who is a person sees X stop running as an app (the words from STOP_APP in src/web/danger_words.ts); a writer who is not an admin, and an agent, do not.
• [ ] X opens promptScreen: the label says what goes ("production and every preview stop, and their data directories and checkouts are removed; the code is untouched") and asks to type <owner>/<name>; anything else is refused with "Type <owner>/<name> to confirm." and nothing changes.
• [ ] The exact name calls disableApp(f.app, f.user, repo), toasts "no longer an app" or the refusal, and the screen re-reads (an app no longer there says so rather than drawing stale environments).
• [ ] The module comment at the top of deploys.ts says so in one sentence.
• [ ] A new test/tui-deploys-disable.test.ts (driven as test/tui-deploy-act.test.ts drives the screen) proves: typing the name removes the app record; a wrong name keeps it; a writer is not offered X. It fails without the change.

Files: src/tui/screens/deploys.ts, test/tui-deploys-disable.test.ts Risks: disableApp removes data on disk; the test runs against a temporary data directory only. Brief: a builder who knows the terminal screens.