fix: HTTP 云函数 Skill 缺少路径映射和网关路径处理的关键说明

[binggg]

Attribution issue

• issueId: issue_mo1hkx69_frhv2z
• category: skill
• canonicalTitle: HTTP 云函数 Skill 缺少路径映射和网关路径处理的关键说明
• representativeRun: atomic-js-cloudbase-http-function-deploy/2026-04-16T12-55-40-01e14c

Automation summary

• root_cause: The main cloud-functions skill did not surface a key HTTP-function guardrail that already existed deeper in the references and MCP tool messaging: creating an HTTP function does not automatically create a browser/public gateway path, /{functionName} is not guaranteed, and gateway path prefixes are separate from the in-function router. In all-in-one usage, agents can stop at the top-level skill and miss that distinction, which is a real product-facing documentation defect.
• changes: Updated config/source/skills/cloud-functions/SKILL.md with two explicit HTTP-function gotchas and one gateway-exposure note. The skill now warns against assuming automatic public path mapping, warns against baking gateway prefixes like /api/httpDemo into the function router, and states that browser/public access requires separate gateway configuration layered on top of the HTTP function’s own routes.
• validation: Re-read the existing HTTP-function reference to confirm the new top-level guidance matches the established contract for gateway access and anonymous-access handling, then ran git diff --check to verify the edit is clean. No broader automated test run was necessary becau

Changed files

• config/source/skills/cloud-functions/SKILL.md

[chatgpt-codex-connector]

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