Should there be a way to discover whether the Abstract Command has finished successfully if abstractcs.cmderr == busy?

[en-sc]

The specification states in [3.7. Abstract Commands]:

If the debugger starts a new command while busy is set, cmderr becomes 1 (busy), the currently executing command still gets to run to completion, but any error generated by the currently executing command is lost.

AFAIU, this presents an issue when accessing non-idempotent memory. When abstractcs.cmderr == busy after the access there is no way to know whether the access has actually succeeded. Should there be a way to address this?