The terminal's deploys screen probes a running app with `p`: every door tried as nobody, a user and an admin, read-only, as MCP `probe` does #7323

Intent: the owner checks from the terminal that an app answers who it should and refuses who it should not.

Done:

• [ ] On the deploys screen (src/tui/screens/deploys.ts), p runs the same probe the MCP tool probe runs (src/contract/probes.ts) against the running app, and lists one line per door: path, as whom, the status, and ok or what was wrong.
• [ ] An app that is not running says so in words, and nothing is tried.
• [ ] Only viewers the MCP tool lets probe are offered p.
• [ ] A test (e.g. test/tui-deploys-probe.test.ts) drives p against a fake runtime and sees one ok and one wrong line.

Files: src/tui/screens/deploys.ts, a new test. Risk: the domains issue in this plan also edits this screen; keep the two in separate sections.