fix: uploadFiles MCP 工具 cloudPath 格式不清且缺少部署验证能力，导致静态托管部署后 404

[binggg]

Attribution issue

• issueId: issue_moj04v8k_rh94tl
• category: tool
• canonicalTitle: uploadFiles MCP 工具 cloudPath 格式不清且缺少部署验证能力，导致静态托管部署后 404
• representativeRun: application-js-vite-hello-world-hosting-deploy/2026-04-28T19-08-29-bd50e1

Automation summary

• root_cause: The uploadFiles MCP tool and web-development skill documentation lacked clear guidance about (1) cloudPath format (no leading '/'), (2) mandatory pre-deployment checklist for subdirectory deployment, and (3) Vite base configuration requirements for subdirectory deployment. This caused AI agents to deploy to subdirectories without proper build configuration, resulting in 404 errors for static assets.
• changes:

1. mcp/src/tools/hosting.ts: Updated uploadFiles tool description to include:

• Clear "子目录部署强制二次确认" (subdirectory deployment forced secondary confirmation) section with 3 mandatory checks
• Explicit warning about forbidden './' relative paths in build config
• Updated cloudPath parameter description to clarify "相对于托管根目录，不要前导 '/'" with examples ('vite-test' correct, '/vite-test' wrong)

2. config/source/skills/web-development/SKILL.md: Added new section "Subdirectory deployment requirements" with:

• cloudPath format guidance with correct/wrong examples
• Build configuration requirements (base/publicPath/assetPrefix must match deployment path)
• Mandatory pre-deployment checklist
• Common 404 cause explanation (using './' relative paths)

3. **config/s

Changed files

• config/source/skills/web-development/SKILL.md
• config/source/skills/web-development/frameworks.md
• mcp/src/tools/hosting.ts

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[binggg]

Attribution post-PR evaluation

• visibility: internal identifiers, run ids, and private links are intentionally omitted
• attempt: 1
• eval_scope: primary_only
• overall: ERROR
• summary: post-PR evaluation errored
• updated_at: 2026-04-28T20:38:00.960Z

Cases

• [ERROR] — primary — evaluation errored