mirror of
https://git.openapi.site/https://github.com/desirecore/market.git
synced 2026-07-23 07:03:51 +08:00
docs(dev-environment-setup): /environment/refresh 补充重新加载登录环境变量语义 (#24)
## 变更说明 / Description 配合客户端 PR [desirecore/desirecore#808](https://github.com/desirecore/desirecore/pull/808):`POST /api/runtime/environment/refresh` 端点现在除清检测缓存外,还会**重新抓取登录 shell / Windows 注册表环境并精确同步到 `process.env`**。本 PR 更新 `dev-environment-setup` skill 文档,让 AI 在「用户改了 `.zshrc` / `setx` 但工具看不到」时能主动调用该端点(无需用户重启 App)。 Companion to client PR desirecore#808: the `/environment/refresh` endpoint now also reloads login-shell / Windows-registry env and precise-syncs into `process.env`. This PR updates the `dev-environment-setup` skill docs so the AI proactively calls it when a user reports a freshly-changed env var that tools can't see. ## 改动 / Changes - `references/desirecore-runtime.md`:第三节端点表更新 + 第七节扩展(重新加载语义 + `envDiff` 返回结构 + 「何时主动调用」触发场景 + 局限) - `SKILL.md` / `SKILL.zh-CN.md`:L1 路由表新增「用户改了 `.zshrc` / 环境变量 / 代理 / `setx` 但工具看不到 → 刷新端点」+ 重要约束第 3 条扩展(中英双语同步) - `version` 2.0.3 → 2.0.4;并修正 #16 起遗留的 `source_hash` stale 值(`7e4baaf` → `748e754b`,已用 `scripts/i18n` 同款算法验证) ## 说明 / Notes - 该 skill 为 `translated_by: human`,中英两份已手动同步 - 文档描述的端点能力随客户端 PR desirecore#808 发布;旧客户端调用该端点仍只清检测缓存(不报错),文档短暂超前可接受
This commit is contained in:
@@ -12,7 +12,7 @@ description: >-
|
||||
cross-cutting environment question. 使用场景:用户提到 环境配置、PATH、
|
||||
容器、Docker、Podman、WSL、WSL2、办公依赖、系统工具,或不确定属于 Python /
|
||||
Node.js 时的入口指引。
|
||||
version: 2.0.3
|
||||
version: 2.0.4
|
||||
type: procedural
|
||||
risk_level: low
|
||||
status: enabled
|
||||
@@ -27,7 +27,7 @@ tags:
|
||||
- router
|
||||
metadata:
|
||||
author: desirecore
|
||||
updated_at: '2026-05-05'
|
||||
updated_at: '2026-06-09'
|
||||
i18n:
|
||||
default_locale: en-US
|
||||
source_locale: zh-CN
|
||||
@@ -40,7 +40,7 @@ metadata:
|
||||
description: >-
|
||||
Use this skill as a router/index when the user faces a development environment question that spans multiple domains: containers (Docker/Podman), WSL2 on Windows, office-skill dependencies (DOCX/PDF/XLSX/ PPTX), or system tools (LibreOffice/Poppler/Pandoc/Tesseract). For pure Python issues use python-runtime skill; for pure Node.js issues use nodejs-runtime skill. Triggers include: "setup environment", "PATH", "WSL", "WSL2", "docker not found", "podman", "container", "office dependency", "LibreOffice", "poppler", "pandoc", "tesseract", or any cross-cutting environment question. 使用场景:用户提到 环境配置、PATH、 容器、Docker、Podman、WSL、WSL2、办公依赖、系统工具,或不确定属于 Python / Node.js 时的入口指引。
|
||||
body: ./SKILL.zh-CN.md
|
||||
source_hash: sha256:7e4baaf42d5c0ace
|
||||
source_hash: sha256:748e754b5537ea01
|
||||
translated_by: human
|
||||
en-US:
|
||||
name: Dev Environment Setup
|
||||
@@ -48,9 +48,9 @@ metadata:
|
||||
description: >-
|
||||
Use this skill as a router/index when the user faces a development environment question that spans multiple domains: containers (Docker/Podman), WSL2 on Windows, office-skill dependencies (DOCX/PDF/XLSX/ PPTX), or system tools (LibreOffice/Poppler/Pandoc/Tesseract). For pure Python issues use python-runtime skill; for pure Node.js issues use nodejs-runtime skill. Triggers include: "setup environment", "PATH", "WSL", "WSL2", "docker not found", "podman", "container", "office dependency", "LibreOffice", "poppler", "pandoc", "tesseract", or any cross-cutting environment question. Use when the user mentions environment setup, PATH, containers, Docker, Podman, WSL, WSL2, office dependencies, system tools, or needs an entry-point guide when uncertain whether the issue belongs to Python or Node.js.
|
||||
body: ./SKILL.md
|
||||
source_hash: sha256:7e4baaf42d5c0ace
|
||||
source_hash: sha256:748e754b5537ea01
|
||||
translated_by: human
|
||||
translated_at: '2026-05-03'
|
||||
translated_at: '2026-06-09'
|
||||
market:
|
||||
icon: >-
|
||||
<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewBox="0 0
|
||||
@@ -101,6 +101,7 @@ Route directly to the corresponding skill or document by the keywords in the use
|
||||
| LibreOffice / poppler / pandoc / tesseract / qpdf | `references/system-tools.md` |
|
||||
| Unsure of category, want a quick diagnosis | First run `scripts/probe.sh` and inspect the JSON |
|
||||
| DesireCore Hatch / Volta / HTTP API / Socket.IO | `references/desirecore-runtime.md` |
|
||||
| User edited `.zshrc` / an env var / proxy / `setx`, but tools can't see it | `POST /api/runtime/environment/refresh` reloads the login environment (see `references/desirecore-runtime.md` §7, no app restart needed) |
|
||||
| Four-tier fallback decision (API → CLI → package manager → community solution) | `references/decision-tree.md` |
|
||||
|
||||
## L2: Detailed Specification
|
||||
@@ -147,7 +148,7 @@ DesireCore embeds Hatch (Python) and Volta (Node.js), providing complete environ
|
||||
|
||||
1. **Do not write strong keywords like python / node / pip / npm into this skill's description**—those belong to their respective sub-skills, to avoid trigger conflicts.
|
||||
2. **API first**: `scripts/probe.sh` first checks `${DESIRECORE_ROOT}/agent-service.port`; if it exists, recommend the HTTP API path.
|
||||
3. **Cache coherence**: after any install/uninstall completes, call `POST /api/runtime/environment/refresh` to invalidate the cache before issuing subsequent GETs.
|
||||
3. **Cache coherence + env reload**: after any install/uninstall completes, call `POST /api/runtime/environment/refresh` to invalidate the cache before subsequent GETs; the same endpoint also reloads login environment variables (re-reads `.zshrc` / registry and precise-syncs into `process.env`), so when a user reports a freshly-changed env var that tools can't see, call it proactively too (no app restart; the returned `envDiff` confirms the changes).
|
||||
4. **Cross-platform**: every command template provides both macOS / Linux and Windows (PowerShell) versions.
|
||||
|
||||
## Sub-skill and Document Manifest
|
||||
|
||||
Reference in New Issue
Block a user