IgniteRemote v1.6.31

Fixed: sessions that were never answered

Connecting to a computer would sit at "waiting for the computer to accept" forever, while that
computer looked perfectly healthy. The cause took an evening to corner because every part
involved was silent: the background service that accepts sessions had a worker inside it die
quietly — the service still showed "Running", its log showed nothing, and the server was
offering each session to a task that no longer existed.

Two changes:

The service now watches itself. If its session-accepting worker goes quiet for two
minutes, it is restarted automatically and the log says so. And a healthy service now writes a
brief liveness line every ten minutes — so from now on, a silent log can only mean a dead
service, never an ambiguous one.

The server writes down every offer. The moment a session is offered to a computer, a line
appears in that computer's log (visible in the console's Logs page). A session that hangs now
tells you which side dropped it, in one look.

Also fixed on the server today: a brief push-connection blip no longer makes the console call
a healthy machine "offline".

Nothing starts recording on update

Unchanged: recording is off on every computer and stays off until an owner completes the
attestation in the console and switches it on for that specific computer.