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

Author: CodeBuddy Attribution Bot

config/.claude/skills/cloud-functions/SKILL.md

@@ -50,6 +50,8 @@ Keep local `references/...` paths for files that ship with the current skill dir
 - Confusing official CloudBase API client work with building your own HTTP function.
 - Mixing Event Function code shape (`exports.main(event, context)`) with HTTP Function code shape (`req` / `res` on port `9000`).
 - Treating HTTP Access as the implementation model for HTTP Functions. HTTP Access is a gateway configuration for Event Functions, not the HTTP Function runtime model.
+- Assuming an HTTP Function automatically gets a browser/public URL path, or assuming that path is always `/{functionName}`.
+- Writing gateway prefixes such as `/api/httpDemo` into the function router itself. Public gateway path and in-function route path are different layers.
 - Forgetting that runtime cannot be changed after creation.
 - Using cloud functions as the first answer for Web login.
 - Forgetting that HTTP Functions must ship `scf_bootstrap`, listen on port `9000`, and include dependencies.
@@ -199,6 +201,8 @@ server.listen(9000);
 - `manageGateway(action="createAccess")`
 - If gateway operations need raw cloud API fallback, read `./references/operations-and-config.md` first
 
+When a user says they need browser/public access, do not assume creation already exposed the function. HTTP Function runtime routes still live inside the function, while gateway access adds an external path prefix separately.
+
 ## Related skills
 
 - `cloudrun-development` -> container services, long-lived runtimes, Agent hosting

config/.claude/skills/cloud-functions/references/http-functions.md

@@ -143,6 +143,29 @@ manageGateway({
 });
 ```
 
+### Path mapping model
+
+Keep the public gateway path and the in-function router path as two different layers.
+
+- `manageGateway(..., path: "/api/hello")` creates the **external** access prefix.
+- Your HTTP Function still matches its own internal routes such as `/`, `/health`, `/users`.
+- Do **not** rewrite the function router to include the gateway prefix.
+
+Example mapping:
+
+| External URL | Route your HTTP Function should handle |
+| --- | --- |
+| `https://{domain}/api/hello` | `/` |
+| `https://{domain}/api/hello/health` | `/health` |
+| `https://{domain}/api/hello/users` | `/users` |
+
+For example, if you expose `path: "/api/httpDemo"`, the function code should normally keep handlers like `app.get("/")` and `app.get("/health")`. Do not change them to `app.get("/api/httpDemo")` or `app.get("/api/httpDemo/health")`.
+
+If the external caller reports a 404, verify these two layers separately:
+
+1. Use `queryGateway(action="getAccess")` to confirm which public path is actually exposed.
+2. Check the HTTP Function router to confirm it handles the internal path after the gateway prefix.
+
 Before enabling anonymous access, confirm both of these:
 
 1. The access path exists.