docs: make homepage result-first with free5GC and vLLM evidence

[gthulhu-work]

Summary

Rework the Gthulhu homepage so the first screen leads with measured workload outcomes, not architecture narrative.

What changes

• add a result table at the top of the English and Chinese homepages;
• highlight the published free5GC GTP scheduling result:
  • average UE ping latency: 88.98 ms → 2.079 ms (97.66% lower)
  • maximum UE ping latency: 130.95 ms → 8.45 ms (93.55% lower)
• highlight the reproducible vLLM CPU-pressure benchmark from [Blog] Keeping vLLM Fast Under CPU Pressure: An sched_ext Scheduler for GPU Inference vllm-project/vllm-project.github.io#300:
  • baseline decode around 6–7 t/s under CPU contention
  • tg128 around 21.3 t/s with Gthulhu + tiered scheduling policy
• clearly mark the vLLM result as an upstream-reviewing community benchmark, not a generalized performance guarantee;
• move Claim2Core architecture/roadmap below the proof points instead of making it the first message visitors see.

Why

The current homepage explains the architecture well, but makes visitors understand the system before showing why they should care. This change follows the result-first style used by performance-oriented infrastructure projects and makes existing published/community evidence the primary entry point.

Sources linked directly from the homepage:

• free5GC: https://free5gc.org/blog/20251126/20251126/
• free5GC earlier case study: https://free5gc.org/blog/20250726/index.en/
• vLLM blog PR: [Blog] Keeping vLLM Fast Under CPU Pressure: An sched_ext Scheduler for GPU Inference vllm-project/vllm-project.github.io#300

[Copilot]

🟢 Approval recommended

The changes are documentation-only, the new structure matches the PR intent, and the added links/claims are consistently presented with appropriate caveats.

Pull request overview

This PR reworks the English and Chinese homepages to lead with measured, externally verifiable performance outcomes (free5GC and vLLM benchmark evidence) before introducing architecture and roadmap context, aligning the landing experience with a “results-first” narrative.

Changes:

• Added a top-of-page results table highlighting published free5GC latency improvements and a reproducible vLLM CPU-pressure benchmark (explicitly labeled as upstream-reviewing community evidence).
• Reordered homepage sections so “why it matters” + proven use cases appear before Claim2Core/architecture details.
• Refreshed the call-to-action block and consolidated the “get involved” links near the end of each page.

File summaries

File	Description
docs/index.md	Adds results-first summary table + proof points, then reorganizes homepage narrative and CTAs (English).
docs/index.zh.md	Mirrors the results-first structure and evidence links while reorganizing the homepage flow (Chinese).

Review details

• Files reviewed: 2/2 changed files
• Comments generated: 0
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.