Recovery path when a UNO Q will not boot or App Lab cannot see it: cables and udev first, then Emergency Download Mode and Arduino Flasher CLI `flash latest`.
How to reinstall the UNO Q Debian image when the board still talks to App Lab, using the built-in flasher, with a clear warning that this is not the same as uploading a sketch.
Why UNO Q and VENTUNO Q run a Linux operating system, how that differs from uploading a sketch, when to reflash, how App Lab's flasher compares to Arduino Flasher CLI, how to recover a UNO Q that will not boot, and why VENTUNO Q follows a different procedure.
How to turn Arduino CLI compile checks into a small pipeline: compile on pull requests, save hex artifacts, optionally lint, and keep flashing boards as a local or tagged-release step, not something GitHub-hosted runners can do without hardware.
Duplicate an official Blink example in Arduino App Lab, read main.py and sketch.ino, change the Bridge call, Run, and know how to get back if IDE 2 overwrote the microcontroller.
