Integrate Oudelaa backend features, security, tests, and deployment updates

PERFORMANCE_TESTING.md

@@ -55,10 +55,36 @@ Supported options:
 - `--concurrency`
 - `--timeout`
 - `--warmup`
+- `--min-success-rate` (percentage from `0` to `100`)
+- `--min-rps` (minimum requests per second)
+- `--max-p95` (maximum p95 latency in milliseconds)
+- `--max-p99` (maximum p99 latency in milliseconds)
 - `--header "Key: Value"`
 - `--body`
 - `--body-file`
 
+### Automated performance gates
+
+Add one or more gates to turn a benchmark into a CI regression check:
+
+```powershell
+node scripts/load-test.js --url http://127.0.0.1:4000/api/v1/health --duration 15 --concurrency 20 --min-success-rate 99.9 --min-rps 1000 --max-p95 100 --max-p99 150
+```
+
+Or run the provided health baseline:
+
+```powershell
+npm run perf:health:gate
+```
+
+All configured gates must pass. The JSON summary contains the individual gate results, followed by a readable `PASS`/`FAIL` report. A performance regression exits with code `2`; invalid arguments or runtime errors exit with code `1`. Calibrate thresholds on production-like staging hardware rather than copying local numbers into deployment policy.
+
+The gate parser, evaluator, and process exit behavior have a standalone test suite:
+
+```powershell
+npm run test:perf
+```
+
 ## 5. What to watch
 
 - `requestsPerSecond`: throughput