Enlarge reading type; add brand icons and per-run metadata chips

- Bump body text across the registry and case sections (notes, prompts,
  tabs, table cells) one size up for readability; SVG viewer no longer
  uses the full-bleed breakout and caps at a smaller height (HTML keeps
  the big frame).
- Brand icons for model, vendor and harness via @lobehub/icons-static-svg
  (zero-dep static assets; deliberately not the @lobehub/icons React
  package, whose peers pull in antd). Mono SVGs are currentColor so they
  follow the theme. Mapping lives in site/src/lib/brands.tsx, derived
  from the strings contributors already fill in models/*.json.
- Case pages now show Harness (with icon) and Effort chips next to the
  contributor chip; registry harness column is labeled 运行环境（Harness）.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

README.en.md

@@ -58,6 +58,6 @@ Contributions are data-only — no code changes needed:
 1. Artifact: `outputs/<model-id>/<case-id>.<ext>` (e.g. `outputs/gpt-5-5-pro/pelican-cycling.svg`).
 2. Registration: `models/<model-id>.json` (new file for a new combination; add to `runs` for an existing one) — see the schema example in the Chinese README.
 
-CI-enforced rules: dash-only lowercase ids matching the `outputs/` folder name; a **required bilingual provenance `note`** per run (which harness, what effort, one-shot or fixed); every declared run must have its artifact; multiple versions of the same combination x case go in an array with distinct `file` names (e.g. `pelican-cycling-2.svg`). Set `contributor` to your GitHub username — the site shows your avatar linked to your profile next to the run.
+CI-enforced rules: dash-only lowercase ids matching the `outputs/` folder name; a **required bilingual provenance `note`** per run (which harness, what effort, one-shot or fixed); every declared run must have its artifact; multiple versions of the same combination x case go in an array with distinct `file` names (e.g. `pelican-cycling-2.svg`). Set `contributor` to your GitHub username — the site shows your avatar linked to your profile next to the run. Fill in `harness` and `effort` truthfully for new combinations: the case page renders Harness / Effort metadata chips from these fields and auto-matches brand icons for the model, vendor and harness (via [lobe-icons](https://github.com/lobehub/lobe-icons)) — contributors never touch icons.
 
 PRs get data validation + a build from CI; merges to `main` deploy automatically.

README.md

@@ -82,6 +82,7 @@ bun run build    # 数据校验 + 类型检查 + 产物构建（输出到 site/d
 - 每条 run 的 `note` **双语必填**——这是本仓库的可信度来源，必须写明产出怎么来的；
 - 声明的 run 必须有对应的产出文件；
 - 同一组合对同一案例可提交多个版本：`runs.<case-id>` 写成数组，第二个版本起必须用 `file` 指定不同文件名（如 `pelican-cycling-2.svg`）；
-- `contributor` 填你的 GitHub 用户名，站点会在产出旁展示你的头像并链接到主页。
+- `contributor` 填你的 GitHub 用户名，站点会在产出旁展示你的头像并链接到主页；
+- 新组合的 `harness`（运行环境）与 `effort`（思考配额）请如实填写：站点会据此在测评页生成「运行环境 / 思考配额」metadata 徽章，并自动为模型、厂商、Harness 匹配品牌 icon（来自 [lobe-icons](https://github.com/lobehub/lobe-icons)），贡献者无需处理任何图标。
 
 提 PR 后 CI 会跑数据校验 + 构建；合入 `main` 自动部署。