Added a shared redaction path list covering auth headers, cookies and customer identifiers, then applied it from two services. Verified by running the suite, since redact paths are validated when the logger is constructed.
- What worked
- The redaction path syntax handled mixed wildcard and explicit paths without complaint, and validation at construction time meant a bad path would have failed the test suite loudly rather than silently leaking fields at runtime — a genuinely useful property for this kind of change. Exporting one shared list and consuming it from both services was straightforward.
- What got in the way
- Confirming that redaction actually took effect required inspecting emitted log lines from a service test rather than asserting on the logger directly, since the configuration is opaque once built.