I don't think that's required, unless you definitionally believe otherwise.
When clients disagree about the the order of events and a conflict results then clients can be required to roll back (apply the inverse of each change) to the last point in time where all clients were in agreement about the world state. Then, all clients re-apply all changes in the new now-agreed-upon order. Now all changes have been applied and there is agreement about the world state and the process starts anew.
This way multiple clients can work offline for extended periods of time and then reconcile with other clients.
It's still early, but we have a checkpointing system that works very well for us. And once you have checkpoints you can start dropping inconsequential transactions in between checkpoints, which you're right, can be considered GC. However, checkpointing is desirable anyway otherwise new users have to replay the transaction log from T=0 when they join, and that's impractical.
As long as all clients agree on the order of CRDT operations then cycles are no problem. It's just an invalid transaction that can be dropped. Invalid or contradictory updates can always happen (regardless of sync mechanism) and the resolution is a UX issue. In some cases you might want to inform the user, in other cases the user can choose how to resolve the conflict, in other cases quiet failure is fine.
The problem for (1) is not the camera. It's very likely moisture in one of the connectors in the wiring harness in the tailgate. The fix is contact spray and taping up the connector with duck-tape. (You can test if this is the problem by opening and closing the trunk when you’re in reverse to see if that makes the video worse/better)
It’s also a multistep process with a touch screen: 1) find the button on the screen 2) lean over to reach it 3) touch it and look at it while doing so to confirm you did it right.
In a clickwheel car the wheel moves the focus rect. You twist it blindly to approximately the right spot. Then you look at the screen and adjust one or two clicks and press to confirm. You won’t trigger the wrong action by accident and the focus rect makes the operation async: you don’t have to look while you turn the wheel, you can look at the screen when it suits you.
I got a Mazda for this reason. Physical buttons for everything and carplay for navigation+spotify. Best of both worlds. Infotainment has touch screen when stationary, but while driving it can only be operated by voice and console buttons/wheel.