✨ feat: 添加微信小程序调试工具和完整参数参考文档

.codex/skills/shz-pc-debug/references/project-topology.md

@@ -1,21 +1,21 @@
-# SHZ Project Topology
+# SHZ 项目结构
 
-| Workspace | Responsibility | Use during debugging |
+| 工作区 | 职责 | 调试时的用途 |
 | --- | --- | --- |
-| `/Users/lapuda/code/shz-backend` | Backend project | Investigate API routing, authorization, business services, scheduled work, persistence, and server errors. Use the project's log and guarded database skills here. |
-| `/Users/lapuda/code/shz-admin` | PC frontend | Investigate PC job-seeker, supervisory-admin, and enterprise UI routes, components, client state, request construction, and browser interaction. |
-| `/Users/lapuda/code/shz-employment-service` | Mini-program | Investigate only mini-program-specific behavior, or a suspected interface/authentication/business-logic concern shared with the PC application. |
+| `/Users/lapuda/code/shz-backend` | 后端项目 | 调查 API 路由、授权、业务服务、定时任务、持久化和服务器错误。在此使用项目日志和受保护的数据库 skill。 |
+| `/Users/lapuda/code/shz-admin` | PC 前端 | 调查 PC 求职者、监管管理员和企业 UI 路由、组件、客户端状态、请求构造和浏览器交互。 |
+| `/Users/lapuda/code/shz-employment-service` | 小程序 | 仅调查小程序特有行为，或与 PC 应用共用的接口/认证/业务逻辑问题。 |
 
-## Select the minimum scope
+## 选择最小范围
 
-1. Start a PC visual, interaction, navigation, or missing-request investigation in `shz-admin` after capturing browser evidence.
-2. Start an API status, response, permission, server exception, or database-data investigation in `shz-backend`.
-3. Investigate both `shz-admin` and `shz-backend` when the browser request or response shows that the failure crosses the client/server boundary.
-4. Add `shz-employment-service` only after evidence indicates the same endpoint or business behavior is involved. Do not change mini-program code for a PC-only issue.
+1. 捕获浏览器证据后，在 `shz-admin` 中开始 PC 视觉、交互、导航或请求缺失问题的调查。
+2. 在 `shz-backend` 中开始 API 状态、响应、权限、服务器异常或数据库数据问题的调查。
+3. 当浏览器请求或响应表明故障跨越客户端/服务器边界时，同时调查 `shz-admin` 和 `shz-backend`。
+4. 只有证据表明涉及同一个接口或业务行为时，才加入 `shz-employment-service`。PC 独有问题不得修改小程序代码。
 
-## Work safely across repositories
+## 跨仓库安全工作
 
-1. Change into the selected workspace before using CodeGraph, running checks, or editing files.
-2. Check each repository's working tree independently and preserve unrelated changes.
-3. Attempt CodeGraph in the selected workspace before broad text search. If its index is unavailable, do not create one; use `rg` as the fallback.
-4. Run focused verification in every repository changed. Do not deploy, restart services, or alter a remote environment unless the current user request explicitly authorizes committing and deploying; then follow [deployment.md](deployment.md).
+1. 使用 CodeGraph、运行检查或编辑文件前，先进入选定的工作区。
+2. 独立检查每个仓库的工作树，并保留无关改动。
+3. 广泛文本搜索前，在选定工作区尝试使用 CodeGraph。如果索引不可用，不得创建索引；改用 `rg`。
+4. 对每个发生变更的仓库运行聚焦验证。除非当前用户请求明确授权提交和部署，否则不得部署、重启服务或修改远程环境；获得授权后遵循 [deployment.md](deployment.md)。