Well, no help from anyone, but I thought I’d report back in case anyone else runs into the issue.
The problem seems to be the difference between the Site Address (URL) and WordPress Address (URL). Originally, I didn’t change the latter because of scary warnings. But, when I updated that to match the updated Site Address, the encoding issue went away.
Hope someone else finds this useful in the future!
