reconfigurator-cli died with an unexpected cursor error

Using reconfigurator-cli to edit blueprints from within the switch zone of an a4x2 deployment, I just saw this:

〉blueprint-save 1785a790-7d26-4ed1-91f8-720ee19f5d12 new-blueprint.json
saved blueprint 1785a790-7d26-4ed1-91f8-720ee19f5d12 to "new-blueprint.json"
Error: reconfigurator-cli: unexpected error: The cursor position could not be read within a normal duration
root@oxz_switch:/tmp# echo $?
1

There was a noticeable pause between the saved blueprint ... line and the Error line (which itself was immediately followed by the process exiting).

My gut feeling is that this might be related to a4x2 serial console shenanigans and is not really worth investigating, but wanted to note it here in case others see it (especially if anyone sees it in some other context).

Start by reproducing the blueprint-save command in reconfigurator-cli within an a4x2 switch zone, noting the pause between the save confirmation and cursor error. Compare the behavior in another context if available; the issue is done when the cursor timeout is explained or the report is confirmed as specific to the serial-console environment.