feat: add VitePress documentation site with GitHub Pages deployment

[Doraemonblogs]

• VitePress setup with sidebar navigation (9 sections, 37 translations grouped by source)
• Custom landing page (hero + six core concept feature cards)
• Local full-text search, dark mode, last-updated timestamps, edit-on-GitHub links
• Custom indigo theme + Chinese typography optimizations
• GitHub Actions workflow for auto-deploy to GitHub Pages
• Fix: escape raw angle brackets in inside-the-scaffold-paper-translation.md (Vue compiler compat)
• Config: base path, sitemap, social/edit links pointing to Doraemonblogs/harness-engineering

[cursor]

Thanks for putting this together. I reviewed the PR against the latest main and tested it locally: npm ci && npm run build completes successfully, and all consistency checks pass. The implementation is thoughtful, especially the source-based grouping of translations, the Chinese typography, the GitHub Pages workflow, and the fix for the raw angle brackets in works/inside-the-scaffold-paper-translation.md.

After reviewing the direction for the docs site, I’ve decided not to merge #21 as-is and will instead continue with the implementation in #22. This isn’t a reflection on the quality of your work. The final site needs to deploy to harness.dyu.sh, and I want its navigation and displayed counts to be generated from the filesystem rather than maintained by hand. That required a broader architectural rewrite, including the new C14 consistency check.

To be clear, #22 builds on both the design and parts of the implementation in this PR—not just the general idea. It carries forward the choice of VitePress, the translation grouping, the typography details, much of the Pages workflow structure, and the hero-plus-concept-card layout. I’ve credited #21 in the PR description and source comments, and I’ll add you as a co-author to the main implementation commit before #22 is merged so the Git history reflects your contribution properly.

The two-line angle-bracket fix is already included in commit 579e7252 with your authorship preserved. If you’d prefer to submit that fix as a standalone PR first, let me know and I’ll rebase #22 on top of it.

Thanks again—this PR established the direction for the docs site and saved me a lot of work. I really appreciate the contribution and would be glad to collaborate again.