[iPeluwa]

Problem

A session whose wrapper dies without a clean exit (closed terminal, killed process) stays at exitCode: -1 until the reaper finalizes it at the next session-start. But nothing flushes it afterwards: flushPendingSubmissions runs on clean ends, and a reaped session's only other trigger is another session ending cleanly. If sessions keep dying uncleanly — laptop sleep, closed tabs — reaped work sits unsubmitted indefinitely. I lost a 13-commit session this way this week.

Fix

• refreshAndReap() / reapOrphanedSessions() / refreshRecentSessions() now return how many sessions they settled.
• onSessionStart calls flushPendingSubmissions when that count is non-zero, so the session-start that reaps a session also sends it. Quiet starts still spend no time on the network.

Tests

test/flush-on-reap.test.mjs (3 cases): reap returns count and submits; clean-end re-finalize keeps momentum; no flush on a start that settled nothing.

[iPeluwa]

Closing — keeping these fixes local rather than upstreaming. Thanks!