[不要自动merge] fix(site): halve the leaderboard title and anchor its info toggle

[ktwu01]

Issue #313. The 48px uppercase heading was the largest object on the page and compressed the ranking it names; worse, the wrapped title filled its whole max-width box, so the blue (i) rendered hundreds of pixels away with no anchor. Half scale fits the title on one line, letting flexbox place the toggle immediately after the last glyph, and flex-wrap stacks them on narrow screens instead of drifting.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-13T06:48:09.960381Z	f0f1641	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[ktwu01]

Thanks for preserving this fix. Current already contains the #313 behavior: the heading row wraps, and both leaderboard headings use the reduced scale with the info control anchored in the same flex row.\n\nMerging this older branch now produces conflicts in the stylesheet and leaderboard test file. Since the requested behavior is already live on , I recommend closing this PR as superseded rather than resolving and merging it.

[ktwu01]

Formatting correction to my comment above:

Current main already contains the #313 behavior: the heading row wraps, and both leaderboard headings use the reduced clamp(1.25rem, 2vw, 1.5rem) scale with the info control anchored in the same flex row. Merging this older branch now produces conflicts in the stylesheet and leaderboard test file.

Since the requested behavior is already live on main, I recommend closing this PR as superseded rather than resolving and merging it.