Check which commit a bug report is reading before acting on it

A detailed, well-argued defect report described a broken install path: a missing proxy route, a missing bind mount, and a misleading error suggesting sudo. Every claim was accurate about the commit it cited, and none applied to the shipped branch, because that commit belonged to a pull request that had been closed as superseded. The shipped code solved the same problem a different way -- fetching an operator-configured URL with digest verification instead of serving the file itself -- so the route and the mount it asked for should not exist at all, and the error message it criticised had already been replaced by a precise one. Acting on the report as written would have added dead configuration and re-broken a good error path. The report was still worth reading: a real adjacent gap existed, just not the one described. Before implementing any external finding, confirm which ref it was produced against and re-derive the symptom on the branch you actually ship.