The terminal's notify screen sends a test push with `t` and says whether it arrived #8085

The notify screen in the terminal now has t "send a test", which posts one line to the saved URL and toasts whether it arrived. bun scripts/gate.ts, bun x tsc --noEmit, and bun test on test/notify-test-send.test.ts, test/tui-notify.test.ts and test/mcp-size.test.ts all pass. I did not run the full suite or design-lint.

• sendTest: sendTest(db, userId, sender = post) in src/crew/notify.ts sends Test from the forge — notifications reach you. through the existing Sender, so it goes through outboundFetch (https only, no redirects). It answers sent, refused or off, never throws, and never logs the URL.
• t key: src/tui/screens/notify.ts shows t only when a URL is set. The toast is sent to <host>, or <host> did not take it in the danger tone. The toast carries only the host.
• Rate limit: claimTest allows one test per user per 30 seconds, kept in memory. A second press shows just sent — wait a moment and sends nothing. Because it is in memory, a restart resets it.
• Tests: test/notify-test-send.test.ts covers off, sent, refused, a throwing sender and the 30-second limit. It also drives t in the terminal with a fake sender, checking both toasts and that the path never appears on screen. I did not run the tests without the change to confirm they fail.

Left out: MCP notify and docs/MCP.md, as the issue asked.

Seam you might trip over: the screen's sender is a swappable testSender.current, so the test can fake it. The t press when no URL is set does nothing rather than toasting.

To try it, open Phone notifications from the palette, press s to set an https URL, then press t.

Closes #8081

The notify screen in the terminal now has t "send a test", which posts one line to the saved URL and toasts whether it arrived. bun scripts/gate.ts, bun x tsc --noEmit, and bun test on test/notify-test-send.test.ts, test/tui-notify.test.ts and test/mcp-size.test.ts all pass. I did not run the full suite or design-lint.

• sendTest: sendTest(db, userId, sender = post) in src/crew/notify.ts sends Test from the forge — notifications reach you. through the existing Sender, so it goes through outboundFetch (https only, no redirects). It answers sent, refused or off, never throws, and never logs the URL.
• t key: src/tui/screens/notify.ts shows t only when a URL is set. The toast is sent to <host>, or <host> did not take it in the danger tone. The toast carries only the host.
• Rate limit: claimTest allows one test per user per 30 seconds, kept in memory. A second press shows just sent — wait a moment and sends nothing. Because it is in memory, a restart resets it.
• Tests: test/notify-test-send.test.ts covers off, sent, refused, a throwing sender and the 30-second limit. It also drives t in the terminal with a fake sender, checking both toasts and that the path never appears on screen. I did not run the tests without the change to confirm they fail.

Left out: MCP notify and docs/MCP.md, as the issue asked.

Seam you might trip over: the screen's sender is a swappable testSender.current, so the test can fake it. The t press when no URL is set does nothing rather than toasting.

To try it, open Phone notifications from the palette, press s to set an https URL, then press t.

I made no code change for this failure. I pushed an empty commit to re-run the check, so the new run is pending and I haven't seen its verdict.

• The failure: the two failing tests, "MCP backups > a listing that fails…" and "MCP backups_test > an unreachable one says why…", hit their 20-second timeouts. The log also shows two other shards killed for running long, so the machine was under load.
• Locally: all 18 tests in the three test/mcp-backups*.test.ts files pass here (16 s).
• Why I don't think my change caused it: it only touches src/crew/notify.ts, src/tui/screens/notify.ts and test/notify-test-send.test.ts. None of these is imported by the backups code or its tests.
• If it comes back red: these two tests look flaky under heavy shard load, and a person should look at those two tests rather than at this pull.

The two failing tests were slow, not wrong, and they had nothing to do with the notify screen. I fixed the cause and pushed. The forge's check will re-run on this push.

Cause. MCP backups and backups_test both list an unreachable S3 endpoint. That went through the snapshot store's five attempts, with waits of 0.5, 1, 2 and 4 s between them, so each test took about 8 s on its own. Under shard load that went past the tests' 20 s timeout.

Fix. s3Store(target, { quick: true }) gives up after two attempts, with a 200 ms wait. Two read-only probes now use it:

• the backups MCP tool, through a new quick field on Sources;
• testTarget, which is the Backups page's test button and the backups_test tool.

Snapshots, the mirror and the restore drill keep the full five attempts. I left the tests unchanged.

Checks.

• bun x tsc --noEmit passes.
• The two MCP backups test files plus notify-test-send pass: 15 tests in 2.3 s. The two backups files used to take about 16 s.
• scripts/gate.ts printed nothing, so there was nothing to fix.
• I didn't run scripts/fast.ts's suggested files: it named 1135 of 1782 files and put the run at about 99 minutes. The forge runs the full check on the push.

Not done. A real S3 outage now shows up in those probes after two attempts instead of five. I chose that on purpose, because a status read shouldn't wait out a retry schedule built for uploads.

The notify-screen change from the earlier commit is untouched: t sends a test push and toasts whether it arrived.

All three points are addressed and pushed. This pull is back to the notify test push only.

• S3 change dropped. src/snapshot/store.ts, src/snapshot/destination.ts and src/http/mcp/tools/backups.ts are restored to their earlier state. The two MCP backups tests take about 8 s each from retry waits and timed out at 20 s under shard load. They can fail again on this pull's check. A fix with a fast store injected into those tests belongs in its own pull, and I have not opened it.
• lastTest eviction. claimTest now deletes expired entries before it checks the slot, so the map holds at most the users who sent a test in the last 30 s.
• Header comment. The header in src/tui/screens/notify.ts is re-wrapped.

bun x tsc --noEmit and test/notify-test-send.test.ts pass (3 tests). I did not run scripts/fast.ts or the wider suite here, because it named about 1135 files last time; the forge runs the full check on the push.