With send and backfill now running server-side (#48), the CLI no longer sees their progress/retry events — e.g. send FLOOD_WAIT retries and backfill progress happen on the server and never reach the user's terminal. logSendRetry (which logged retries on stderr during in-process sends) is now dead code. This loses transparency.
Goal: stream server-side events (send retries, backfill progress, rate-limit waits) back to the invoking CLI so the user sees what's happening — respecting --quiet and --json. E.g. a stream/SSE on the control channel, or an event feed the foreground command tails.
Remove the dead logSendRetry (+ its test) as part of this, or before.
Refs: core/control-server.js, core/control-client.js, core/operations.js (send), core/command-context.js.
With
sendand backfill now running server-side (#48), the CLI no longer sees their progress/retry events — e.g.sendFLOOD_WAIT retries and backfill progress happen on the server and never reach the user's terminal.logSendRetry(which logged retries on stderr during in-process sends) is now dead code. This loses transparency.Goal: stream server-side events (send retries, backfill progress, rate-limit waits) back to the invoking CLI so the user sees what's happening — respecting
--quietand--json. E.g. a stream/SSE on the control channel, or an event feed the foreground command tails.Remove the dead
logSendRetry(+ its test) as part of this, or before.Refs:
core/control-server.js,core/control-client.js,core/operations.js(send),core/command-context.js.