nessarandClaude Sonnet 5.5 b37101435a test(benchmark): calibrate again after the protocol and judge against the slower value ...

The relative gate calibrated once before the scenarios, so load that
started afterwards (the push and pull_request runs of one commit overlap
on the same runner, next to the test, build and image jobs) slowed the
scenarios but not the yardstick. A pull_request run failed `two years`
at 1653.1 ms against a 1648.7 ms budget this way.

The spec now repeats the calibration after the protocol and uses the
slower of the two values. The budgets can only loosen, never tighten,
and the log reprints the table with the budgets actually applied when
they change.

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

2026-10-19 10:11:26 +02:00

..

adr

perf(planning): plan from the best-ranked obligation solution

2026-10-18 21:18:06 +02:00

agents

docs: migrate repository guidance to Gitea

2026-10-13 19:38:32 +02:00

benchmark

test(benchmark): calibrate again after the protocol and judge against the slower value

2026-10-19 10:11:26 +02:00

research

feat: enhance documentation for leave planning concepts and solver recommendations

2026-08-28 17:00:12 +02:00

bun-adoption.md

fix: report line-only coverage honestly and tighten Bun test helpers

2026-10-17 16:10:29 +02:00

gitea-actions.md

test(benchmark): calibrate again after the protocol and judge against the slower value

2026-10-19 10:11:26 +02:00

planner-cancellation.md

fix(planning): keep counterfactual moves off the shared final plan

2026-10-18 21:49:55 +02:00

planning-duration.md

fix(planning): recalibrate the duration estimate to the faster engine

2026-10-18 23:31:28 +02:00

planning-objectives.md

perf(planning): plan from the best-ranked obligation solution

2026-10-18 21:18:06 +02:00

statistics.md

docs: migrate repository guidance to Gitea

2026-10-13 19:38:32 +02:00

trace-free-planning-verification.md

feat(server): serve the client-only build with Bun

2026-10-17 13:50:05 +02:00