#3833 telemetry stats says "No telemetry data found" right after successful sends; say the spool is empty because it flushed

After about forty CLI invocations in one session on 20261020.024627.0-sha.26dc044f (macOS 27), all of which reached the account's public combat log, swamp telemetry stats prints only [INF] telemetry·stats: No telemetry data found. and ls ~/.config/swamp/telemetry is empty. That is correct by the documented lifecycle (/manual/reference/usage-telemetry-events, Local spool: a sent entry is removed immediately), but to a user checking what left the machine the line reads as "telemetry is off" or "nothing was recorded".

Expected: stats distinguishes "nothing recorded" from "everything sent", for example Spool empty: last flush succeeded at <time>, N entries sent in the last 2 days, and mentions telemetryKeepFlushed as the way to keep entries for inspection. Actual: one line, No telemetry data found., whether telemetry is disabled, never ran, or flushed successfully a second ago.

Steps to reproduce:

1. With telemetry enabled and network access, run any few swamp commands, e.g. swamp version three times.
2. swamp telemetry stats -> No telemetry data found.; ls ~/.config/swamp/telemetry -> empty.

The repository key telemetryKeepFlushed: true (.swamp.yaml only, no user-global equivalent per the usage-telemetry reference) renames sent entries to .flushed.json for two days; the bundled source reads it as keepFlushed = marker.telemetryKeepFlushed ?? false. Whether stats counts .flushed.json files when the key is on was not checked. #1129 and #1233 (shipped) documented the user-global spool and stats; neither touched the empty-state wording.

Suggestion: keep a small flush record (last attempt time, result, count) next to the spool and print it in the empty state, or at minimum change the line to name the flush and the telemetryKeepFlushed key.