I agree with your opinion - user setting should be left untouched. For me, the update quite works. For updater I have configured user.lua (to keep alive my custom packages), and it stays not oweritten by update.
I found a few files on /etc/config been different against update, but updater/opkg works fine, it informs me that files are different, and place new files as (example): /etc/config/system-opkg.
I just review changes, nothing important, and delete -opkg files. ucollect and resolver was interesting - I dont use any custom VLANs (running default), fortunatelly I didnt use ucollect at all:
ucollect (3.5.3):
config interface
option ifname 'eth1'
ucollect-opkg (3.6)
package 'ucollect'
config interface
option ifname 'eth0.2'
Resolver’s new options are
option static_domains '1' option dynamic_domains '0'
and I really missing basic documentation for config on Kresd docs site.
P.S.: I dont use automatic updater. I just enable it for a few moments, then run updater.sh, and then disable again. I watching news on forum, also opkg update + opkg list-upgradable is sufficient enough to make decision, when perform update.
P.P.S.: I have this in updater config, maybe thats the thing, that makes my updates non-problematic:
config override 'override'
option disable '1'