The terminal's deploys screen opens an app's prompt source with `i`: the connected Instagram account, fetch now, connect or remove, as Settings › Prompts does #7465

Intent: an app owner who turns their audience's comments into the crew's next tell can manage that from the terminal. Today only Settings › Prompts (src/web/pages/prompts.ts) and MCP prompts reach listPromptSources, addPromptSource, runPromptSource and removePromptSource (src/actions/prompts.ts).

Done:

• [ ] i on the deploys screen (src/tui/screens/deploys.ts) pushes a new src/tui/screens/prompts.ts. It lists the app's prompt sources as the page does: the account, when it was last fetched and what it last turned into, and when it needs refreshing (REFRESH_AFTER_DAYS).
• [ ] a connects one. The token is typed masked, handed to addPromptSource once, and never drawn or logged. f fetches now through runPromptSource and says what came back. d removes the selected source after a confirm.
• [ ] Only the repository's admin who is a person is offered i and the keys. Anyone else is not offered i.
• [ ] Refusals use the action's words (not_found, no_such_source and the add checks).
• [ ] A test (e.g. test/tui-prompts.test.ts) connects a source with a fake fetch, checks no frame holds the token, fetches now, removes it after a confirm, and checks a reader has no i.

Files: src/tui/screens/deploys.ts, src/tui/screens/prompts.ts (new), a new test.

Risk: the fetch reaches Instagram. The test must use the action's injectable fetch, never the network.