Droidsmith today: trust boundaries and a device corpus

[SysAdminDoc]

Droidsmith is a cross-platform GUI for managing Android devices over ADB, built with Tauri so it stays light.

Recent work has been about trust boundaries and testing. The privileged command boundary got split out so the parts that touch your device are isolated from the parts that draw the interface. There's now a versioned corpus of real ADB transcripts backing the tests, which means device quirks get captured once and guarded forever instead of regressing quietly. Public release upgrades are preserved, so updating doesn't reset your workspace.

On the roadmap: scrcpy encoder-constraint recovery for the screens that refuse the default encoder, and a consolidation pass on the workspace visual system.

The thing I can't test from here is your device zoo. Samsung, Pixel, Xiaomi and the rest each have their own ADB personality, and the thread pinned alongside this one is for reporting what works and what chokes on your hardware. Bugs with logs go to Issues.