Interface IUploadClientChannel

The server's view of one client of the application session for what the upload service must push to it: the App's pause and resume of a file (ruling row 12 of 2026-09-24). The client stops sending the chunks of a paused file and starts again on resume; a chunk sent for a file the App has paused is answered 423 by the servlet, so the push is a courtesy that saves the round trip, never the guard.

Implemented by the client-session-level upload channel of the JS transport order (A1), which registers itself with AppGyroFileUploaderService.addClientChannel when its client session is created and removes itself when that session is disposed of. A channel registered while files are already paused by the App is told about each of them at registration, so a reconnecting client learns what it must not send. The client's own pauses are never echoed back to it.

Called on the thread the pause or resume happened on (the App's worker for a call on the reservation, a timer thread for none: timers cancel, they never pause), never on the servlet thread; the implementation posts to the client as it sees fit.