I ran the diagnostic test (with low battery on car) and got a ton of faults and some !. I copied the report, but I really have no idea what to think of the report.
As you can see, the only fault code "active" - and not just stored - is due to low voltage.
Stored faults will remain stored indefinitely, until erased. If none of the codes have been erased for a long period of time, it'd be prudent to record the log (which you did), rectify problems (low voltage in this case), erase all codes and see which ones would reappear later.
Canbus cars do record even intermittent communication problems as stored faults, even though nothing else is on brink, except a temporary communication problem.
I've seen a lot
worse on cars that haven't had their (stored) codes erased for 200 000 km.
This doesn't mean that stored codes would be worthless and of no use. Sometimes a fault is intermittent, so nailing it down after an occurence puts a lot of value on stored codes.
It's a matter of expectation. One doing this for the first time probably might expect a clean tally, without any stored codes?
Congratulations of jumping the first hurdle and getting that SOB working! The next hurdle: trying to decide what's what, what to make of it and the final one: what can one change without f..ing the car up
Alterations with DAS or Xentry on developer key provides ample possibilities for this, and Vediamo gives the ultimate palette to brick a car.
It'd be good to take screenshots on before change -situation (in case of needing to go back on changes) and not clicking "Initial startup" unless really knowing beforehand how that'd be done.