`5x/sweep-5.md`

24 lines
# /5x sweep 5 (cap) — after 0e8aa0e, server in its own session with a signal/exit logger

## Verify (5x/out/sweep-5/)
| check | result |
|---|---|
| E2E Chromium | 19/19 (LIVE) |
| E2E WebKit (cold) | 21/21 (SNAP front → LIVE back — the camera-timeout→snap fix exercised organically) |
| E2E Firefox | 19/19 (LIVE) |
| E2E WebKit warm | 19/19 (LIVE) |
| E2E hung camera → SNAP file-input (shotAdd) | Chromium 22/22 · WebKit 22/22 · Firefox 22/22 |
| /3x `/` | M1 M2 M3 B4 PASS · generic clickthrough 7 timeouts = known launcher-overlay artifact (targeted toolbar check covers it) |
| /3x `/captures` | M1 M2 M3 B4 PASS · clickthrough 7/0 |
| — test server SIGTERM'd here (logged: `got SIGTERM` 18:16:15Z, ppid=1, ~8.4 min after start); restarted, remaining stages run on the fresh server — |
| /3x `/batch` | M1 M2 M3 B4 PASS · clickthrough 8/0 |
| /3x `/cam` | M1 M3 B4 PASS · M2 FAIL = known SSE / virtual-time-budget artifact |
| console/4xx/broken-img probe 3 engines × 4 pages | PASS |
| index launcher + toolbar clickthrough 3 engines | 33/33 PASS |
| history thumbs after scroll 3 engines | PASS |
| missing-side rule API + UI 3 engines | PASS |

Caught: **0 app defects.** Env: 5th external kill — now proven a SIGTERM from outside the process (not a crash,
not the tool's process group: the server ran in its own session). Sender not identified (checked keep-alive,
pm2-fracture-canary, orphan-session-reaper — none match). Fixes: none needed.