[umbrella] Official fkst website: let fkst build its own front door (wave tracking, intake: decline)

[loning]

DO NOT auto-implement / intake: decline — umbrella/epic tracking issue only; it indexes manually decomposed waves and must not enter the autonomous dev pipeline.

Vision

This repo hosts the official fkst website (https://chronoaiproject.github.io/fkst-website/, GitHub Pages enabled, build_type=workflow): presenting the whole fkst project (three-repo ecosystem) to the world — and the site itself is developed by fkst's own autonomous pipeline. The site IS the dogfood.

Language policy: English-primary with a Chinese version (zh-en bilingual), matching the repo convention.

Content pillars:

• What it is: fkst = a fully autonomous agent-company system on the fkst-substrate engine (event flow, three-tier companies, reliable delivery, marker-as-fact, consensus gating, self-driving dev loop).
• Three repos: fkst-substrate (engine, Rust) / fkst-packages (package library, Lua) / fkst-website (this repo, library C).
• Living evidence: live board (site-board's board.json), real records of autonomous PRs/merges.

Waves (manually decomposed; open the next wave only after the previous one is verified)

• wave-1: site/ static skeleton, English-primary + zh version, + GitHub Pages deploy workflow (→ Official site wave-1: static English-primary homepage (zh version) + GitHub Pages deploy workflow #3)
• wave-2: content pages — architecture overview (engine/packages/composition model), doctrine highlights, three-repo navigation
• wave-3: live board integration (site-board snapshot published to Pages, showing the autonomous pipeline's real-time state)
• wave-4: publish automation (redeploy on merge; derive content from in-repo docs to avoid double sourcing)

Features expand at the pipeline's own pace: each wave = a tight-scope implementable issue, completed autonomously via intake → consensus → implement.

（中文摘要：官网伞 issue，英文为主中英双语，四波次人工拆解、逐波喂给自治管线。）

⟦AI:FKST⟧

[loning]

github-devloop intake decision: decline

Reason:
伞形追踪 issue，主要用于人工拆分索引，不是具体实现请求

[LoningSG]

github-devloop intake decision: track
Service class: background

Acknowledged as a tracking umbrella. Individual waves should enter the pipeline as separate issues; this issue stays open for tracking.

Reason:
Issue-triage best practice treats epics/umbrellas as tracking containers; this issue bundles "wave-1" through "wave-4" and points implementable work to "#3".