@greptileai

I've basically rewritten this PR as an additional commit. Thanks for submitting this ages ago, and sorry for such a long delay.

Greptile Summary

This PR fixes issue #1726 by teaching the code generator to escape literal : characters in OpenAPI paths for the three routers that use : as a path-parameter delimiter — Echo, Gin, and Fiber v2/v3. Without this, two paths sharing a prefix but ending in different literal-colon segments (e.g. /pets:validate and /pets:generate) would collide on the same :param slot and only the first registered route would ever match.

• A new escapeLiteralPathColons helper is added to utils.go and called at the start of SwaggerUriToEchoUri, SwaggerUriToFiberUri, and SwaggerUriToGinUri, replacing every literal : with \\: before path-parameter substitution introduces its own :param delimiters. The fiber-v3 template is also fixed to pass the path through toGoString (like the other backends already did), so the backslash is correctly double-escaped in the emitted Go source.
• New per-backend generated fixtures and an integration test in internal/test/paths/ confirm that each affected router dispatches the two colon-suffixed routes to their respective handlers independently. The existing path_edge_cases directory is relocated from parameters/ into the new paths/ top-level category.

Confidence Score: 4/5

The core fix is well-scoped and correct — existing paths without literal colons are unaffected, and paths with colons were already broken before this change, so there is no regression risk.

The escapeLiteralPathColons logic is order-safe and well-tested. The fiber-v3 template correction addresses a pre-existing gap. All three affected router converters are updated consistently, and Iris is correctly left alone since it uses {} not : for path parameters. The only concern is the test directory reorganization, which creates an unofficial top-level category.

The internal/test/paths/ directory and its relocation of parameters/path_edge_cases/ deserve a second look to confirm the team is comfortable with the new category name.

Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 1
internal/test/paths/doc.go:1-10
**New `paths/` category not in established test structure**

The repository organises `internal/test/` into a fixed set of top-level categories (e.g. `parameters/`, `servers/`, `schemas/`, …); `paths/` does not appear in that list. The new colon-routing tests are about server route registration, so `internal/test/servers/` is the most natural home. A sibling directory there (e.g. `servers/colon_paths/`) with per-backend config files would fit the established structure without requiring a new top-level category.

The same concern applies to the relocation of `parameters/path_edge_cases/` into this new directory. Moving an already-established leaf out of `parameters/` into an unofficial category quietly breaks the taxonomy that the rules are meant to preserve.

_{Reviews (1): Last reviewed commit: "Complete literal-colon path support for ..." | Re-trigger Greptile}