GeezerVison

Greptile Summary

This PR deprecates the legacy security-scope-on-context emission pattern — where generated server code embedded per-operation scopes into the request context via typed context keys — and gates it behind a new compatibility.enable-auth-scopes-on-context option (default off). All seven backend templates (chi, echo, echo/v5, fiber, gin, gorilla, iris, stdhttp) are updated, the configuration struct and JSON schema are kept in sync, and the fiber middleware fixture opts in to preserve an existing anonymous-alternative regression test.

• All 7 backend templates correctly guard scope-embedding behind opts.Compatibility.EnableAuthScopesOnContext; collectComponentTypes in codegen.go likewise gates GenerateTypesForSecuritySchemes; and constants.tmpl gates the scope constant block — the three emission sites are consistently covered.
• TestEnableAuthScopesOnContext verifies both opt-in and opt-out states but only for StdHTTPServer; the chi/gorilla/stdhttp templates use a structurally different guard (if and .SecurityDefinitions opts…) compared to echo/gin/iris/fiber (outer if opts…, inner range), so a backend-specific regression in the other group would go undetected.

Confidence Score: 4/5

Safe to merge; the change removes generated boilerplate that was genuinely incorrect and provides a clean opt-in path for users who depend on it.

The implementation is thorough — all seven backend templates, the type-generation path in codegen.go, and the scope-constant template are all consistently gated. Configuration struct and JSON schema are kept in sync. The only gap is that the new test only exercises the stdhttp backend; the structurally different guard pattern used in echo/gin/iris/fiber templates is not independently verified.

pkg/codegen/codegen_test.go — TestEnableAuthScopesOnContext covers only StdHTTPServer; echo, chi, gin, gorilla, iris, and fiber template guards go untested.

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

---

### Issue 1 of 1
pkg/codegen/codegen_test.go:493-514
**Test coverage limited to a single backend**

`TestEnableAuthScopesOnContext` only exercises `StdHTTPServer`. All seven backend templates (chi, echo, echo/v5, fiber, gin, gorilla, iris) had guard changes in this PR, and any future template-level regression (e.g., the `if`/`range` ordering in `echo-wrappers.tmpl`) would go undetected. At minimum, adding `EchoServer: true` as a second sub-test case (reusing the same spec) would catch divergence between the chi/gorilla/stdhttp pattern (`if and … opts.Compatibility`) and the echo/gin/iris/fiber pattern (outer `if opts.Compatibility`, inner `range`) that are structurally different in the templates.

_{Reviews (1): Last reviewed commit: "Deprecate ctx based security scopes" | Re-trigger Greptile}