fix: 修复场景入口索引冲突并记录 API 上线验收

[yi-ge]

变更说明 / Description

API 文档 #72 已自动部署，16个页面与8个下载的正式线上验收全部通过。全站验收718个URL均200，但应用场景中英文入口的canonical被目录README隐式索引覆盖为尾斜杠地址。

• 将作者资产说明 docs/03-use-cases/README.md 重命名为 _README.md，由已有Docusaurus默认规则排除；正文逐字保留，无仓内引用需要调整。
• 保留正式 /use-cases 和 /en/use-cases 的slug、正文与导航。重建后两入口canonical和标题均准确。
• 回写API正式Production deployment及逐项生产验收报告；全站门禁保持严格，部署后再次验收。

The API documentation is already deployed and all 16 API pages / 8 downloads passed production acceptance. The site-wide audit exposed an existing README/index output collision at the bilingual use-case landing pages. Rename the author-only README to use Docusaurus's existing exclusion convention; preserve the real landing pages and all API contracts. Record production evidence without treating the two existing SEO failures as passed.

验证 / Validation

• Bilingual production build passed.
• Built /use-cases and /en/use-cases now have exact canonicals and their intended headings, “应用场景” / “Use Cases”.
• pnpm api:check -- --build: 8 bilingual groups / 24 operations / 3 specs and identical downloads passed.
• Existing README has no repository references; no language fallback page should be generated for an author-only asset guide.
• API production evidence from deployment 7088235715 is saved in api/production-verification.json; source remains merged API code e45f229.
• After this PR deploys, rerun site-wide production HTTP/SEO verification.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
docs	Ready	Preview	Oct 15, 2026 9:04am UTC