tink-harness 1.9.12 → 1.9.14

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "tink",
   "description": "A small harness layer for Claude Code and Codex.",
-  "version": "1.9.12",
+  "version": "1.9.14",
   "author": {
     "name": "dotori"
   }

package/CHANGELOG.md

@@ -6,6 +6,27 @@ All notable changes to Tink are tracked here.
 
 No unreleased changes yet.
 
+## [1.9.14] - 2026-06-11
+
+### Changed
+
+- `npx tink-harness update` now asks a single question (which agent surface to refresh) and handles everything else automatically: language is detected from `.tink/config.json`, components and scope use sensible defaults, and Tink-owned files always refresh while user-modified harness/memory/config files stay preserved.
+- README (EN/KO) reorganized developer-first: a one-minute Quick start, a "see your harness health" section with dashboard screenshots (3D map + harness cards), and an updated one-question update description. The origin story and all install/command details are kept.
+
+### Added
+
+- Dashboard screenshots committed under `.github/assets/` (`dashboard-map.png`, `dashboard-harnesses.png`).
+
+## [1.9.13] - 2026-06-11
+
+### Fixed
+
+- `npx tink-harness update` now always refreshes `.tink/tools/` (the lifecycle generator and health-report renderer). Previously stale tools were preserved as "user-modified", so updated installs kept rendering the old dashboard. Run `update` again on affected machines to pick up the current tools.
+
+### Changed
+
+- `/tink:update` docs and the update summary now list `.tink/tools/` in the always-updated category; added a regression test that a stale tool file is overwritten by `update`.
+
 ## [1.9.12] - 2026-06-11
 
 ### Changed

package/README.ko.md

@@ -8,12 +8,62 @@ Claude Code와 Codex를 위한 작은 하네스 레이어입니다.
 
 Tink는 지금 작업에 맞는 하네스를 고르고, 실행 상태를 보이게 만들고, 실제 사용 중 생긴 실패와 피드백으로 하네스 세트를 개선합니다.
 
-**최신 패키지:** v1.9.12 — 로컬 건강 리포트가 탭형 대시보드로 바뀌었습니다. 3D 하네스 지도, 쉬운 말 건강 요약, Claude Code와 Codex 양쪽 복사-붙여넣기 명령이 포함된 다음 행동 제안을 제공합니다. 전체 변경 이력은 [CHANGELOG](CHANGELOG.md)를 확인하세요.
+**최신 패키지:** v1.9.14 — 로컬 건강 리포트가 탭형 대시보드로 바뀌었습니다. 3D 하네스 지도, 쉬운 말 건강 요약, Claude Code와 Codex 양쪽 복사-붙여넣기 명령이 포함된 다음 행동 제안을 제공합니다. 전체 변경 이력은 [CHANGELOG](CHANGELOG.md)를 확인하세요.
 
 [English](README.md) · **한국어** · [변경 이력](CHANGELOG.md)
 
 ---
 
+## 빠른 시작
+
+1분이면 Tink를 직접 써볼 수 있습니다.
+
+**Claude Code (플러그인):**
+
+```text
+/plugin marketplace add dotoricode/tink-harness
+/plugin install tink@tink-harness
+/reload-plugins
+/tink:setup
+```
+
+**Claude Code 또는 Codex (스탠드얼론):**
+
+```bash
+npx tink-harness@latest install
+```
+
+문서를 더 읽는 대신 실제 작업을 맡겨 보세요:
+
+```text
+/tink:cast 인증 모듈 리팩터링     # Claude Code
+$tink:cast 인증 모듈 리팩터링     # Codex
+```
+
+`cast`는 작업에 맞는 하네스를 고르고(없으면 초안을 만들고), `.tink/current/`에 보이는 계획을 쓰고, 승인 후 첫 안전한 단계를 시작합니다. 끝난 run마다 간결한 기록이 남고 — 그 기록이 아래 대시보드가 됩니다.
+
+## 하네스 건강을 눈으로 확인
+
+몇 번의 run이 쌓이면, 읽기 전용 helper 두 개가 기록을 로컬 대시보드로 바꿔 줍니다:
+
+```bash
+node .tink/tools/generate-harness-lifecycle-summary.mjs
+node .tink/tools/render-harness-health-report.mjs
+# .tink/maintenance/harness-health-report.html 열기
+```
+
+하네스와 그들이 쓰는 규칙·메모리, 그 연결을 보여주는 인터랙티브 3D 지도 — 무리마다 고유한 색을 갖고, 살아있는 관계 위로 신호가 흐릅니다:
+
+![Tink 하네스 지도 — 하네스·규칙·메모리·단계를 보여주는 인터랙티브 3D 뷰](.github/assets/dashboard-map.png)
+
+실제 사용량 순으로 정렬된 하네스 카드 — 쉬운 말 건강 요약, 주의 점수, 승인 이력, 그리고 Claude Code·Codex 양쪽 복사용 명령이 포함된 다음 행동 제안:
+
+![사용량 순 하네스 카드와 쉬운 말 건강 요약·히스토리](.github/assets/dashboard-harnesses.png)
+
+서버도, 텔레메트리도, 숨은 캐시도 없습니다 — 제안만 준비하는 정적 로컬 페이지입니다. 재사용되는 변경은 여전히 Tink의 승인 절차를 거칩니다.
+
+---
+
 ## 왜 만들었나
 
 새로운 AI 코딩 하네스와 워크플로는 계속 늘어납니다. 좋은 것도 많지만, 여러 개를 섞다 보면 환경이 무거워지고 매번 다시 정리해야 합니다.
