lc0, UCI compliance: no info before bestmove in certain positions

[frpays]

From http://wbec-ridderkerk.nl/html/UCIProtocol.html

• bestmove [ ponder ]
  the engine has stopped searching and found the move best in this position.
  the engine can send the move it likes to ponder on. The engine must not start pondering automatically.
  this command must always be sent if the engine stops searching, also in pondering mode if there is a "stop" command, so for every "go" command a "bestmove" command is needed!
  Directly before that the engine should send a final "info" command with the final search information, the the GUI has the complete statistics about the last search.

It happens that lc0 does not comply to this. For example when there is a direct mate.

position startpos moves h2h4 e7e5 h4h5 d7d5 h5h6 g8h6 g2g4 h6g4 f2f4 f8e7 f4e5 e7h4
go nodes 1000
best move h1h4

The UCI client may terminates the connection.

Another way to get it is to plug the 5-man tablebase and ask for a 4-man position.

position fen 8/8/8/6B1/8/8/4k3/1K5N b - - 0 1
go
bestmove e2f3 ponder g5c1```

[fli]

I've seen this happen before and I think it is only in positions where there is a single move that can be played.