fix: add min-threshold to baseline comparison CI test

The baseline comparison test was failing intermittently because:
- Fast policies (~200µs) showed large percentage swings (72%)
- Absolute differences were small (~170µs) - normal CI variance
- 50% threshold alone couldn't account for this

Adding --min-threshold 500µs ensures regressions only fail when BOTH:
1. Percentage exceeds threshold (50%), AND
2. Absolute time exceeds min-threshold (500µs)

This is exactly the scenario min-threshold was designed to handle.

Signed-off-by: Sertac Ozercan <[email protected]>

Author: sozercan

.github/workflows/test-gator.yaml

@@ -123,12 +123,14 @@ jobs:
             --iterations 30 \
             --save /tmp/baseline.json
 
-          # Compare against baseline (should pass with 50% threshold)
+          # Compare against baseline with min-threshold to handle CI variance
+          # Fast policies (~200µs) can show large % swings from small absolute changes
           ./bin/gator bench \
             --filename test/gator/bench/basic/ \
             --iterations 30 \
             --compare /tmp/baseline.json \
-            --threshold 50
+            --threshold 50 \
+            --min-threshold 500µs
 
       - name: Test min-threshold
         run: |