{"version":"2.1.280","anchor":"process-spawn-telemetry-gains-stdoutstderr-chunk-validation","canonical_anchor":"process-spawn-telemetry-gains-stdoutstderr-chunk-validation","heading":"Process-spawn telemetry gains stdout\/stderr chunk validation","tier":"internal","area":"Telemetry","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/process-spawn-telemetry-gains-stdoutstderr-chunk-validation","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Process-spawn telemetry gains stdout\/stderr chunk validation\n\nProcess-spawn telemetry now validates the shape of each stdout\/stderr chunk it records\n\n**What**\n\nThe telemetry for the `process.spawn` event, which records when Claude Code launches a subprocess, now checks that each output chunk it captures has a valid shape: a `stream` field that is either `stdout` or `stderr`, and a `text` field that is a non-empty string. If a chunk doesn't match, an error label is surfaced instead.\n\n**Why**\n\nThis catches malformed process output data at the telemetry layer, helping ensure spawn-related telemetry stays reliable rather than silently recording broken entries.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}