Greptile Summary

This PR fixes issue #2383 where typed context keys for security schemes broke context.Value lookups across packages when a scheme was $ref'd from an import-mapped spec. The fix makes each referencing package emit a constant alias (BearerAuthScopes = externalRef0.BearerAuthScopes) instead of declaring its own context key type, so the key's identity is shared. Constants are now derived from components/securitySchemes rather than operation security requirements, enabling specs with no paths to export constants that other packages alias.

• GenerateConstants now accepts *openapi3.T (was []OperationDefinition) and iterates components/securitySchemes, calling importedSecuritySchemeScopes to determine whether to emit a local typed constant or a package-qualified alias.
• schema.go introduces SecuritySchemeProvider with an ImportedScopes field; constants.tmpl branches on it to choose the correct declaration form.
• enable-auth-scopes-on-context is now formally marked Deprecated in both the Go doc comment and the JSON schema; both must be enabled (referencing package and referenced package) for the aliasing to work.

Confidence Score: 3/5

The change correctly fixes cross-package context key sharing, but it breaks the exported pkg/codegen API surface in two places that direct library consumers will hit at compile time.

The algorithm and generated output are correct, and the test coverage across unit and integration tests is thorough. However, GenerateConstants is an exported function whose parameter type changed from []OperationDefinition to *openapi3.T, and Constants.SecuritySchemeProviderNames was renamed to SecuritySchemeProviders — both without a prior deprecation notice. Any downstream tool or plugin that imports pkg/codegen and calls either of these will fail to compile. The template data model also changed in a way that silently breaks custom constants.tmpl overrides.

pkg/codegen/codegen.go and pkg/codegen/schema.go carry the exported API changes that affect direct library consumers.

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

---

### Issue 1 of 2
pkg/codegen/codegen.go:1043-1063
**Breaking signature change to exported `GenerateConstants`**

The function signature changed from `GenerateConstants(t *template.Template, ops []OperationDefinition)` to `GenerateConstants(t *template.Template, swagger *openapi3.T)`. Any external code that imports `pkg/codegen` and calls `GenerateConstants` directly (e.g. custom codegen plugins or wrappers) will fail to compile after this change. Similarly, `Constants.SecuritySchemeProviderNames []string` was renamed to `Constants.SecuritySchemeProviders []SecuritySchemeProvider` in `schema.go`, breaking any external code that constructs or reads `Constants` by field name.

Both are exported symbols with no prior deprecation notice. If there are known external consumers of this API surface, a compatibility shim or a CHANGELOG note is worth adding; if `pkg/codegen` is intentionally considered an unstable API, a comment or doc update would prevent future confusion.

### Issue 2 of 2
pkg/codegen/templates/constants.tmpl:1-11
**Template override users need to migrate to `.SecuritySchemeProviders`**

The data passed to this template changed from `.SecuritySchemeProviderNames` (a `[]string`) to `.SecuritySchemeProviders` (a `[]SecuritySchemeProvider`). Any project that has overridden `constants.tmpl` via a custom template directory will get a silent empty output (the range loop iterates over a nil/zero-value field) rather than a compile error, potentially hiding the generated constants entirely.

_{Reviews (1): Last reviewed commit: "Share security scheme context keys acros..." | Re-trigger Greptile}