feat(website): expose all ten diagram types across homepage, Start, Guide and Proof Lab #918

Problem and value

Stable 3.1.0 supports ten diagram types. Release preparation added an explicit ten-type notice so the website does not imply that selected examples are the entire product. However, the homepage still previews five modes, Start supplies six recipes/tabs, and the Guide/Proof Lab do not offer full coverage of Class, Tree, Timeline and Waterfall. A capability notice is insufficient for discovery and first use.

Scope and dependencies

Consume checked examples and canonical recipes from #916. Expand the existing homepage, Guide, Start and Proof Lab pathways; do not introduce a parallel capability registry or another generation pipeline. Keep the site’s restrained visual hierarchy and current install/discovery flows.

Acceptance

• Every supported type can be discovered from the homepage and reached through an appropriate scenario, starter prompt and checked example.
• Add Class/Tree/Timeline/Waterfall starter entries and accessible Start tabs using canonical recipes; retain ERD and legacy recipe IDs/deep links.
• Guide recommendation and initial HTML reference cover the promoted scenarios in both English and Chinese. Selective recommendation remains bounded rather than claiming every input can be automatically analysed.
• Proof Lab has working promoted-type filters/cards linked to real source/HTML/receipts, with counts derived from the checked inventory. No empty promised example or fake quality badge.
• Homepage previews are legible and explorable; explain each new type through the question it answers. No forced animation or unnecessary promotion modal.
• Source/channel/version labels follow actual release identity. Illustrative timelines/durations and conceptual schemas remain labelled.
• Verify no-JavaScript initial content, language continuity, keyboard/tab behaviour, deep links and copied prompts in real Chrome for both GitHub Pages and Cloudflare builds.
• Review matched desktop/narrow light/dark screenshots, including control overlap, long labels, scrolling and selected-type states. Record perceptual review separately from machine checks.

Keep existing public URLs, source attribution and export/install flows functional. Deliver through dev and stable promotion; do not update user installations or overwrite v3.1.0.