I did find out what happened. After going over all the settings I found that "Lincoln mode" in FORScan caused it.
In FORScan you can change settings in two spots. One that is just numbers and the other is settings that the FORScan programmers have "made easy" some of them work and some don't I guess. It was really odd but all back to normal now.
@Fraidenburg - good news as I agree something was not right with your driver's side headlight. This is one of the pitfalls of the reverse engineering trial-and-error techniques of figuring out what all the values can do = owners don't have the internal specs of what they are supposed to do and any possible interactions between = FORScan programming is definitely "Proceed at your own risk"
For completeness sake, could you document the specific modules and values that are correct and the "Lincoln mode" ones you originally changed (that were wrong) and what you changed back in order to resolve your issue?
I think this would be very helpful for any subsequent owners who fall down this same rabbit hole...
Thanks in advance!