tink-harness 1.9.11 → 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.11",
+  "version": "1.9.13",
   "author": {
     "name": "dotori"
   }

package/CHANGELOG.md

@@ -6,6 +6,28 @@ 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
+
+- Restyled the dashboard with a warm editorial palette (charcoal/ivory/amber) in place of the generic black-and-blue look, with softer semantic tones and larger radii.
+- Improved harness-tab readability: bigger card titles, labels, detail text, and history entries with more breathing room.
+
+### Added
+
+- Next-action suggestions now provide copy-paste commands for both Claude Code (`/tink:...`) and Codex (`$tink:...`).
+- README (EN/KO) refreshed: latest-package summary, release badge, and an up-to-date description of the tabbed dashboard, 3D harness map, and next-action panel.
+
 ## [1.9.11] - 2026-06-11
 
 ### Changed

package/README.ko.md

@@ -8,7 +8,7 @@ Claude Code와 Codex를 위한 작은 하네스 레이어입니다.
 
 Tink는 지금 작업에 맞는 하네스를 고르고, 실행 상태를 보이게 만들고, 실제 사용 중 생긴 실패와 피드백으로 하네스 세트를 개선합니다.
 
-**최신 패키지:** v1.9.1 — 하네스 건강 요약, graph, timeline, 후보 점수, 생애주기 상태, 정적 로컬 리포트를 추가합니다. 전체 변경 이력은 [CHANGELOG](CHANGELOG.md)를 확인하세요.
+**최신 패키지:** v1.9.13 — 로컬 건강 리포트가 탭형 대시보드로 바뀌었습니다. 3D 하네스 지도, 쉬운 말 건강 요약, Claude Code와 Codex 양쪽 복사-붙여넣기 명령이 포함된 다음 행동 제안을 제공합니다. 전체 변경 이력은 [CHANGELOG](CHANGELOG.md)를 확인하세요.
 
 [English](README.md) · **한국어** · [변경 이력](CHANGELOG.md)
 
@@ -131,7 +131,7 @@ node .tink/tools/generate-harness-lifecycle-summary.mjs
 node .tink/tools/render-harness-health-report.mjs
 ```
 
-리포트는 정적 대시보드 형태입니다. graph overview, 최근 run timeline, 하네스별 카드를 보여주지만 서버를 시작하거나, 파일을 감시하거나, hidden cache를 만들거나, 새 public `tink index` 명령을 추가하지 않습니다.
+리포트는 정적인 탭형 로컬 페이지입니다. 홈 요약, 사용량 순 하네스 카드와 평가·생성 히스토리, 메모리 참조, run 활동 피드, 그리고 인터랙티브 3D 하네스 지도(드래그 이동, 우클릭 드래그 회전, 휠 확대 — three.js를 CDN에서 불러오며 오프라인이면 안내가 표시됩니다)를 제공합니다. 하네스나 건강 그룹을 선택하면 쉬운 말 요약과 함께 Claude Code(`/tink:...`)·Codex(`$tink:...`) 양쪽 복사용 명령이 포함된 다음 행동을 제안합니다. 여전히 서버를 시작하거나, 파일을 감시하거나, hidden cache를 만들거나, 새 public `tink index` 명령을 추가하지 않습니다 — 제안만 하며, 재사용 상태 변경은 기존 승인 절차를 그대로 따릅니다.
 
 선택된 하네스에 따라 `.tink/current/goals.json`에는 현재 실행의 목표 체크포인트가, `.tink/current/delegation.md`에는 인수인계 패킷이 추가될 수 있습니다. Tink는 이런 브리프를 보이는 상태로 준비하지만, 별도 승인된 워크플로가 아니면 worker, tmux pane, worktree를 시작하지 않습니다.
 

package/README.md

@@ -17,14 +17,14 @@
 </p>
 
 <p>
-  <a href="https://github.com/dotoricode/tink-harness/releases/tag/v1.9.1"><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.1 - Adds harness health summaries with graph, timeline, scoring, lifecycle states, and a static local report. 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)
 
@@ -210,7 +210,7 @@ node .tink/tools/generate-harness-lifecycle-summary.mjs
 node .tink/tools/render-harness-health-report.mjs
 ```
 
