Fix benchmark execution: use Maven profile instead of -Dgroups

-Dgroups=benchmark doesn't work because surefire's <excludedGroups>
takes precedence over command-line includedGroups. Added a 'benchmark'
Maven profile that overrides both <excludes> and <excludedGroups> and
sets <groups>benchmark</groups>.

Run benchmarks: mvn test -Pbenchmark (requires Docker)

https://claude.ai/code/session_01RyMeX221wTfN1atWi98YK2

Author: claude

AUDIT.md

@@ -258,7 +258,7 @@ End-to-end HTTP latency measured with `CyclesProtocolBenchmarkTest` (Spring Boot
 - Results are from a containerized CI environment (Testcontainers Redis 7-Alpine, localhost networking). Production with dedicated Redis will be faster.
 - Latencies include full HTTP round-trip: Spring Boot request handling, auth filter, JSON serialization, Redis EVALSHA, Lua execution, response building.
 - The BCrypt cache eliminates ~100ms+ from all operations after the first request per API key (60s cache window).
-- Run benchmarks: `mvn test -Dgroups=benchmark` (requires Docker)
+- Run benchmarks: `mvn test -Pbenchmark` (requires Docker)
 - Benchmarks are excluded from default `mvn verify` builds via `<excludedGroups>benchmark</excludedGroups>` in surefire config
 
 ### Production Hardening (Phase 2 audit)

cycles-protocol-service/cycles-protocol-service-api/pom.xml

@@ -94,5 +94,21 @@
                 </plugins>
             </build>
         </profile>
+        <profile>
+            <id>benchmark</id>
+            <build>
+                <plugins>
+                    <plugin>
+                        <groupId>org.apache.maven.plugins</groupId>
+                        <artifactId>maven-surefire-plugin</artifactId>
+                        <configuration>
+                            <excludes combine.self="override" />
+                            <excludedGroups combine.self="override" />
+                            <groups>benchmark</groups>
+                        </configuration>
+                    </plugin>
+                </plugins>
+            </build>
+        </profile>
     </profiles>
 </project>

cycles-protocol-service/cycles-protocol-service-api/src/test/java/io/runcycles/protocol/api/CyclesProtocolBenchmarkTest.java

@@ -18,7 +18,7 @@
  * Results are environment-dependent (CI vs local, container overhead, etc.).
  * Use these numbers as relative guidance, not absolute SLA targets.
  *
- * Run separately: mvn test -Dgroups=benchmark
+ * Run separately: mvn test -Pbenchmark
  */
 @DisplayName("Performance Benchmarks")
 @Tag("benchmark")

cycles-protocol-service/cycles-protocol-service-api/src/test/java/io/runcycles/protocol/api/CyclesProtocolConcurrentBenchmarkTest.java

@@ -24,7 +24,7 @@
  * Results are CI-environment sensitive — latency and throughput depend on
  * container resources, Redis container networking, and JVM warm-up.
  *
- * Run separately: mvn test -Dgroups=benchmark
+ * Run separately: mvn test -Pbenchmark
  */
 @DisplayName("Concurrent Load Benchmarks")
 @Tag("benchmark")