What
Executable launch failures and subprocess init timeouts now report a structured error class, and any path in the message is scrubbed for secrets before it is interpolated.
Details
- The helper producing "executable not found / failed to launch" strings now returns an object with
telemetryMessageanderrorClass, one of "executable_launch_failed" or "executable_not_found". - Paths go through a new redaction helper applying the shared token patterns: Bearer, sk-ant-, AKIA, gh*_, JWT and others.
- Subprocess init timeouts become a TelemetrySafeError with errorClass "initialize_timeout"; the user-visible message is unchanged.
Evidence
errorClass: "initialize_timeout"
Strings lifted out of the shipped bundle, so the claim above can be checked against them.