Here we assume that the user is aware of the implications of manually setting the robot status, and therefore we do not perform additional checks to align with ISAR. This endpoint should only be used when the Flotilla status has become misaligned with ISAR anyways.
We could also consider deleting any ongoing missions on the robot when setting it to available, but this likely won't be expected by the user of the endpoints so it is probably best to keep it simple like it currently is. If Flotilla is stuck on a mission which is not in ISAR then the user should delete the mission in Flotilla and then run this endpoint to trigger onRobotAvailable.
Here we assume that the user is aware of the implications of manually setting the robot status, and therefore we do not perform additional checks to align with ISAR. This endpoint should only be used when the Flotilla status has become misaligned with ISAR anyways.
We could also consider deleting any ongoing missions on the robot when setting it to available, but this likely won't be expected by the user of the endpoints so it is probably best to keep it simple like it currently is. If Flotilla is stuck on a mission which is not in ISAR then the user should delete the mission in Flotilla and then run this endpoint to trigger onRobotAvailable.