We should be able to check for the completion of implicit batch writing

Once we enableBatch(...), the BatchProcess can retry failed writing on some kind of error. The process may repeat forever (until buffer overrun or InfluxDB client shut down). In this case as InfluxDB users we don't know if the process is finished successfully or still in progress
There should be a way to check the process status

Start by locating enableBatch(...) and the BatchProcess implementation mentioned in the issue, then trace how retries and shutdown are handled. Define the observable process states needed to distinguish successful completion, ongoing retries, and termination, and verify the behavior around failed writes and buffer or client shutdown.

Written by the indexing model from the issue text.