From fc41d84c44f7e499180f0c553ddfb0018df6e844 Mon Sep 17 00:00:00 2001
From: Flotapponnier <160007691+Flotapponnier@users.noreply.github.com>
Date: Wed, 30 Sep 2026 14:17:43 +0200
Subject: [PATCH] the tier selector reads its label from the spec, so a cost
 bench stops saying "Access"

`dimension_labels` landed with the zero-is-a-value work and every axis
reads it except the one that motivated it: venue, bucket, kind, chain and
region all do `dimensionLabels?.<key> ?? "<stock>"`, while the tier row
hardcoded "Access".

benchmarks/rpc-cost.yml declares `tier: Billing model` and its tier axis
is usage / dedicated / reference ("Billed per request", "Dedicated
capacity", "Free public, not ranked"). "Access" is the wrong word for
that axis: on rpc-cost the plan band is the `venue` axis, not this one.
The page rendered "Access" sixteen times against a spec that had already
written the right label.

One line, same shape as the five axes beside it. rpc-cost is the only
spec in the tree that declares `dimension_labels.tier`, so the nine chain
RPC benches keep "Access", which is correct for them: there the tier axis
really is public against API-key.

typecheck and eslint clean.
---
 src/components/benchmark-body.tsx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/components/benchmark-body.tsx b/src/components/benchmark-body.tsx
index ff1d55ee8..08932658c 100644
--- a/src/components/benchmark-body.tsx
+++ b/src/components/benchmark-body.tsx
@@ -817,7 +817,7 @@ export function BenchmarkBody({
         <div className="mt-8 space-y-3">
           {tierOptions.length > 0 && (
             <DimensionRow
-              label="Access"
+              label={dimensionLabels?.tier ?? "Access"}
               options={tierOptions}
               selected={tier ?? headlineTier}
               onSelect={setTier}