Neutralize NUL bytes in StructuredFormatter log output

[groupthinking]

Escape raw NUL (0x00) so it can’t truncate structured log records and remains JSON-valid, closing the CWE-117 gap.

[linear-code]

GRV-368

[coderabbitai]

⚠️ Possible Duplicate Issue(s)

• GRV-345
• CWE-117: StructuredFormatter does not neutralize NUL (0x00) after #1270/#1255 consolidation #1421

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[github-actions]

👋 Thanks for opening this issue! It has been automatically labeled for triage.

[groupthinking]

Covered on main.

Acceptance: raw NUL (0x00) must not truncate structured log records.

logging_config.py maps ord("\\x00") → \\u0000 and test_logging_config_crlf.py asserts no raw NUL survives to the sink. Residual JSON-fallback holes were closed in #1515 (35169d387).

Closing as done.