The terminal's "What I can do" screen says when your email is unverified, and `v` sends a new verification email, as MCP `email_verify` does #7314

The terminal's "What I can do" screen (src/tui/screens/can.ts) now tells a person when their email is unverified, and v sends a new verification email.

• The line: while the email is unverified, one line under the role says so, using the account page's wording: until the email is verified you can read and talk, but not make repositories, apps or runs. A verified account sees no line.
• v: sends the email through resendVerification, the same action the account page and MCP email_verify use. The outcome is shown in the same words MCP and the API use (VERIFY_WORDS for too_soon, no_mail and failed, and CAPPED_WORDS). The link only ever goes into the email, never onto the screen. The v key appears in the screen's key list only while the account can actually use it.
• Agents: never offered v and never shown the line. emailVerified already counts every agent as verified, and the screen also checks that the account is not an agent.
• Placeholder addresses: an account still on a placeholder (.invalid) address isn't offered v either, because there is nowhere to send the email. Its line says to add an email from account settings in a browser instead.

The new test/tui-verify.test.ts checks four things. An unverified account sees the line, and v sends exactly one email, to that account's address, with no link on the screen. A second v inside the resend window sends nothing and shows VERIFY_WORDS.too_soon. Once verified, there is no line and v sends nothing. An agent is never offered v.

bun x tsc --noEmit is clean. test/tui-verify.test.ts, test/tui-can.test.ts and test/mcp-size.test.ts pass, and so do the 129 files scripts/fast.ts named (1000 pass, 24 skipped in the sandbox). The MCP is unchanged, so no ceiling moved.

To try it, open "What I can do" from the palette (Ctrl+K) as an unverified account and press v twice: the first press sends the email, the second shows the "try again in a few minutes" refusal.

🤖 Generated with Claude Code

Closes #7301

The terminal's "What I can do" screen (src/tui/screens/can.ts) now tells a person when their email is unverified, and v sends a new verification email.

• The line: while the email is unverified, one line under the role says so, using the account page's wording: until the email is verified you can read and talk, but not make repositories, apps or runs. A verified account sees no line.
• v: sends the email through resendVerification, the same action the account page and MCP email_verify use. The outcome is shown in the same words MCP and the API use (VERIFY_WORDS for too_soon, no_mail and failed, and CAPPED_WORDS). The link only ever goes into the email, never onto the screen. The v key appears in the screen's key list only while the account can actually use it.
• Agents: never offered v and never shown the line. emailVerified already counts every agent as verified, and the screen also checks that the account is not an agent.
• Placeholder addresses: an account still on a placeholder (.invalid) address isn't offered v either, because there is nowhere to send the email. Its line says to add an email from account settings in a browser instead.

The new test/tui-verify.test.ts checks four things. An unverified account sees the line, and v sends exactly one email, to that account's address, with no link on the screen. A second v inside the resend window sends nothing and shows VERIFY_WORDS.too_soon. Once verified, there is no line and v sends nothing. An agent is never offered v.

bun x tsc --noEmit is clean. test/tui-verify.test.ts, test/tui-can.test.ts and test/mcp-size.test.ts pass, and so do the 129 files scripts/fast.ts named (1000 pass, 24 skipped in the sandbox). The MCP is unchanged, so no ceiling moved.

To try it, open "What I can do" from the palette (Ctrl+K) as an unverified account and press v twice: the first press sends the email, the second shows the "try again in a few minutes" refusal.

🤖 Generated with Claude Code

The terminal's What I can do screen now says when your email is unverified, and v sends a new verification email through resendVerification. It uses the same per-account resend window and mail caps as the account page, the API and MCP email_verify, and reports the outcome in the API's words; the link never appears on screen. Agents are always counted as verified, so they are never offered v. An account on a placeholder .invalid address is told to add an email from account settings in a browser, and gets no v either.

This push answers the review:

• Docs: docs/CREW.md no longer calls What I can do "read only". It now says the screen shows an unverified email, that v sends a new verification email as the account page and MCP email_verify do, and what a placeholder-address account is told instead.
• Placeholder test: test/tui-verify.test.ts adds an unverified account on a .invalid address. The test checks that the screen tells it to add an email in a browser, does not offer v, and sends no mail when v is pressed. With the isStandInEmail guard removed, this test fails.
• Shared words: verifyWords(outcome) in src/actions/verify_words.ts maps each resendVerification outcome to its sentence. src/tui/screens/can.ts and src/http/mcp/tools/email_verify.ts both use it, so the two can't drift apart. The MCP tool's error codes and sentences are unchanged.

To try it, ssh with the preview's FORGE_APP_SSH command as an unverified account, open What I can do (ctrl-k), press v, then press v again to see the "a link was sent a moment ago" refusal.

tsc --noEmit passes, as do test/tui-verify.test.ts, test/mcp-email-verify.test.ts, test/verify-words.test.ts, test/mcp.test.ts and test/settings-email-verify.test.ts. I didn't run the full set scripts/fast.ts named: 1104 test files, an estimated 95 minutes.

🤖 Generated with Claude Code

The terminal's What I can do screen now says when your email is unverified, and v sends a new verification email through resendVerification. It uses the same per-account resend window and mail caps as the account page, the API and MCP email_verify, and reports the outcome in the API's words; the link never appears on screen. Agents are always counted as verified, so they are never offered v. An unverified account on a placeholder .invalid address is told to add an email from account settings in a browser, and gets no v either.

• Shared words: verifyWords(outcome) in src/actions/verify_words.ts maps each resendVerification outcome to its sentence. src/tui/screens/can.ts and src/http/mcp/tools/email_verify.ts both use it, so the terminal and MCP can't drift apart. The MCP tool's error codes and sentences are unchanged.
• Docs: docs/CREW.md no longer calls What I can do "read only". It now says how the screen shows an unverified email and what v does, and what a placeholder-address account is told instead.
• Tests: test/tui-verify.test.ts covers four cases:

- An unverified account sees the line, and v sends exactly one mail. - A second v inside the resend window sends nothing and is refused in the API's words. - A verified account and an agent see no line, and v sends nothing. - A placeholder-address account is told to add an email in a browser, is not offered v, and sends nothing when it presses v. This last case fails if the isStandInEmail guard is removed.

• Merge: main changed the same Roles paragraph in docs/CREW.md. I took main's version, keeping the People command's new s (suspend) key and the new "Where you are signed in" paragraph, and reapplied the What I can do sentence to it.

To try it, connect with the preview's FORGE_APP_SSH command as an unverified account and open What I can do with ctrl-k. Press v to get a new link, then press v again to see the "a link was sent a moment ago" refusal.

After the merge, tsc --noEmit passes, as do test/tui-verify.test.ts, test/mcp-email-verify.test.ts, test/verify-words.test.ts, test/mcp.test.ts and test/settings-email-verify.test.ts. I didn't run the full set scripts/fast.ts named, because it was too broad: 1104 test files, an estimated 95 minutes.

🤖 Generated with Claude Code