-The report is a static dashboard-style page with a graph overview, recent run timeline, and one card per harness. It does not start a server, watch files, create a hidden cache, or add a public `tink index` command.
+The report is a static, tabbed local page: a home overview, usage-sorted harness cards with an evaluation/maintenance history, memory references, a run activity feed, and an interactive 3D harness map (drag to move, right-drag to rotate, wheel to zoom; rendered with three.js from a CDN, with an offline notice when unavailable). Selecting a harness or health group shows a plain-language summary plus a suggested next action with copy-paste commands for both Claude Code (`/tink:...`) and Codex (`$tink:...`). It still does not start a server, watch files, create a hidden cache, or add a public `tink index` command - suggestions only; reusable-state changes keep their approval gates.
 
 When selected, current-run artifacts may also include `.tink/current/goals.json` for goal checkpoints or `.tink/current/delegation.md` for handoff packets. Tink prepares those briefs as visible state; it does not start workers, tmux panes, or worktrees unless a separate approved workflow does so.
 

package/VERSIONING.md

@@ -1,6 +1,6 @@
 # Versioning
 
-Current version: `1.9.11`
+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.11",
+  "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.

package/templates/tink/tools/render-harness-health-report.mjs

@@ -162,10 +162,10 @@ const COPY = {
     },
     actions: {
       keep: { what: 'Healthy and proven by records.', next: 'No action needed - just keep using it.', command: '', expect: '' },
-      observe: { what: 'Not enough records to judge yet.', next: 'Keep working normally with /tink:cast so records accumulate.', command: '/tink:cast', expect: 'What happens: it picks the right harness for your task, plans the run, and the work gets recorded - improving future judgments.' },
-      weave: { what: 'Repeated friction shows up in the records.', next: 'Run /tink:weave to prepare a small improvement proposal.', command: '/tink:weave', expect: 'What happens: it drafts an improvement (e.g. updated instructions) from the recorded friction and shows it to you. Nothing changes until you approve.' },
-      merge_candidate: { what: 'Often used together with another harness.', next: 'Run /tink:weave to check the overlap and decide whether to combine them.', command: '/tink:weave', expect: 'What happens: it inspects the overlap evidence and proposes whether to combine or keep separate. Nothing changes until you approve.' },
-      frog_candidate: { what: 'Repeated trouble plus high cost - cleanup candidates.', next: 'Run /tink:frog to review archive/delete with approval.', command: '/tink:frog', expect: 'What happens: it lists cleanup candidates with their evidence. Archiving or deleting only happens after your explicit approval.' }
+      observe: { what: 'Not enough records to judge yet.', next: 'Keep working normally with /tink:cast so records accumulate.', command: 'tink:cast', expect: 'What happens: it picks the right harness for your task, plans the run, and the work gets recorded - improving future judgments.' },
+      weave: { what: 'Repeated friction shows up in the records.', next: 'Run /tink:weave to prepare a small improvement proposal.', command: 'tink:weave', expect: 'What happens: it drafts an improvement (e.g. updated instructions) from the recorded friction and shows it to you. Nothing changes until you approve.' },
+      merge_candidate: { what: 'Often used together with another harness.', next: 'Run /tink:weave to check the overlap and decide whether to combine them.', command: 'tink:weave', expect: 'What happens: it inspects the overlap evidence and proposes whether to combine or keep separate. Nothing changes until you approve.' },
+      frog_candidate: { what: 'Repeated trouble plus high cost - cleanup candidates.', next: 'Run /tink:frog to review archive/delete with approval.', command: 'tink:frog', expect: 'What happens: it lists cleanup candidates with their evidence. Archiving or deleting only happens after your explicit approval.' }
     },
     recPlain: {
       keep: 'Working well - keep using it as is.',
@@ -300,10 +300,10 @@ COPY.ko = {
   },
   actions: {
     keep: { what: '기록으로 잘 검증되어 있어요.', next: '별도 행동이 필요 없어요 — 계속 사용하면 됩니다.', command: '', expect: '' },
-    observe: { what: '아직 판단할 기록이 부족해요.', next: '/tink:cast로 평소처럼 작업하면 기록이 쌓여 판단이 정확해져요.', command: '/tink:cast', expect: '실행하면: 작업에 맞는 하네스를 골라 계획을 세우고, 끝나면 이번 작업이 기록으로 남아 다음 판단이 정확해져요.' },
-    weave: { what: '반복되는 마찰이 기록되어 있어요.', next: '/tink:weave를 실행해 작은 개선 제안을 준비하세요.', command: '/tink:weave', expect: '실행하면: 기록된 마찰을 바탕으로 개선안(지침 수정 등)을 만들어 보여줘요. 승인하기 전에는 아무것도 바뀌지 않아요.' },
-    merge_candidate: { what: '다른 하네스와 자주 함께 쓰여요.', next: '/tink:weave로 겹침을 확인하고 합칠지 검토하세요.', command: '/tink:weave', expect: '실행하면: 겹침 근거를 살펴보고 합칠지 따로 둘지 제안해 줘요. 승인 전에는 아무것도 바뀌지 않아요.' },
-    frog_candidate: { what: '반복 문제와 높은 비용이 기록됐어요 — 정리 후보예요.', next: '/tink:frog로 보관/삭제 검토를 승인 절차와 함께 진행하세요.', command: '/tink:frog', expect: '실행하면: 정리 후보와 근거를 정리해 보여줘요. 보관·삭제는 명시적으로 승인해야만 실제로 진행돼요.' }
+    observe: { what: '아직 판단할 기록이 부족해요.', next: '/tink:cast로 평소처럼 작업하면 기록이 쌓여 판단이 정확해져요.', command: 'tink:cast', expect: '실행하면: 작업에 맞는 하네스를 골라 계획을 세우고, 끝나면 이번 작업이 기록으로 남아 다음 판단이 정확해져요.' },
+    weave: { what: '반복되는 마찰이 기록되어 있어요.', next: '/tink:weave를 실행해 작은 개선 제안을 준비하세요.', command: 'tink:weave', expect: '실행하면: 기록된 마찰을 바탕으로 개선안(지침 수정 등)을 만들어 보여줘요. 승인하기 전에는 아무것도 바뀌지 않아요.' },
+    merge_candidate: { what: '다른 하네스와 자주 함께 쓰여요.', next: '/tink:weave로 겹침을 확인하고 합칠지 검토하세요.', command: 'tink:weave', expect: '실행하면: 겹침 근거를 살펴보고 합칠지 따로 둘지 제안해 줘요. 승인 전에는 아무것도 바뀌지 않아요.' },
+    frog_candidate: { what: '반복 문제와 높은 비용이 기록됐어요 — 정리 후보예요.', next: '/tink:frog로 보관/삭제 검토를 승인 절차와 함께 진행하세요.', command: 'tink:frog', expect: '실행하면: 정리 후보와 근거를 정리해 보여줘요. 보관·삭제는 명시적으로 승인해야만 실제로 진행돼요.' }
   },
   recPlain: {
     keep: '잘 쓰이고 있어요 — 그대로 유지하면 됩니다.',
@@ -1558,14 +1558,17 @@ function renderScript(harnesses, copy) {
           actionPanel.innerHTML = head + '<p class="action-body">' + esc(copy.actionDefault || '') + '</p>';
           return;
         }
-        const command = action.command ? (harnessId ? action.command + ' ' + harnessId : action.command) : '';
+        const suffix = harnessId ? ' ' + harnessId : '';
+        const cmdRow = (label, value) =>
+          '<div class="cmd-row"><span class="cmd-label">' + esc(label) + '</span><code>' + esc(value) + '</code>' +
+          '<button class="copy-btn" type="button" data-copy-cmd="' + esc(value) + '">' + esc(copy.copyCmd || 'Copy') + '</button></div>';
         actionPanel.innerHTML = head +
           (harnessId ? '<p class="action-target">' + esc(copy.actionTarget || 'Target') + ': <strong>' + esc(harnessId) + '</strong></p>' : '') +
           '<p class="action-body">' + esc(action.what || '') + '</p>' +
           '<p class="action-next">' + esc(action.next || '') + '</p>' +
-          (command
-            ? '<div class="cmd-row"><code>' + esc(command) + '</code>' +
-              '<button class="copy-btn" type="button" data-copy-cmd="' + esc(command) + '">' + esc(copy.copyCmd || 'Copy') + '</button></div>' +
+          (action.command
+            ? cmdRow('Claude Code', '/' + action.command + suffix) +
+              cmdRow('Codex', '$' + action.command + suffix) +
               (action.expect ? '<p class="action-expect">' + esc(action.expect) + '</p>' : '') +
               '<p class="action-caveat">' + esc(copy.actionCaveat || '') + '</p>'
             : '');
@@ -2280,30 +2283,30 @@ function renderStyles() {
   return `<style>
     :root {
       color-scheme: dark;
-      --bg-page: #0A0A0A;
-      --bg-card: #111111;
-      --bg-hover: #161616;
-      --bg-selected: #1C1C1C;
-      --border-default: #1F1F1F;
-      --border-hover: #2A2A2A;
-      --border-strong: #383838;
-      --text-primary: #E8E8E8;
-      --text-secondary: #666666;
-      --text-muted: #3D3D3D;
-      --accent: #2563EB;
-      --accent-dim: #1E2D4A;
-      --accent-text: #93C5FD;
-      --success: #22C55E;
-      --success-dim: #14291E;
-      --warning: #F59E0B;
-      --warning-dim: #2A1F0A;
-      --danger: #EF4444;
-      --danger-dim: #2A0F0F;
-      --font-ui: 'IBM Plex Sans', -apple-system, sans-serif;
+      --bg-page: #171511;
+      --bg-card: #1E1B16;
+      --bg-hover: #25211A;
+      --bg-selected: #2C2720;
+      --border-default: #2D2820;
+      --border-hover: #3B342A;
+      --border-strong: #4C4336;
+      --text-primary: #EBE4D6;
+      --text-secondary: #A2988A;
+      --text-muted: #645B4E;
+      --accent: #C9913F;
+      --accent-dim: #3A2F1B;
+      --accent-text: #E2B873;
+      --success: #8FAE76;
+      --success-dim: #28301F;
+      --warning: #D2A24A;
+      --warning-dim: #342917;
+      --danger: #C97862;
+      --danger-dim: #34221C;
+      --font-ui: 'Avenir Next', 'Pretendard', 'IBM Plex Sans', -apple-system, 'Segoe UI', sans-serif;
       --font-mono: 'IBM Plex Mono', 'Fira Code', monospace;
-      --radius-sm: 4px;
-      --radius-md: 6px;
-      --radius-lg: 8px;
+      --radius-sm: 5px;
+      --radius-md: 8px;
+      --radius-lg: 12px;
       --border-width: 1px;
       --space-1: 4px;
       --space-2: 8px;
@@ -2311,12 +2314,12 @@ function renderStyles() {
       --space-4: 16px;
       --space-6: 24px;
       --space-8: 32px;
-      --chart-line: #2563EB;
+      --chart-line: #C9913F;
       --chart-line-w: 1.5px;
-      --chart-area: rgba(37, 99, 235, 0.06);
-      --chart-grid: #1F1F1F;
-      --chart-dot-fill: #111111;
-      --chart-dot-stroke: #2563EB;
+      --chart-area: rgba(201, 145, 63, 0.07);
+      --chart-grid: #2D2820;
+      --chart-dot-fill: #1E1B16;
+      --chart-dot-stroke: #C9913F;
     }
 
     * { box-sizing: border-box; }
@@ -3047,7 +3050,7 @@ function renderStyles() {
       padding: 6px 12px;
       border-radius: var(--radius-md);
       border: 1px solid var(--border-default);
-      background: rgba(10, 10, 14, 0.78);
+      background: rgba(23, 21, 17, 0.82);
       color: var(--text-secondary);
       font-size: 12px;
       pointer-events: none;
@@ -3188,6 +3191,13 @@ function renderStyles() {
       flex-wrap: wrap;
     }
 
+    .cmd-label {
+      min-width: 78px;
+      color: var(--text-muted);
+      font-size: 11.5px;
+      white-space: nowrap;
+    }
+
     .cmd-row code {
       background: var(--bg-hover);
       border: 1px solid var(--border-default);
@@ -3485,13 +3495,14 @@ function renderStyles() {
 
     .harness-summary:hover { background: var(--bg-hover); }
 
-    .harness-summary .eyebrow { margin: 0 0 2px; font-size: 10px; }
+    .harness-summary .eyebrow { margin: 0 0 3px; font-size: 11.5px; letter-spacing: 0.03em; }
 
     .harness-summary h3 {
       margin: 0;
-      font-size: 14px;
-      line-height: 1.25;
+      font-size: 15.5px;
+      line-height: 1.3;
       font-weight: 600;
+      letter-spacing: -0.01em;
       overflow-wrap: anywhere;
     }
 
@@ -3503,12 +3514,12 @@ function renderStyles() {
 
     .harness-mini span {
       color: var(--text-secondary);
-      font-size: 11px;
+      font-size: 12.5px;
       white-space: nowrap;
     }
 
     .harness-mini strong {
-      font-size: 18px;
+      font-size: 20px;
       line-height: 1;
       font-family: var(--font-mono);
       font-weight: 600;
@@ -3552,16 +3563,15 @@ function renderStyles() {
     .harness-reason {
       margin: 0;
       color: var(--text-secondary);
-      font-size: 12px;
-      line-height: 1.5;
+      font-size: 13.5px;
+      line-height: 1.6;
     }
 
     .detail-label {
-      margin: var(--space-1) 0 0;
+      margin: var(--space-2) 0 0;
       color: var(--text-secondary);
-      font-size: 10px;
-      text-transform: uppercase;
-      letter-spacing: 0.06em;
+      font-size: 11.5px;
+      letter-spacing: 0.04em;
     }
 
     .co-used-chips { display: flex; flex-wrap: wrap; gap: 6px; }
@@ -3588,7 +3598,7 @@ function renderStyles() {
       display: flex;
       justify-content: space-between;
       gap: var(--space-2);
-      font-size: 12px;
+      font-size: 13px;
       color: var(--text-secondary);
     }
 
@@ -3597,17 +3607,17 @@ function renderStyles() {
     .harness-next {
       margin: 0;
       color: var(--text-primary);
-      font-size: 12px;
-      line-height: 1.5;
+      font-size: 13.5px;
+      line-height: 1.6;
     }
 
     .evidence-list {
       margin: 0;
       padding-left: 16px;
       color: var(--text-secondary);
-      font-size: 11px;
+      font-size: 12.5px;
       display: grid;
-      gap: 3px;
+      gap: 4px;
     }
 
     .harness-card .link-button { margin-top: var(--space-1); justify-self: start; }
@@ -3628,19 +3638,19 @@ function renderStyles() {
 
     .history-feed li {
       display: grid;
-      grid-template-columns: 110px 1fr;
+      grid-template-columns: 120px 1fr;
       gap: var(--space-3);
       align-items: start;
       border: 1px solid var(--border-default);
       border-radius: var(--radius-md);
       background: var(--bg-card);
-      padding: var(--space-2) var(--space-3);
+      padding: var(--space-3) var(--space-4);
     }
 
     .history-type {
       display: inline-block;
       font-family: var(--font-mono);
-      font-size: 10px;
+      font-size: 11px;
       text-transform: uppercase;
       letter-spacing: 0.05em;
       color: var(--text-secondary);
@@ -3657,12 +3667,12 @@ function renderStyles() {
     .history-type.harness-create,
     .history-type.harness-edit { color: var(--success); border-color: var(--success-dim); }
 
-    .history-feed strong { font-size: 12px; font-weight: 500; }
+    .history-feed strong { font-size: 13.5px; font-weight: 500; }
 
     .history-harnesses {
-      margin: 2px 0 0;
+      margin: 3px 0 0;
       color: var(--text-secondary);
-      font-size: 11px;
+      font-size: 12.5px;
       font-family: var(--font-mono);
     }