@greptileai

Greptile Summary

This PR fixes a runtime panic caused by OpenAPI path parameters with dashes (e.g. addressing-identifier) being passed as-is to Go's net/http ServeMux, which requires wildcard segment names to be valid Go identifiers.

Key changes:

• Introduces SanitizeGoIdentifier (replaces illegal runes with _, intentionally does not prefix Go keywords) extracted from the existing SanitizeGoIdentity.
• SwaggerUriToStdHttpUri now sanitizes each wildcard name via SanitizeGoIdentifier.
• The stdhttp middleware template uses the new SanitizedParamName() method for r.PathValue() calls while preserving the original ParamName in error messages.
• Adds an integration test in internal/test/server-specific/stdhttp/ that exercises the dashed-param scenario end-to-end.

The core fix is correct and well-structured. Two things worth attention:

• Name-collision risk: two OpenAPI parameters whose names differ only in illegal characters (e.g. my-param and my_param) will sanitize to the same string. ServeMux panics at startup when a pattern contains duplicate wildcard names; this edge case is currently undetected during code generation.
• SanitizeGoIdentifier lacks direct unit tests: it is only covered indirectly through SwaggerUriToStdHttpUri, making future regressions harder to catch.

Confidence Score: 4/5

• Safe to merge; the core fix is correct and well-tested, with one edge-case collision risk that is unlikely in real-world specs.
• The fix correctly addresses the reported panic, the template changes are minimal and accurate, and an integration test validates the happy path. The score is 4 rather than 5 because of the unhandled sanitization-collision edge case (duplicate wildcard names causing a ServeMux panic) and the absence of direct unit tests for the new SanitizeGoIdentifier helper.
• pkg/codegen/utils.go — the SwaggerUriToStdHttpUri sanitization logic and the new SanitizeGoIdentifier function.

_{Last reviewed commit: 730c94f}