Good documentation around how proprietary software behaves so it can be troubleshot (in the automotive field this already exists, they don't give you raw source

Good documentation around how proprietary software behaves so it can be troubleshot (in the automotive field this already exists, they don't give you raw source code but they give you the exact sequence of operations under which a trouble code is set - for example, "this DTC is set if the battery voltage goes below 11V for 2 seconds" or oscilloscope waveforms of raw sensor signals) and a ban on bullshit restrictions in the name of "security" such as the binding of Touch ID buttons to the mainboard.