Writing Defect Reports

A report is a claim, and it is read by people who will not re-derive it. The cost of an overstated one is not embarrassment — it is a maintainer spending an afternoon on a premise that does not hold, or a "fix" landing for a failure mode that never occurred. The techniques for finding a defect live in verifying-external-behavior and testing-python-libraries. This skill is about the step between finding one and publishing it.

The rule underneath all of it: publish the claim you actually measured, at the layer you measured it.

The anomaly is real; the headline may not be

The common failure is not a fabricated bug. It is a genuine internal oddity promoted one layer too far.