docs: add toolchain migration impact inventory

[12ain]

Summary

• Add comprehensive inventory of docs toolchain components
• Document build, routing, theme, sidebar/navigation, and deployment
• Include verification commands and migration impact analysis
• Link to RFC RFC: migrate dumi/Umi toolchain to clear remaining docs security alerts #32 and issue docs: inventory docs toolchain migration impact #33

Changes

Added aigc/prompts/docs-toolchain-migration-impact-inventory-2026-06-16.zh-CN.md which contains:

1. Toolchain Overview: All components with versions and security status
2. Build: Configuration, commands, and affected files
3. Routing: File system-based routing rules
4. Theme: Default theme configuration
5. Sidebar/Navigation: Auto-generated from directory structure
6. Deployment: Cloudflare Pages/Workers configuration
7. CI/CD: All workflow files and their purposes
8. Verification Commands: Local dev, build, audit, CI, and deployment
9. Migration Impact Analysis: Low/medium/high impact areas
10. Configuration Files: Complete list of all config files
11. Dependency Overrides: Detailed pnpm.overrides with CVE numbers
12. Documentation Structure: File counts and categories
13. Code Quality Tools: Prettier, EditorConfig, Husky

Related Issues

• Closes docs: inventory docs toolchain migration impact #33
• Related to RFC: migrate dumi/Umi toolchain to clear remaining docs security alerts #32

[lwnmengjing]

Thanks @12ain — this is a thorough inventory and it covers the scope of #33 well. The build and CodeQL checks are already green.\n\nBefore merge, please make these small updates so the document remains accurate and maintainable:\n\n1. Replace in the frontmatter/title/description with a dated “snapshot” or “baseline”. This inventory will drift as dumi/Umi and GitHub advisories change.\n2. Refresh the security section. Since June 20, GitHub reports new development-only transitive alerts for:\n - 4.12.23 (patched in 4.12.25)\n - 4.9.2 (patched in 4.9.3)\n Therefore “only elliptic remains” is no longer accurate. Please record these as newly actionable toolchain items and keep as the no-patched-version item.\n3. Add a final newline to the Markdown file.\n4. Update the PR body with explicit sections for Tests/Verification, Docs Impact, Security Impact, and Release Impact. That is why PR Guard is failing; the content itself is not the blocker.\n\nNo broad rewrite is needed. Once these items are updated and checks are green, this should be ready for approval and squash merge.

[lwnmengjing]

Correction to my review above: shell formatting removed the inline code terms. The missing terms are Final, hono, piscina, and elliptic. Specifically, please rename the Final wording to snapshot/baseline; record hono 4.12.23 -> 4.12.25 and piscina 4.9.2 -> 4.9.3 as new development-only transitive toolchain items; keep elliptic as the no-patched-version item. The requested changes are otherwise unchanged.