tink-harness 1.9.12 → 1.9.13

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.13",
   "author": {
     "name": "dotori"
   }

package/CHANGELOG.md

@@ -6,6 +6,16 @@ All notable changes to Tink are tracked here.
 
 No unreleased changes yet.
 
+## [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,7 +8,7 @@ Claude Code와 Codex를 위한 작은 하네스 레이어입니다.
 
 Tink는 지금 작업에 맞는 하네스를 고르고, 실행 상태를 보이게 만들고, 실제 사용 중 생긴 실패와 피드백으로 하네스 세트를 개선합니다.
 
-**최신 패키지:** v1.9.12 — 로컬 건강 리포트가 탭형 대시보드로 바뀌었습니다. 3D 하네스 지도, 쉬운 말 건강 요약, Claude Code와 Codex 양쪽 복사-붙여넣기 명령이 포함된 다음 행동 제안을 제공합니다. 전체 변경 이력은 [CHANGELOG](CHANGELOG.md)를 확인하세요.
+**최신 패키지:** v1.9.13 — 로컬 건강 리포트가 탭형 대시보드로 바뀌었습니다. 3D 하네스 지도, 쉬운 말 건강 요약, Claude Code와 Codex 양쪽 복사-붙여넣기 명령이 포함된 다음 행동 제안을 제공합니다. 전체 변경 이력은 [CHANGELOG](CHANGELOG.md)를 확인하세요.
 
 [English](README.md) · **한국어** · [변경 이력](CHANGELOG.md)
 

package/README.md

@@ -17,14 +17,14 @@
 </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.13"><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.13 - 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)
 

package/VERSIONING.md

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

package/bin/install.js

@@ -388,7 +388,8 @@ function isAlwaysUpdatePath(src) {
   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) {

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:
+- **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.13",
   "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:
+- **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.