Surface reproducible competitive evidence on the organization landing page

[yhay81]

Background

The organization profile explains what Hayate is and where to start, but it does not expose the published same-workload benchmark or the dated, source-backed capability matrix. A visitor therefore has to discover the answer to “why Hayate instead of FastAPI, Django, or Hono?” indirectly.

Scope

• Add a concise “Why Hayate” section to the organization profile.
• Show the recorded 2026-07-27 same-workload startup, dependency, payload, throughput, and HTTP-contract results.
• Link the reproducible benchmark and competitive capability matrix as the authoritative details.
• State the important limits explicitly:
  • the HTTP contract is a common-workload score, not universal standards compliance;
  • Hono remains materially faster on the Node workload;
  • Django retains integrated admin/ORM/forms/template strengths;
  • Hono retains JavaScript multi-runtime and route-inferred TypeScript RPC strengths.
• Add the competitive evidence links to the documentation hub and llms.txt so both people and coding agents find the same sources.

Acceptance criteria

• Every numerical claim matches the checked-in raw/rendered benchmark evidence.
• The landing page distinguishes measured results from profile-specific capability conclusions.
• No universal-winner or all-applications claim is made.
• Benchmark and capability links are discoverable from the org profile, repository README, and llms.txt.
• Documentation link and workflow checks pass.

[yhay81]

Implemented by #18 and merged as 5a4c7ea0678dd5e4805ec2a0f933b440c1f7c6d0. The main documentation and clean-start run is green: https://github.com/hayatepy/.github/actions/runs/30239161213.