@@ -62,6 +112,8 @@ Standalone / Codex:
 npx tink-harness@latest update
 ```
 
+업데이트는 질문 하나 — 어떤 agent surface를 갱신할지 — 만 묻고 나머지는 자동으로 처리합니다. Tink가 관리하는 파일(commands, skills, maintenance, 런타임 tools)은 항상 최신으로 덮어쓰고, 사용자가 수정한 하네스·메모리·설정은 보존합니다.
+
 `CODEX_HOME`을 지정하지 않으면 Windows에서는 `%USERPROFILE%\.codex`, macOS/Linux에서는 `~/.codex`에 Codex skill이 설치됩니다.
 
 ### 고급 옵션

package/README.md

@@ -17,19 +17,69 @@
 </p>
 
 <p>
-  <a href="https://github.com/dotoricode/tink-harness/releases/tag/v1.9.12"><img src="https://img.shields.io/github/v/release/dotoricode/tink-harness?label=release&color=2ea44f" alt="GitHub release"></a>
+  <a href="https://github.com/dotoricode/tink-harness/releases/tag/v1.9.14"><img src="https://img.shields.io/github/v/release/dotoricode/tink-harness?label=release&color=2ea44f" alt="GitHub release"></a>
   <a href="https://www.npmjs.com/package/tink-harness"><img src="https://img.shields.io/npm/v/tink-harness?label=npm&color=cb3837" alt="npm version"></a>
   <a href="https://github.com/dotoricode/tink-harness/actions/workflows/ci.yml"><img src="https://img.shields.io/github/actions/workflow/status/dotoricode/tink-harness/ci.yml?branch=main&label=ci" alt="CI"></a>
   <a href="https://github.com/dotoricode/tink-harness/blob/main/LICENSE"><img src="https://img.shields.io/github/license/dotoricode/tink-harness" alt="License"></a>
   <a href="https://github.com/dotoricode/tink-harness/stargazers"><img src="https://img.shields.io/github/stars/dotoricode/tink-harness?style=social" alt="GitHub stars"></a>
 </p>
 
-<p><strong>Latest package:</strong> v1.9.12 - The local health report is now a tabbed dashboard with a 3D harness map, plain-language health summaries, and next-action suggestions with copy-paste commands for both Claude Code and Codex. See <a href="CHANGELOG.md">CHANGELOG</a> for release history.</p>
+<p><strong>Latest package:</strong> v1.9.14 - The local health report is now a tabbed dashboard with a 3D harness map, plain-language health summaries, and next-action suggestions with copy-paste commands for both Claude Code and Codex. See <a href="CHANGELOG.md">CHANGELOG</a> for release history.</p>
 
 **English** · [한국어](README.ko.md) · [Changelog](CHANGELOG.md)
 
 ---
 
+## Quick start
+
+Try Tink in about a minute.
+
+**Claude Code (plugin):**
+
+```text
+/plugin marketplace add dotoricode/tink-harness
+/plugin install tink@tink-harness
+/reload-plugins
+/tink:setup
+```
+
+**Claude Code or Codex (standalone):**
+
+```bash
+npx tink-harness@latest install
+```
+
+Then hand Tink a real task instead of reading more docs:
+
+```text
+/tink:cast refactor the auth module     # Claude Code
+$tink:cast refactor the auth module     # Codex
+```
+
+`cast` picks (or drafts) the right harness, writes a visible plan into `.tink/current/`, and starts the first safe step after your approval. Every finished run leaves a compact record - and those records become the dashboard below.
+
+## See your harness health
+
+After a few runs, two read-only helpers turn your records into a local dashboard:
+
+```bash
+node .tink/tools/generate-harness-lifecycle-summary.mjs
+node .tink/tools/render-harness-health-report.mjs
+# then open .tink/maintenance/harness-health-report.html
+```
+
+An interactive 3D map of your harnesses, the rules and memory they use, and how they connect - each cluster gets its own color, and neural pulses travel along live relationships:
+
+![Tink harness map - an interactive 3D view of harnesses, rules, memory, and stages](.github/assets/dashboard-map.png)
+
+Harness cards sorted by real usage, with plain-language health summaries, an attention score, the approval history, and a suggested next action with copy-paste commands for both Claude Code and Codex:
+
+![Harness cards sorted by usage with plain-language health and history](.github/assets/dashboard-harnesses.png)
+
+No server, no telemetry, no hidden cache - it is a static local page that only prepares suggestions. Anything reusable still goes through Tink's approval gates.
+
+---
+
 ## Why I made this
 
 New coding harnesses show up almost every day. Many of them are genuinely useful.
@@ -113,19 +163,13 @@ If update does not find the latest version, uninstall and install again:
 /plugin install tink@tink-harness
 ```
 
