Perf regression: fortunes, tls-renegotiation-kestrel, updates

| Scenario | Environment | Date | Old RPS | New RPS | Change | Deviation | StDev | Dependencies |
| -------- | ----------- | ---- | ------- | ------- | ------ | --------- | ----- | ------------ |
| fortunes [Fixed] | Fortunes 19- Trends Database cobalt-hosted-lin | 07/20/2026 09:08:58 | 164,142 | 91,283 | -44.39 % (-72,859) :thumbsdown: | -3.89 σ | 18,747.22 | Changes NameVersionDiff |
| tls-renegotiation-kestrel | Kestrel Linux: TLS Renegotiation 9- Trends cobalt-cloud-lin | 07/19/2026 21:40:49 | 908 | 848 | -100.00 % (-60) :thumbsdown: | -3.81 σ | 15.75 | Changes NameVersionDiff |
| updates [Fixed] | Updates Minimal APIs 19- Trends Database cobalt-hosted-lin | 07/20/2026 09:15:34 | 18,557 | 10,435 | -43.77 % (-8,123) :thumbsdown: | -2.25 σ | 3,615.82 | Changes NameVersionDiff |

[PowerBI Dashboard](https://aka.ms/aspnet/benchmarks)

@sebastienros

No source file, test, or entry point is identified. Start by reviewing the PowerBI Dashboard and reproducing the fortunes, tls-renegotiation-kestrel, and updates benchmark scenarios; compare the old and new runs and their listed dependencies. Done means the reported regression is explained and the affected benchmark results return to expected levels.

Written by the indexing model from the issue text.