The terminal's deploys screen lists an app's custom domains, adds, checks and removes one, as MCP `app_domains` does #7421

The terminal's deploys screen now lists the app's own domains for its admin, and n opens a domains screen that adds, checks and removes one. It calls the same actions the settings page and MCP app_domains use, and says the page's words. The tests listed below pass and the type check is clean. I did not open a preview to look at it.

Commit 1 (no behaviour change):

• The domain sentences that lived in src/web/pages/settings.ts (the refusal codes, the records in words, the added and removed messages) move to src/actions/domain_words.ts, following the pattern of env_words.ts. The settings page reads them from there, word for word.
• yesNo moves from waves.ts to common.ts so both screens can use it.

Commit 2 (the feature):

• Domains line: for the app's admin, the deploys screen shows a line like Domains: app.example.com live · shop.example.com waiting for DNS.
• Domains screen (n): each domain is one row with its state and what the last check said.

- + asks for a name and calls addAppDomain. - c calls checkAppDomain, then shows what the check said and Still needed: <records> until the domain is verified. The selected row's footer shows the same. - - asks remove <host>? y/n and calls removeAppDomain.

• Refusals: a bad name and a name another app already has are refused in the page's words. Each action checks admin rights again.
• Who sees it: listAppDomains only answers the app's admin, so anyone it refuses sees neither the domains nor n. If they reach the domains screen directly, it says "Only the app's admin manages its domains." and offers no keys.
• docs/APPS.md and docs/TOUR.md name the new keys.

Choices to look at:

• c, not k, checks a domain. The issue asked for k, but j/k already move the selection on every list screen.
• A separate screen. The domains get their own screen because the deploys list already owns j/k.
• Non-admins see no list. The issue says people who cannot admin should see the list without the keys, but the action refuses them the list itself. I kept the action's gate rather than widening it.

Tests: a new case in test/tui-deploys.test.ts drives the screen with keystrokes, using a stubbed DNS resolver. It covers a bad name refused, an add, the domains line, a taken name refused on a second app, a check showing the record still needed, a non-admin refused, and - then n keeping the domain while - then y removes it. I ran tsc, design-lint, mcp-size, the tui-deploys, waves, settings and domains test files, and the other tui and words test files they share code with. The full suite was not run here; the forge's check runs it on this push.

To try it: ssh into the app's terminal as the app's admin, open Deploys, press n, then +.

🤖 Generated with Claude Code

Closes #7322

The terminal's deploys screen now lists the app's own domains for its admin, and n opens a domains screen that adds, checks and removes one. It calls the same actions the settings page and MCP app_domains use, and says the page's words. The tests listed below pass and the type check is clean. I did not open a preview to look at it.

Commit 1 (no behaviour change):

• The domain sentences that lived in src/web/pages/settings.ts (the refusal codes, the records in words, the added and removed messages) move to src/actions/domain_words.ts, following the pattern of env_words.ts. The settings page reads them from there, word for word.
• yesNo moves from waves.ts to common.ts so both screens can use it.

Commit 2 (the feature):

• Domains line: for the app's admin, the deploys screen shows a line like Domains: app.example.com live · shop.example.com waiting for DNS.
• Domains screen (n): each domain is one row with its state and what the last check said.

- + asks for a name and calls addAppDomain. - c calls checkAppDomain, then shows what the check said and Still needed: <records> until the domain is verified. The selected row's footer shows the same. - - asks remove <host>? y/n and calls removeAppDomain.

• Refusals: a bad name and a name another app already has are refused in the page's words. Each action checks admin rights again.
• Who sees it: listAppDomains only answers the app's admin, so anyone it refuses sees neither the domains nor n. If they reach the domains screen directly, it says "Only the app's admin manages its domains." and offers no keys.
• docs/APPS.md and docs/TOUR.md name the new keys.

Choices to look at:

• c, not k, checks a domain. The issue asked for k, but j/k already move the selection on every list screen.
• A separate screen. The domains get their own screen because the deploys list already owns j/k.
• Non-admins see no list. The issue says people who cannot admin should see the list without the keys, but the action refuses them the list itself. I kept the action's gate rather than widening it.

Tests: a new case in test/tui-deploys.test.ts drives the screen with keystrokes, using a stubbed DNS resolver. It covers a bad name refused, an add, the domains line, a taken name refused on a second app, a check showing the record still needed, a non-admin refused, and - then n keeping the domain while - then y removes it. I ran tsc, design-lint, mcp-size, the tui-deploys, waves, settings and domains test files, and the other tui and words test files they share code with. The full suite was not run here; the forge's check runs it on this push.

To try it: ssh into the app's terminal as the app's admin, open Deploys, press n, then +.

🤖 Generated with Claude Code