Input Sanity Checks Land After XSLT Gunk-Up
A bug spotted this morning traced back to a validation gap: input encoding checks didn't account for unusual character sets, allowing data to pass parsing and storage while later fouling the XSLT processor. The fix tightens the node addition pathway with stricter sanity checks on all inbound content.
As a side effect, these checks now enforce well-formed XML, catching structural slip-ups such as improperly nested closing tags before they reach downstream stages.
