Perf regression: antiforgery-noop, json, json

| Scenario | Environment | Date | Old RPS | New RPS | Change | Deviation | StDev | Dependencies |
| -------- | ----------- | ---- | ------- | ------- | ------ | --------- | ----- | ------------ |
| antiforgery-noop [Fixed] | Antiforgery No Operation 11- Trends idna-intel-lin | 07/24/2026 10:13:46 | 136,514 | 132,426 | -2.99 % (-4,087) :thumbsdown: | -4.16 σ | 983.41 | Changes NameVersionDiff |
| json | Json Minimal APIs 11- Trends idna-intel-lin | 07/24/2026 10:10:16 | 135,846 | 128,877 | -5.13 % (-6,969) :thumbsdown: | -6.38 σ | 1,093.10 | Changes NameVersionDiff |
| json | Json Platform 13- Trends cobalt-hosted-lin-azl3 | 07/24/2026 10:17:43 | 549,629 | 446,367 | -18.79 % (-103,262) :thumbsdown: | -5.33 σ | 19,377.96 | Changes NameVersionDiff |

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

@sebastienros

Start with the linked PowerBI Dashboard and compare the antiforgery-noop and both json scenarios against the reported old and new RPS values and deviations. Identify what changed between the benchmark runs; done means the regression is explained and the affected benchmark result is restored or appropriately accounted for.

Written by the indexing model from the issue text.