Copy/home coin section

[sejhere]

Adds a new "The coin" section to the Home page, between Why
Quantus and The Ecosystem. Three columns in the same card
pattern as the wallet MoneySection, with an expanding divider
matching the neighbouring sections.

Copy comes from Jangle's Notion comments, with QUAN swapped to
QTC throughout.

Two commits:

1. The coin section — CoinSection.astro, ten home.coin.* keys
   across all nine locales, wired into both index pages.
2. SolutionSection typewriter timings, CHAR_DELAY 28 to 14ms,
   pre-delay 1500 to 400ms, eyebrow fade 900 to 300ms. The
   animation runs on wall-clock time while the reader is on
   scroll time, so on longer locales it was still typing after
   the section had scrolled past. Not part of the new section,
   but it sits directly above it.

Locale keys 629 -> 639, exact parity across all nine.
astro build passes.

Note: the "35+ chains" claim in column two has no whitepaper
backing, it exists only in Notion copy. Flagging since the rest of the copy follows
the whitepaper.

format:check fails as it already does on main (CRLF vs LF).

[n13]

Reviewer model: GPT 5.6 Sol

Verdict: REQUEST_CHANGES — the section implementation is sound, but the public launch-availability claim is not currently substantiated.

Blocking finding

• [High] Do not publish QTC availability across 35+ chains before a QTC route is live — website/src/i18n/en-US.json:260 (and the equivalent copy in all eight translated locale files). The new copy says QTC “is reachable from 35+ chains at launch.” NEAR Intents' current first-party overview reports 34 supported chains, while its documented live 1Click token endpoint currently returns assets across 35 chain identifiers but contains no QTC, QUAN, or Quantus asset. The existence of supported source chains does not by itself make QTC swappable from them; without a listed QTC asset, liquidity, and a successful quote/settlement path, this homepage statement is not presently true. Please verify an end-to-end QTC route and use its actual supported count, or remove/qualify this claim in every locale until that integration is live. Sources: https://intents.near.org/overview and https://1click.chaindefuser.com/v0/tokens.

Validation

• git diff --check 45bde265...37c6716e — passed.
• bun test — 22 passed, 0 failed.
• bun run build — passed; 1,444 pages built.
• Locale parity/validity check — all nine locale files have the same 639 scalar keys and ten valid home.coin.* entries.
• Headless Chromium rendering — desktop, 769px tablet, and 375px mobile checks across all nine locales found no overflow inside the new section, no runtime/console errors, and a working divider/link.
• Focused Prettier check flags SolutionSection.astro and zh-CN.json; both files already fail the same check at the base revision, so this is not introduced by the PR.

No other blocking findings found.

[sejhere]

Copy revised. The 35+ chains claim is gone entirely, and the
availability column is now qualified as coming soon.

[sejhere]

Copy revised. The 35+ chains claim is gone entirely, and the
availability column is now qualified as coming soon.

[n13]

Reviewer model: GPT 5.6 Sol

Verdict: APPROVE — the previous launch-availability blocker is resolved, and no blocking findings remain.

The new head removes the unsubstantiated 35+ chains claim and qualifies QTC acquisition as coming soon in all nine locales. I reviewed both the full base-to-head diff and the incremental ad5174e copy revision; the component wiring, translation-array rendering, responsive styling, and faster typewriter sequence are consistent with the surrounding implementation.

Validation

• git diff --check 45bde265...ad5174e — passed.
• bun test — 22 passed, 0 failed.
• bun run build — passed; 1,444 pages built.
• Locale parity/shape check — all nine locale files have the same 638 leaf key paths, and every home.coin.cols.pq.body value is a three-string array.
• Built-output check — all nine homepages contain one coin section, three columns, three post-quantum lines, the mining link, and no untranslated home.coin.* keys.
• The focused Prettier check still reports SolutionSection.astro and zh-CN.json from the base revision; five additional locale files differ only in whether the new three-item arrays are collapsed onto one line. This is non-functional and the repository-wide formatter check already fails on the base.
• GitHub reports no check runs for the current head; local validation above is therefore the available automated evidence.

No blocking findings found.