cosec-integrationlisted

# CoSec Spring Boot Integration Make the smallest integration that fits the target application. Preserve its build tool, dependency-management style, HTTP stack, configuration format, and existing security boundaries. ## Inspect first Determine: - Spring WebFlux, Spring MVC, or Spring Cloud Gateway; add exactly the matching CoSec transport. - The CoSec version already managed by a BOM, version catalog, parent, or lockfile. Never copy a version from this skill. - Whether policies are local-only or must initialize a shared repository. - Whether Redis, OAuth, IP enrichment, tracing, OpenAPI, Kafka, or token revocation is actually required. The starter already brings `cosec-core` and `cosec-jwt`. Prefer its Gradle feature capabilities because they include the integration and its runtime dependencies: | Need | Starter capability | CoSec module | |---|---|---| | Spring MVC | `webmvc-support` | `cosec-webmvc` | | Spring WebFlux | `webflux-support` | `cosec-webflux` | | Spring Cloud Gateway | `gateway-support` | `cosec-gateway` | | Social OAuth | `oauth-support` | `cosec-social` | | Redis cache, revocation, distributed limiters | `cache-support` | `cosec-cocache` | | IP region | `ip2region-support` | `cosec-ip2region` | | OpenTelemetry | `opentelemetry-support` | `cosec-opentelemetry` | | OpenAPI | `openapi-support` | `cosec-openapi` | | Kafka audit sink | `kafka-support` | `cosec-kafka` | For Gradle, select a capability on the starter dependency: ```kotlin implementation(pla