{"version":"2.1.265","anchor":"tool-result-pairing-debug-messages-now-use-structuredredact","canonical_anchor":"tool-result-pairing-debug-messages-now-use-structuredredact","heading":"Tool-result pairing debug messages now use structured\/redacted formatting helpers","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/tool-result-pairing-debug-messages-now-use-structuredredact","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Tool-result pairing debug messages now use structured\/redacted formatting helpers\n\nTool-result pairing debug logs now numbered and formatted with redaction helpers\n\n**What**\n\nWhen Claude Code detects a mismatch between tool-use and tool-result messages (a structural check called `ensureToolResultPairing`), the debug and error messages it logs are now built differently: each message is numbered with an index, and tool-use IDs are formatted through a redaction\/formatting helper and joined with a dedicated helper function, instead of being concatenated directly into a plain string.\n\n**Why**\n\nThis makes these internal diagnostic logs more structured and consistent, and applies proper redaction formatting to identifiers that appear in them.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}