Confidence-led concept

You are building one self-contained, fully interactive wireframe-style React
component that demonstrates a single hotel "Room Normalizer" concept.

# Concept
- Number: 10 of 14
- Section: normalizer
- Name: Confidence-led concept
- Tagline: Trust + match quality
- One-line summary: Each group leads with a confidence banner ('Same room across 6 offers · Matched across 4 rate plans') plus a meter and 'How we matched' panel.

# Framing
Directly addresses the trust problem in normalization. Surfaces match quality so users know when to trust the grouping vs. when to look harder.

# What this is
Each room group leads with a confidence banner: 'Same room across 6 offers · Matched across 4 rate plans', plus a confidence meter and an expandable 'How we matched' panel listing the rate plans collapsed into this room type.

# Why it works
Directly addresses the trust problem in normalization. Surfaces match quality so users know when to look harder vs. trust the grouping. Makes the system's reasoning legible.

# Best use case
Early rollouts of normalized inventory, lower-quality data feeds, and any context where match accuracy varies room-to-room.

# Tradeoffs / risks
If the confidence model is wrong, the banner makes the failure louder. Adds vertical space per group. Risk of users over-indexing on the meter and ignoring the rates themselves.

# UX notes (scannability · normalization · booking confidence · provider transparency)
Best concept for confidence-building. Normalization is the headline, not the substrate. Reserve CTAs remain per-row so booking velocity isn't sacrificed for trust UI.

# Visual + interaction requirements
- Wireframe fidelity: monochrome, system UI, no brand color. Use Tailwind
  utility classes only. No images. Use simple borders, muted backgrounds,
  and mono labels for meta text (uppercase, tracking-widest, text-[10px]).
- Canvas width: 764px, centered. Internal content respects that frame.
- Context: this lives inside a hotel PDP "Rooms & Rates" section. Assume
  3 normalized room types (King, Queen, Double Queen) with 5–8 bookable
  rates each. Invent realistic mock data inline — rate label, bed, meals
  (room only / breakfast included), cancellation (free until N / non-refundable),
  payment (pay now / pay at hotel), price per night.
- Fully interactive: every control the concept implies must work in-browser
  with React state only — no backend, no router. Examples: accordions expand,
  tabs filter, sort headers sort, "Show N more" reveals rows, builder toggles
  recompute price live, sticky CTAs update with selection.
- Accessibility: real <button> elements, keyboard focus rings, aria-expanded
  on disclosure controls, aria-pressed on toggles.

# Deliverable
- A single default-exported React component file using TypeScript + Tailwind.
- No external UI library. Inline any small primitives you need.
- Include the mock data inline at the top of the file.
- File should run as-is when dropped into a Vite + React + Tailwind project.

Build only this concept. Do not generate the other 13.