[Flotapponnier]

My own defect, shipped minutes ago in #3275.

The Ethereum explainer said "across the 7 measured providers" while eleven published, so I replaced the hand-typed number with {{count:chain:ethereum}}. The renderer does not resolve that form — bench-template's CHAIN_TEMPLATE_RE takes best_name, best_p50, worst_name and worst_p50 only, and count exists for :tier: alone. An unmatched token is passed through unchanged, so the live page now reads:

across the {{count:chain:ethereum}} measured providers

A wrong number became a visible placeholder on an indexed URL, which is worse than what it replaced.

Why the clause is removed rather than fixed

Adding a per-chain count to the renderer is not cheap: the chain path has bestPerChain and worstPerChain — a single leader and trailer per chain, not the rows — so there is nothing to count.

And unscoped {{count}} is not a substitute. The Ethereum explainer renders on every tab of the bench (checked on ?chain=all, ?chain=ethereum and ?chain=bsc — present on all three), so on the BNB tab it would print 9 inside a paragraph about Ethereum. The sentence is complete without it.

The part that matters more than the sentence

validate-specs.ts already lints every placeholder, and it passed this one twice. Two holes, and the first hid the second.

1. per_chain_explainer was never in the linted field list, on any spec. The list covers subtitle, seo_*, abstract, disclaimer, findings, methodology and faq. So no token in any per-chain explainer has ever been checked — and that is the field written per chain, therefore the one most likely to carry a chain-scope mistake. Both h2 and body are linted now, and it comes back clean across all 253 specs, so this closes a hole without opening a backlog.

2. With that field linted the token still passed, because the chain branch checked only that the chain value is declared. The tier branch sitting right beside it has always also checked which keywords may carry a tier scope (cannot be tier-scoped); the chain branch had no equivalent. It does now, against a CHAIN_SCOPABLE set that names what CHAIN_TEMPLATE_RE actually resolves.

Tested by reinstating the token, not by reading the diff

The first version of this fix reported ✓ 253 specs valid with the bad token in place — which is exactly how the missing field list was found. After both changes:

✗ benchmarks/evm-quote-latency.yml: per_chain_explainer[0].body:
  {{count:chain:ethereum}} cannot be chain-scoped
1 error.

The spec file was restored byte-identical afterwards. Gates: pnpm validate 253 specs, tsc --noEmit clean, bun test src/ 719 pass.