fix: uploadFiles MCP 工具未区分云存储上传与静态托管部署，导致文件上传成功但静态托管返回 404

[binggg]

Attribution issue

• issueId: issue_moctkjy6_r53c36
• category: tool
• canonicalTitle: uploadFiles MCP 工具未区分云存储上传与静态托管部署，导致文件上传成功但静态托管返回 404
• representativeRun: application-js-vite-hello-world-hosting-deploy/2026-04-24T11-16-15-2146cb

Automation summary

• root_cause: The uploadFiles MCP tool description and web-development skill explicitly told AI agents to use "相对路径" (relative paths like ./) for base/publicPath/assetPrefix when deploying to subdirectories. This is wrong — when deploying to a subdirectory like /vite-test, the Vite base must be set to the absolute path '/vite-test/' (with leading and trailing slashes). Using './' causes 404 errors when the access URL lacks a trailing slash, because the browser resolves relative paths against the current directory rather than the intended subdirectory root. Additionally, the cloudPath parameter description didn't clarify format rules (no leading /), and the skill lacked a mandatory pre-upload checklist for subdirectory deployments.
• changes:

1. mcp/src/tools/hosting.ts: Fixed uploadFiles tool description — replaced misleading "是否使用相对路径" with explicit subdirectory deployment rules: base/publicPath/assetPrefix must use absolute paths matching the deploy target (e.g., /vite-test/), forbidden ./ and empty string, must rebuild after config change, must verify build output, cloudPath format (no leading /)
2. mcp/src/tools/hosting.ts: Fixed cloudPath parameter descri

Changed files

• config/source/skills/web-development/SKILL.md
• config/source/skills/web-development/frameworks.md
• doc/mcp-tools.md
• doc/prompts/web-development.mdx
• mcp/src/tools/hosting.ts
• mcp/src/tools/storage-hosting-guidance.test.ts

[binggg]

Closing as duplicate: same case has newer PR #651. Keeping #651.