Perf regression: antiforgery-generation, fortunes_ef

| Scenario | Environment | Date | Old RPS | New RPS | Change | Deviation | StDev | Dependencies |
| -------- | ----------- | ---- | ------- | ------- | ------ | --------- | ----- | ------------ |
| antiforgery-generation [Fixed] | Antiforgery Token Generation 8- Trends gold-lin | 08/18/2026 12:55:48 | 335,096 | 294,625 | -12.08 % (-40,471) :thumbsdown: | -3.37 σ | 12,001.19 | Changes NameVersionDiff |
| fortunes_ef | Fortunes Platform EF 14- Trends Database cobalt-cloud-lin-azl3 | 08/17/2026 23:03:51 | 38,121 | 33,405 | -12.37 % (-4,716) :thumbsdown: | -5.63 σ | 837.78 | Changes NameVersionDiff |

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

@sebastienros

Start with the antiforgery-generation and fortunes_ef scenarios in the benchmark report, then inspect the linked PowerBI Dashboard for the run details and dependency changes. Compare the reported old and new RPS values and identify the change responsible for the regression; done means the cause is isolated and benchmark results no longer show the regression.

Written by the indexing model from the issue text.