-To update an existing standalone install (keeps user-modified files):
-
-```bash
-npx tink-harness@latest update
-```
-
-For Codex:
+To update an existing standalone install (Claude Code or Codex):
 
 ```bash
 npx tink-harness@latest update
 ```
 
-During update, select the installed agent surface you want to refresh.
+Update asks one question - which agent surface to refresh - and handles the rest automatically. Tink-owned files (commands, skills, maintenance, runtime tools) are always brought to the latest version; your customized harnesses, memory, and config are preserved.
 
 If `CODEX_HOME` is not set, Codex skills default to `%USERPROFILE%\.codex` on Windows and `~/.codex` on macOS/Linux.
 

package/VERSIONING.md

@@ -1,6 +1,6 @@
 # Versioning
 
-Current version: `1.9.12`
+Current version: `1.9.14`
 
 Tink follows semver from `1.0.0` onward.
 

package/bin/install.js

@@ -124,7 +124,7 @@ function argValue(name) {
 }
 
 function usage() {
-  console.log(`Tink installer for Claude Code and Codex\n\nUsage:\n  tink-harness [install] [--scope=repo|global] [--global] [--lang=en|ko|zh] [--yes] [--with-hook] [--clean-codex-picker] [--dry-run] [--force]\n  tink-harness update [--scope=repo|global] [--global] [--lang=en|ko|zh] [--yes] [--clean-codex-picker] [--dry-run] [--force]\n\nIf the command is not installed yet, use:\n  npx tink-harness@latest [install]\n  npx tink-harness@latest update\n\nCommands:\n  install  Install Tink.\n  update   Update Tink to the latest templates. Keeps user-modified files.\n\nDefault interactive flow:\n  1. Select language\n  2. Show TINK wizard\n  3. Select Claude Code, Codex, or both\n  4. Select components\n  5. Select repo/global installation scope\n  6. Select Advanced options\n  7. Select git tracking policy for project state\n\nAdvanced options:\n  --dry-run             Preview only. Show what would be written or removed, but do not change files.\n  --force               Overwrite user-modified files. Use only when you want official templates to replace local edits.\n  --clean-codex-picker  Codex-only cleanup. Remove repo-local Claude Tink surfaces that show as Source Command Tink entries.\n\nEnvironment:\n  TINK_INSTALL_SURFACES=claude|codex|all\n  TINK_CLEAN_CODEX_PICKER=1\n\nScopes:\n  repo    Install shared .tink files into the current project.\n  global  Install shared .tink files into your home directory.\n`);
+  console.log(`Tink installer for Claude Code and Codex\n\nUsage:\n  tink-harness [install] [--scope=repo|global] [--global] [--lang=en|ko|zh] [--yes] [--with-hook] [--clean-codex-picker] [--dry-run] [--force]\n  tink-harness update [--scope=repo|global] [--global] [--lang=en|ko|zh] [--yes] [--clean-codex-picker] [--dry-run] [--force]\n\nIf the command is not installed yet, use:\n  npx tink-harness@latest [install]\n  npx tink-harness@latest update\n\nCommands:\n  install  Install Tink.\n  update   Update Tink to the latest templates. Asks only the agent surface; Tink-owned files always refresh, user-modified harness/memory/config files are kept.\n\nDefault interactive flow:\n  1. Select language\n  2. Show TINK wizard\n  3. Select Claude Code, Codex, or both\n  4. Select components\n  5. Select repo/global installation scope\n  6. Select Advanced options\n  7. Select git tracking policy for project state\n\nAdvanced options:\n  --dry-run             Preview only. Show what would be written or removed, but do not change files.\n  --force               Overwrite user-modified files. Use only when you want official templates to replace local edits.\n  --clean-codex-picker  Codex-only cleanup. Remove repo-local Claude Tink surfaces that show as Source Command Tink entries.\n\nEnvironment:\n  TINK_INSTALL_SURFACES=claude|codex|all\n  TINK_CLEAN_CODEX_PICKER=1\n\nScopes:\n  repo    Install shared .tink files into the current project.\n  global  Install shared .tink files into your home directory.\n`);
 }
 
 function normalizeSurfaces(surfaces) {
@@ -383,12 +383,22 @@ function shortList(items, emptyText = '- none') {
   return shown.join('\n');
 }
 
+function detectInstalledLanguage() {
+  try {
+    const config = JSON.parse(fs.readFileSync(path.join(process.cwd(), '.tink/config.json'), 'utf8'));
+    return ['en', 'ko', 'zh'].includes(config.language) ? config.language : null;
+  } catch {
+    return null;
+  }
+}
+
 function isAlwaysUpdatePath(src) {
   const rel = path.relative(root, src).replace(/\\/g, '/');
   return rel.startsWith('templates/claude/commands/') ||
     rel.startsWith('templates/claude/skills/') ||
     rel.startsWith('templates/codex/skills/') ||
-    rel.startsWith('templates/tink/maintenance/');
+    rel.startsWith('templates/tink/maintenance/') ||
+    rel.startsWith('templates/tink/tools/');
 }
 
 function isGeneratedLegacyRuleGraph(src, dest) {
@@ -790,6 +800,27 @@ async function resolveChoices() {
     return { agent, scope, components, gitPolicy, hookScope, language };
   }
 
+  if (isUpdate) {
+    language = detectInstalledLanguage() || language;
+    const copy = COPY[language];
+    printBanner();
+    intro(pc.bgBlue(pc.white(copy.intro)));
+    log.message(`${copy.source}: ${source}`);
+    agent = handleCancel(await select({
+      message: language === 'ko'
+        ? '업데이트할 agent surface를 선택하세요 (나머지는 자동으로 최신화됩니다)'
+        : language === 'zh'
+          ? '选择要更新的 agent surface（其余将自动更新到最新）'
+          : 'Select agent surface to update (everything else refreshes automatically)',
+      options: SURFACE_OPTIONS[language],
+      initialValue: agent
+    }));
+    components = defaultComponentValues(agent, language);
+    scope = scope || 'repo';
+    if (components.includes('hook')) hookScope = scope;
+    return { agent, scope, components, gitPolicy, hookScope, language };
+  }
+
   language = handleCancel(await select({
     message: COPY[language].language,
     options: [

package/commands/update.md

@@ -1,86 +1,86 @@
----
-description: Detect install source, diagnose user-modified files, and show the safe update command.
----
-
-# /tink:update
-
-Tink를 최신 버전으로 안전하게 업데이트하는 방법을 안내합니다.
-
-## What this command does
-This command does not run the update itself. It detects how Tink was installed in this project, diagnoses whether any user-modified files are at risk, and shows the correct command to run.
-
-## Procedure
-1. **Source-repo guard (first):** If the project root contains all of `templates/tink/`, `bin/install.js`, and a `package.json` whose `name` is `"tink-harness"`, this is the tink-harness source repository itself — not a consumer install. Skip the rest of the procedure and emit the "source repo" output (see below). Do not show plugin or npx update commands in this case.
-2. Detect install source:
-   - If the project root (or `cwd`) has `.claude-plugin/plugin.json` and a top-level `commands/` directory, Tink was installed via Claude Code plugin marketplace.
-   - Otherwise, treat it as an `npx tink-harness install` (standalone) installation.
-3. Scan for files that have diverged from the latest installed templates (read-only inspection only):
-   - **Always updated**: `.claude/commands/tink/`, `.claude/skills/tink/`, `.tink/maintenance/` — template changes always propagate here.
-   - **Preserved if user-modified**: `.tink/harnesses/`, `.tink/hooks/`, `.tink/memory/`, `.tink/config.json` — respects `weave` customizations and local configuration.
-4. Show the appropriate update path and a short list of files in the "preserved" category that have diverged.
-
-## Update path: Claude Code plugin
-```text
-/plugin marketplace update tink-harness
-/plugin update tink@tink-harness
-/reload-plugins
-```
-If update is not detected, uninstall and reinstall:
-```text
-/plugin uninstall tink@tink-harness
-/plugin install tink@tink-harness
-```
-The plugin path is handled by Claude Code and does not touch the local `.tink/` directory.
-
-## Update path: npx (standalone)
-```text
-npx tink-harness@latest update
-```
-
-The `update` subcommand:
-- **Always overwrites**: commands, skills, and maintenance files (`.claude/commands/tink/`, `.claude/skills/tink/`, `.tink/maintenance/`) — so you get the latest harness runner and command behavior automatically.
-- **Preserves if modified**: harnesses, hooks, memory, and config (`.tink/harnesses/`, `.tink/hooks/`, `.tink/memory/`, `.tink/config.json`) — respects your `weave` customizations and local settings.
-
-## Output format (source repo)
-
-If the source-repo guard triggers, print only this and stop — do not present plugin or npx commands:
-
-```text
-### 🧶 Tink 업데이트 안내
-
-이 디렉토리는 tink-harness **소스 리포지토리**입니다. 일반 사용자 업데이트 대상이 아니에요.
-
-- 개발 변경 반영: `git pull` 후 일반적인 빌드/테스트 흐름을 사용하세요.
-- 사용자 환경에서 업데이트 흐름을 검증하려면 별도의 프로젝트 디렉토리에서 이 명령을 실행하세요.
-```
-
-## Output format
-
-```text
-### 🧶 Tink 업데이트 안내
-
-**설치 경로**: <plugin marketplace | npx standalone>
-
-**항상 업데이트됨**: commands, skills, maintenance (최신 버전으로 자동 반영)
-
-**사용자 수정 파일** (업데이트 시 보존):
-- <path1>
-- <path2>
-- (보존할 파일 없음)
-
-**업데이트 명령**:
-<command lines>
-
-? 어떻게 할까요?
-1. 위 명령 복사해서 직접 실행
-2. 변경 사항 미리 보기 (`npx tink-harness update --dry-run`)  ← npx standalone에서만 표시
-3. 취소
-```
-
-Use `AskUserQuestion`. Show option 2 (dry-run) **only on the npx standalone path** — Claude Code plugin updates have no dry-run equivalent. So: plugin path → 2 options (run / cancel); npx path → 3 options (run / dry-run / cancel).
-
-## Do not
-- Do not actually run the update command — show it for the user to run in their shell or Claude Code.
-- Do not modify `.tink/` files during diagnosis.
-- Do not bypass the user choice; always offer cancel.
-- Do not present plugin or npx update commands when the source-repo guard triggers — the user is editing tink-harness itself and would get misleading instructions.
+---
+description: Detect install source, diagnose user-modified files, and show the safe update command.
+---
+
+# /tink:update
+
+Tink를 최신 버전으로 안전하게 업데이트하는 방법을 안내합니다.
+
+## What this command does
+This command does not run the update itself. It detects how Tink was installed in this project, diagnoses whether any user-modified files are at risk, and shows the correct command to run.
+
+## Procedure
+1. **Source-repo guard (first):** If the project root contains all of `templates/tink/`, `bin/install.js`, and a `package.json` whose `name` is `"tink-harness"`, this is the tink-harness source repository itself — not a consumer install. Skip the rest of the procedure and emit the "source repo" output (see below). Do not show plugin or npx update commands in this case.
+2. Detect install source:
+   - If the project root (or `cwd`) has `.claude-plugin/plugin.json` and a top-level `commands/` directory, Tink was installed via Claude Code plugin marketplace.
+   - Otherwise, treat it as an `npx tink-harness install` (standalone) installation.
+3. Scan for files that have diverged from the latest installed templates (read-only inspection only):
+   - **Always updated**: `.claude/commands/tink/`, `.claude/skills/tink/`, `.tink/maintenance/`, `.tink/tools/` — template changes always propagate here.
+   - **Preserved if user-modified**: `.tink/harnesses/`, `.tink/hooks/`, `.tink/memory/`, `.tink/config.json` — respects `weave` customizations and local configuration.
+4. Show the appropriate update path and a short list of files in the "preserved" category that have diverged.
+
+## Update path: Claude Code plugin
+```text
+/plugin marketplace update tink-harness
+/plugin update tink@tink-harness
+/reload-plugins
+```
+If update is not detected, uninstall and reinstall:
+```text
+/plugin uninstall tink@tink-harness
+/plugin install tink@tink-harness
+```
+The plugin path is handled by Claude Code and does not touch the local `.tink/` directory.
+
+## Update path: npx (standalone)
+```text
+npx tink-harness@latest update
+```
+
+The `update` subcommand asks only one question - which agent surface to refresh (Claude Code, Codex, or both). Everything else updates automatically:
+- **Always overwrites**: commands, skills, maintenance, and runtime tools (`.claude/commands/tink/`, `.claude/skills/tink/`, `.tink/maintenance/`, `.tink/tools/`) — so you get the latest harness runner, report tools, and command behavior automatically.
+- **Preserves if modified**: harnesses, hooks, memory, and config (`.tink/harnesses/`, `.tink/hooks/`, `.tink/memory/`, `.tink/config.json`) — respects your `weave` customizations and local settings.
+
+## Output format (source repo)
+
+If the source-repo guard triggers, print only this and stop — do not present plugin or npx commands:
+
+```text
+### 🧶 Tink 업데이트 안내
+
+이 디렉토리는 tink-harness **소스 리포지토리**입니다. 일반 사용자 업데이트 대상이 아니에요.
+
+- 개발 변경 반영: `git pull` 후 일반적인 빌드/테스트 흐름을 사용하세요.
+- 사용자 환경에서 업데이트 흐름을 검증하려면 별도의 프로젝트 디렉토리에서 이 명령을 실행하세요.
+```
+
+## Output format
+
+```text
+### 🧶 Tink 업데이트 안내
+
+**설치 경로**: <plugin marketplace | npx standalone>
+
+**항상 업데이트됨**: commands, skills, maintenance, tools (최신 버전으로 자동 반영)
+
+**사용자 수정 파일** (업데이트 시 보존):
+- <path1>
+- <path2>
+- (보존할 파일 없음)
+
+**업데이트 명령**:
+<command lines>
+
+? 어떻게 할까요?
+1. 위 명령 복사해서 직접 실행
+2. 변경 사항 미리 보기 (`npx tink-harness update --dry-run`)  ← npx standalone에서만 표시
+3. 취소
+```
+
+Use `AskUserQuestion`. Show option 2 (dry-run) **only on the npx standalone path** — Claude Code plugin updates have no dry-run equivalent. So: plugin path → 2 options (run / cancel); npx path → 3 options (run / dry-run / cancel).
+
+## Do not
+- Do not actually run the update command — show it for the user to run in their shell or Claude Code.
+- Do not modify `.tink/` files during diagnosis.
+- Do not bypass the user choice; always offer cancel.
+- Do not present plugin or npx update commands when the source-repo guard triggers — the user is editing tink-harness itself and would get misleading instructions.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "tink-harness",
-  "version": "1.9.12",
+  "version": "1.9.14",
   "description": "Self-growing harnesses for Claude Code and Codex.",
   "license": "MIT",
   "type": "module",

package/templates/claude/commands/tink/update.md

@@ -1,86 +1,86 @@
----
-description: Detect install source, diagnose user-modified files, and show the safe update command.
----
-
-# /tink:update
-
-Tink를 최신 버전으로 안전하게 업데이트하는 방법을 안내합니다.
-
-## What this command does
-This command does not run the update itself. It detects how Tink was installed in this project, diagnoses whether any user-modified files are at risk, and shows the correct command to run.
-
-## Procedure
-1. **Source-repo guard (first):** If the project root contains all of `templates/tink/`, `bin/install.js`, and a `package.json` whose `name` is `"tink-harness"`, this is the tink-harness source repository itself — not a consumer install. Skip the rest of the procedure and emit the "source repo" output (see below). Do not show plugin or npx update commands in this case.
-2. Detect install source:
-   - If the project root (or `cwd`) has `.claude-plugin/plugin.json` and a top-level `commands/` directory, Tink was installed via Claude Code plugin marketplace.
-   - Otherwise, treat it as an `npx tink-harness install` (standalone) installation.
-3. Scan for files that have diverged from the latest installed templates (read-only inspection only):
-   - **Always updated**: `.claude/commands/tink/`, `.claude/skills/tink/`, `.tink/maintenance/` — template changes always propagate here.
-   - **Preserved if user-modified**: `.tink/harnesses/`, `.tink/hooks/`, `.tink/memory/`, `.tink/config.json` — respects `weave` customizations and local configuration.
-4. Show the appropriate update path and a short list of files in the "preserved" category that have diverged.
-
-## Update path: Claude Code plugin
-```text
-/plugin marketplace update tink-harness
-/plugin update tink@tink-harness
-/reload-plugins
-```
-If update is not detected, uninstall and reinstall:
-```text
-/plugin uninstall tink@tink-harness
-/plugin install tink@tink-harness
-```
-The plugin path is handled by Claude Code and does not touch the local `.tink/` directory.
-
-## Update path: npx (standalone)
-```text
-npx tink-harness@latest update
-```
-
-The `update` subcommand:
-- **Always overwrites**: commands, skills, and maintenance files (`.claude/commands/tink/`, `.claude/skills/tink/`, `.tink/maintenance/`) — so you get the latest harness runner and command behavior automatically.
-- **Preserves if modified**: harnesses, hooks, memory, and config (`.tink/harnesses/`, `.tink/hooks/`, `.tink/memory/`, `.tink/config.json`) — respects your `weave` customizations and local settings.
-
-## Output format (source repo)
-
-If the source-repo guard triggers, print only this and stop — do not present plugin or npx commands:
-
-```text
-### 🧶 Tink 업데이트 안내
-
-이 디렉토리는 tink-harness **소스 리포지토리**입니다. 일반 사용자 업데이트 대상이 아니에요.
-
-- 개발 변경 반영: `git pull` 후 일반적인 빌드/테스트 흐름을 사용하세요.
-- 사용자 환경에서 업데이트 흐름을 검증하려면 별도의 프로젝트 디렉토리에서 이 명령을 실행하세요.
-```
-
-## Output format
-
-```text
-### 🧶 Tink 업데이트 안내
-
-**설치 경로**: <plugin marketplace | npx standalone>
-
-**항상 업데이트됨**: commands, skills, maintenance (최신 버전으로 자동 반영)
-
-**사용자 수정 파일** (업데이트 시 보존):
-- <path1>
-- <path2>
-- (보존할 파일 없음)
-
-**업데이트 명령**:
-<command lines>
-
-? 어떻게 할까요?
-1. 위 명령 복사해서 직접 실행
-2. 변경 사항 미리 보기 (`npx tink-harness update --dry-run`)  ← npx standalone에서만 표시
-3. 취소
-```
-
-Use `AskUserQuestion`. Show option 2 (dry-run) **only on the npx standalone path** — Claude Code plugin updates have no dry-run equivalent. So: plugin path → 2 options (run / cancel); npx path → 3 options (run / dry-run / cancel).
-
-## Do not
-- Do not actually run the update command — show it for the user to run in their shell or Claude Code.
-- Do not modify `.tink/` files during diagnosis.
-- Do not bypass the user choice; always offer cancel.
-- Do not present plugin or npx update commands when the source-repo guard triggers — the user is editing tink-harness itself and would get misleading instructions.
+---
+description: Detect install source, diagnose user-modified files, and show the safe update command.
+---
+
+# /tink:update
+
+Tink를 최신 버전으로 안전하게 업데이트하는 방법을 안내합니다.
+
+## What this command does
+This command does not run the update itself. It detects how Tink was installed in this project, diagnoses whether any user-modified files are at risk, and shows the correct command to run.
+
+## Procedure
+1. **Source-repo guard (first):** If the project root contains all of `templates/tink/`, `bin/install.js`, and a `package.json` whose `name` is `"tink-harness"`, this is the tink-harness source repository itself — not a consumer install. Skip the rest of the procedure and emit the "source repo" output (see below). Do not show plugin or npx update commands in this case.
+2. Detect install source:
+   - If the project root (or `cwd`) has `.claude-plugin/plugin.json` and a top-level `commands/` directory, Tink was installed via Claude Code plugin marketplace.
+   - Otherwise, treat it as an `npx tink-harness install` (standalone) installation.
+3. Scan for files that have diverged from the latest installed templates (read-only inspection only):
+   - **Always updated**: `.claude/commands/tink/`, `.claude/skills/tink/`, `.tink/maintenance/`, `.tink/tools/` — template changes always propagate here.
+   - **Preserved if user-modified**: `.tink/harnesses/`, `.tink/hooks/`, `.tink/memory/`, `.tink/config.json` — respects `weave` customizations and local configuration.
+4. Show the appropriate update path and a short list of files in the "preserved" category that have diverged.
+
+## Update path: Claude Code plugin
+```text
+/plugin marketplace update tink-harness
+/plugin update tink@tink-harness
+/reload-plugins
+```
+If update is not detected, uninstall and reinstall:
+```text
+/plugin uninstall tink@tink-harness
+/plugin install tink@tink-harness
+```
+The plugin path is handled by Claude Code and does not touch the local `.tink/` directory.
+
+## Update path: npx (standalone)
+```text
+npx tink-harness@latest update
+```
+
+The `update` subcommand asks only one question - which agent surface to refresh (Claude Code, Codex, or both). Everything else updates automatically:
+- **Always overwrites**: commands, skills, maintenance, and runtime tools (`.claude/commands/tink/`, `.claude/skills/tink/`, `.tink/maintenance/`, `.tink/tools/`) — so you get the latest harness runner, report tools, and command behavior automatically.
+- **Preserves if modified**: harnesses, hooks, memory, and config (`.tink/harnesses/`, `.tink/hooks/`, `.tink/memory/`, `.tink/config.json`) — respects your `weave` customizations and local settings.
+
+## Output format (source repo)
+
+If the source-repo guard triggers, print only this and stop — do not present plugin or npx commands:
+
+```text
+### 🧶 Tink 업데이트 안내
+
+이 디렉토리는 tink-harness **소스 리포지토리**입니다. 일반 사용자 업데이트 대상이 아니에요.
+
+- 개발 변경 반영: `git pull` 후 일반적인 빌드/테스트 흐름을 사용하세요.
+- 사용자 환경에서 업데이트 흐름을 검증하려면 별도의 프로젝트 디렉토리에서 이 명령을 실행하세요.
+```
+
+## Output format
+
+```text
+### 🧶 Tink 업데이트 안내
+
+**설치 경로**: <plugin marketplace | npx standalone>
+
+**항상 업데이트됨**: commands, skills, maintenance, tools (최신 버전으로 자동 반영)
+
+**사용자 수정 파일** (업데이트 시 보존):
+- <path1>
+- <path2>
+- (보존할 파일 없음)
+
+**업데이트 명령**:
+<command lines>
+
+? 어떻게 할까요?
+1. 위 명령 복사해서 직접 실행
+2. 변경 사항 미리 보기 (`npx tink-harness update --dry-run`)  ← npx standalone에서만 표시
+3. 취소
+```
+
+Use `AskUserQuestion`. Show option 2 (dry-run) **only on the npx standalone path** — Claude Code plugin updates have no dry-run equivalent. So: plugin path → 2 options (run / cancel); npx path → 3 options (run / dry-run / cancel).
+
+## Do not
+- Do not actually run the update command — show it for the user to run in their shell or Claude Code.
+- Do not modify `.tink/` files during diagnosis.
+- Do not bypass the user choice; always offer cancel.
+- Do not present plugin or npx update commands when the source-repo guard triggers — the user is editing tink-harness itself and would get misleading instructions.