So the same CSS rules apply since otherwise I had to worry about <code id=typeans> and its various possible <span>s (which I’ve both styled). I also didn’t want any input errors to be masked for the alternate font.
At least, that seemed the most straightforward design at the time, in hindsight that original field would ofc also work.
Simply because it was (is) still accepted in the actual template. The error is only in the previewer and not enforced when saving the template. So, retrofitting it to the reviewer now will break decks for quite a few people (edit: and hence make me regret reporting this ).