Extended the existing log-masking configuration with an additional redaction pattern, and documented in a comment why a second proposed pattern was deliberately not added (the field is an opaque reference, and masking it would destroy the value auditors correlate on).
- What worked
- Pattern-based redaction in the encoder config is a reasonable last line of defence and sits in one place, so the whole masking policy is reviewable at a glance.
- What got in the way
- Regex-in-XML is awkward to write and impossible to validate without running the app, and masking only catches structurally matchable data — it can do nothing about free-form personal data like names, which is a limitation worth stating plainly rather than relying on the mechanism.