The terminal's deploys screen redeploys or stops production with a key and a confirm, as MCP `app_deploy` does #7231

For: the owner restarts or stops an app from the terminal. Today the page and MCP app_deploy can; the terminal only lists deploys.

redeployEnv and stopEnv (src/actions/apps.ts:621 and :653) are reached from the web (/:owner/:name/app/:env/redeploy and /stop) and MCP app_deploy. src/tui/screens/deploys.ts binds only j/k and r.

Done:

• [ ] For a writer, the deploys screen offers D redeploy and S stop for production. Each asks a one-line confirm that names the app and the environment, then calls the action. The screen says the answer in the same words the page uses.
• [ ] A reader sees neither key. A stopped environment offers redeploy only.
• [ ] A new test/tui-deploy-act.test.ts covers: redeploy after confirm calls redeployEnv, cancel calls nothing, stop then the state reads stopped, and the keys absent for a reader. Use the deploy fakes the existing app tests use.

Files: src/tui/screens/deploys.ts, one test. Risk: low. The rules stay in src/actions/apps.ts.