From 284292ffcb67eecf3ae954c9b1904cc4df4667f4 Mon Sep 17 00:00:00 2001 From: Jeffery Date: Thu, 27 Aug 2026 18:49:58 +0800 Subject: [PATCH] =?UTF-8?q?docs(deploy):=20=E9=83=A8=E7=BD=B2=E8=AA=AA?= =?UTF-8?q?=E6=98=8E=E5=90=8C=E6=AD=A5=E4=B8=80=E6=94=AF=20CLI=20=E4=B8=80?= =?UTF-8?q?=E4=BB=BD=E7=9A=84=E9=87=8D=E5=95=9F=E7=8B=80=E6=85=8B=E6=AA=94?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit What：`README.md`「部署留在機器上的檔案」那張表，`$JSC_HOME/restart-required` 那一列改成 `$JSC_HOME/restart-required.d/{cli}`，寫明一支 CLI 一份、內容是四行 key=value，以及路徑與格式的唯一來源在 `jsc-hooks/hooks/restart-gate.sh`。`skills/deploy/SKILL.md` 第 9 步的路徑說明同步改寫，補上「每支 CLI 只讀自己那一份」與「重啟一支只清自己那份、別支的閘門還立著」，全篇維持英文。 Why：這兩份說的是同一件事在不同讀者面前的樣貌——README 給看存取庫的人，技能文件給執行部署的模型。收尾提示裡的路徑是操作者唯一會拿到的線索，寫成舊的單一檔案就對不上機器上的實況，也會讓人以為重啟一支就把全部閘門解除了，那正是這一輪要修掉的錯誤認知。 How：只改說明，第 9 步的完成判準與那句固定的重啟指示都不動。舊表格那一列原本寫「一行一次成功部署」，其實是四行 key=value 的狀態檔，這次一併訂正。路徑與格式指回 `restart-gate.sh`，兩個存取庫不各自維護一份格式說明。 Who：`jsc-cli` 的存取庫說明與 `jsc-cli:deploy` 技能文件，對齊 `jsc-hooks` 的重啟狀態檔設計。 --- README.md | 2 +- skills/deploy/SKILL.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index cf21f6b..eb2099e 100644 --- a/README.md +++ b/README.md @@ -82,7 +82,7 @@ Marketplace 統一為 `jsc`（https://gitea.jsc.idv.tw/plugins/meta.git），安 | --- | --- | --- | | `$JSC_HOME/update-guide.md` | install、update 收尾 | 下次更新的依據：偵測到的 CLI、每支的安裝方式與實際指令、marketplace token、domain 清單 | | `$JSC_HOME/remove-guide.md` | install、update 收尾 | 整組移除的依據：各 CLI 的移除指令，加上 `$JSC_HOME`、本地 clone、kiro 技能目錄、rc 檔 `# jsc-config` 段落這些殘留物 | -| `$JSC_HOME/restart-required` | install、update 全數成功時 | 一行一次成功部署（時間戳、CLI、模式、domain 清單）。`jsc-hooks` 讀它提示使用者重啟工作階段，逃生門 `JSC_RESTART_GATE=off` 也在那邊判讀 | +| `$JSC_HOME/restart-required.d/{cli}` | install、update 全數成功時 | 一支 CLI 一份，內容是四行 key=value（`at`、`mode`、`domains`、`cli`）。`jsc-hooks` 只讀當前 CLI 那一份來提示重啟，別支的不影響這一支；逃生門 `JSC_RESTART_GATE=off` 也在那邊判讀。路徑與格式的唯一來源是 `jsc-hooks/hooks/restart-gate.sh`，`deploy.sh` 只轉呼叫它的 `require` | 兩份指引一律整份覆寫，內容依產生當下的偵測結果生成，不寫死。`uninstall` 不產生指引、也不寫重啟狀態檔。 diff --git a/skills/deploy/SKILL.md b/skills/deploy/SKILL.md index a4bd5bb..b4b4248 100644 --- a/skills/deploy/SKILL.md +++ b/skills/deploy/SKILL.md @@ -25,4 +25,4 @@ description: Batch install, update, or uninstall the whole jsc skill set on ever 6. After install or update, call `jsc-hooks:hooks-install` to rewire the hooks. Done when hooks-install reports a wiring result for each detected CLI. 7. After install or update, run `tools/write-guides.sh {mode} {domain}...` **once for the whole machine**, after every CLI in step 5 has finished. It rewrites `$JSC_HOME/update-guide.md` and `$JSC_HOME/remove-guide.md` from the live detection result, so the later update and removal runs have the real commands for this machine. Skip it for `uninstall`: the guides describe an installed skill set. Done when the script printed a `wrote` line for both files. 8. Report the result and any failure reason for every CLI × mode, plus every `skip` line and every CLI that could not be version-checked in step 2. Done when every detected CLI appears in the report with its `result` status. -9. For install or update, close the report with the restart instruction, in these words: 「請關閉目前的工作階段並重新啟動，新的技能內容才會載入」. `deploy.sh` recorded this round in `$JSC_HOME/restart-required` and prints its path on a `restart` line; `jsc-hooks` reads that file and keeps reminding until the restart happens, with `JSC_RESTART_GATE=off` as the escape hatch. Name the two guide paths from step 7 in the same closing block, so the operator knows where this machine's update and removal commands now live. Done when the restart instruction is printed and both guide paths are named. +9. For install or update, close the report with the restart instruction, in these words: 「請關閉目前的工作階段並重新啟動，新的技能內容才會載入」. `deploy.sh` recorded this round in `$JSC_HOME/restart-required.d/{cli}` — one file per CLI — and prints its path on a `restart` line; `jsc-hooks` reads only that CLI's own file and keeps reminding until that CLI restarts, with `JSC_RESTART_GATE=off` as the escape hatch. Restarting one CLI clears its own file and leaves the others' gates standing. Name the two guide paths from step 7 in the same closing block, so the operator knows where this machine's update and removal commands now live. Done when the restart instruction is printed and both guide paths are named.