test(benchmark): tighten the relative gate to the measured speed

After #302, the development machine's protocol takes about 41 seconds
instead of 232. The budget multipliers now add about 1.5 times headroom
to the new ratios (0.1 for typed obligations, which leaves room for
runner jitter), and the hang guard drops from 600 to 240 seconds, with
a 210-second test timeout: about three times the expected run on
srvhome, which is about 1.9 times slower than nessar-desktop.

Part of #286 and #302. The gate still needs a passing CI benchmark on
two runners.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

.gitea/workflows/ci.yml

@@ -107,7 +107,7 @@ jobs:
             - run: bun install --frozen-lockfile
             - run: bun scripts/generate-langs.js
             - name: Benchmark protocol with relative gate
-              run: timeout 600s bun test src/app/benchmark --timeout=600000
+              run: timeout 240s bun test src/app/benchmark --timeout=240000
 
     build:
         name: build