tink-harness 1.10.0 → 1.11.0

package/.claude-plugin/plugin.json

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

package/CHANGELOG.md

@@ -2,6 +2,13 @@
 
 All notable changes to Tink are tracked here.
 
+## [1.11.0] - 2026-06-12
+
+- **Fixed: update wiped run history.** `.tink/maintenance/` record files (`ledger.jsonl`, `friction.jsonl`, `weave-queue.json`) were in the always-overwrite set, so every npx `update` replaced the user's approval ledger and weave/friction signals with empty seeds - silently resetting dashboard usage history. They are now seed-only: created when missing, never overwritten.
+- Fixed: update resurrected harnesses the user removed via an approved `/tink:frog` operation. The updater now reads `ledger.jsonl` frog entries and skips re-creating those files and index entries (other missing defaults are still restored; `--force` restores everything).
+- Fixed: `dashboard` reported "opened in browser" even when the opener failed (e.g. no `xdg-open`); it now detects failure and tells you to open the file manually. Also fixed the installer's harness count including the human catalog file, and a `/tink:list` example that contradicted its own category rules.
+- New `dashboard` subcommand: `npx tink-harness dashboard` generates the harness health report (lifecycle summary + HTML) from local `.tink` records and opens it in the default browser - no more memorizing the two `node .tink/tools/...` commands. `--no-open` generates the file only. Falls back to the packaged tools when `.tink/tools/` is missing, and finds `.tink` in the current or home directory.
+
 ## [1.10.0] - 2026-06-12
 
 - update: previously the npx `update` reset install scope and git policy to defaults; it now reuses the choices stored at install time (`.tink/config.json` gains `git_policy`). Choosing "커밋 안 함" (commit no .tink files) now means `.gitignore` is never created or edited - by install or by update - and a legacy whole-directory `.tink/` ignore line is left untouched.

package/README.ko.md

@@ -10,7 +10,7 @@ Tink는 사소하지 않은 모든 에이전트 작업을 눈에 보이는 파
 
 <sub>Claude Code와 Codex를 위한 작은 하네스 레이어</sub>
 
-**최신 패키지:** v1.10.0 — 기본 하네스가 기능 특화 세트로 바뀌었습니다. 일반 작업은 하네스 없이 기본 절차로 진행하고, update가 퇴역한 범용 하네스를 자동 정리하며 설치 때 선택(언어·범위·git 정책)을 재사용합니다. weave/frog에는 건강 요약 기반 정리와 임시초안 승격이 추가됐습니다. 전체 변경 이력은 [CHANGELOG](CHANGELOG.md)를 확인하세요.
+**최신 패키지:** v1.11.0 — 한 줄 대시보드: `npx tink-harness dashboard`로 하네스 건강 리포트를 만들고 브라우저로 바로 엽니다. update가 승인 이력·신호 기록을 지우던 심각한 버그와 frog로 삭제한 하네스가 부활하던 문제도 고쳤습니다. 전체 변경 이력은 [CHANGELOG](CHANGELOG.md)를 확인하세요.
 
 [English](README.md) · **한국어** · [변경 이력](CHANGELOG.md)
 
@@ -101,14 +101,14 @@ $tink:cast 인증 모듈 리팩터링     # Codex
 
 ## 하네스 건강을 눈으로 확인
 
-몇 번의 run이 쌓이면, 읽기 전용 helper 두 개가 기록을 로컬 대시보드로 바꿔 줍니다:
+몇 번의 run이 쌓이면, 명령 하나로 기록을 로컬 대시보드로 만들어 브라우저까지 열어 줍니다:
 
 ```bash
-node .tink/tools/generate-harness-lifecycle-summary.mjs
-node .tink/tools/render-harness-health-report.mjs
-# .tink/maintenance/harness-health-report.html 열기
+npx tink-harness dashboard          # 파일만 만들려면 --no-open 추가
 ```
 
+내부적으로는 읽기 전용 helper 두 개(`node .tink/tools/generate-harness-lifecycle-summary.mjs` → `node .tink/tools/render-harness-health-report.mjs`)를 실행한 뒤 `.tink/maintenance/harness-health-report.html`을 엽니다.
+
 ![Tink 대시보드 데모 — 건강 그룹 클릭, 하네스 카드 탐색, 3D 지도 조작](.github/assets/demo.gif)
 
 <sub>당신의 워크플로와 맞는다면, ⭐ 하나가 다른 개발자들이 찾는 데 도움이 됩니다.</sub>
@@ -147,7 +147,7 @@ Standalone / Codex:
 npx tink-harness@latest update
 ```
 
-업데이트는 질문 하나 — 어떤 agent surface를 갱신할지 — 만 묻고 나머지는 자동으로 처리합니다. 언어·설치 범위·git 정책은 설치 때 선택한 값을 그대로 재사용하며, ".tink 커밋 안 함"을 선택했다면 업데이트가 `.gitignore`를 절대 건드리지 않습니다. Tink가 관리하는 파일(commands, skills, maintenance, 런타임 tools)은 항상 최신으로 덮어쓰고, 사용자가 수정한 하네스·메모리·설정은 보존합니다.
+업데이트는 질문 하나 — 어떤 agent surface를 갱신할지 — 만 묻고 나머지는 자동으로 처리합니다. 언어·설치 범위·git 정책은 설치 때 선택한 값을 그대로 재사용하며, ".tink 커밋 안 함"을 선택했다면 업데이트가 `.gitignore`를 절대 건드리지 않습니다. Tink가 관리하는 파일(commands, skills, 런타임 tools)은 항상 최신으로 덮어쓰고, 사용자가 수정한 하네스·메모리·설정과 `.tink/maintenance/`의 모든 기록(ledger 등)은 보존합니다.
 
 `CODEX_HOME`을 지정하지 않으면 Windows에서는 `%USERPROFILE%\.codex`, macOS/Linux에서는 `~/.codex`에 Codex skill이 설치됩니다.
 

package/README.md

@@ -17,14 +17,14 @@
 <p><sub>A small harness layer for Claude Code and Codex</sub></p>
 
 <p>
-  <a href="https://github.com/dotoricode/tink-harness/releases/tag/v1.10.0"><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.11.0"><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.10.0 - The default harness set is now specialized-only: generic work runs as a base run (no harness), update cleans up retired generic harnesses automatically and reuses your install-time choices, and weave/frog gained health-summary-driven cleanup and draft promotion. See <a href="CHANGELOG.md">CHANGELOG</a> for release history.</p>
+<p><strong>Latest package:</strong> v1.11.0 - One-line dashboard: <code>npx tink-harness dashboard</code> generates the harness health report and opens it in your browser. Also fixes a serious update bug that wiped approval-ledger and signal history, and stops update from resurrecting harnesses you removed via frog. See <a href="CHANGELOG.md">CHANGELOG</a> for release history.</p>
 
 **English** · [한국어](README.ko.md) · [Changelog](CHANGELOG.md)
 
@@ -115,14 +115,14 @@ $tink:cast refactor the auth module     # Codex
 
 ## See your harness health
 
-After a few runs, two read-only helpers turn your records into a local dashboard:
+After a few runs, one command turns your records into a local dashboard and opens it in your browser:
 
 ```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
+npx tink-harness dashboard          # add --no-open to just generate the file
 ```
 
+Under the hood it runs the two read-only helpers (`node .tink/tools/generate-harness-lifecycle-summary.mjs`, then `node .tink/tools/render-harness-health-report.mjs`) and opens `.tink/maintenance/harness-health-report.html`.
+
 ![Tink dashboard demo - clicking a health group, browsing harness cards, and inspecting the 3D map](.github/assets/demo.gif)
 
 <sub>If this matches your workflow, a ⭐ helps others find it.</sub>
@@ -187,7 +187,7 @@ To update an existing standalone install (Claude Code or Codex):
 npx tink-harness@latest update
 ```
 
-Update asks one question - which agent surface to refresh - and handles the rest automatically. Language, install scope, and git policy are reused from the choices you made at install time; if you chose not to commit `.tink`, update never touches your `.gitignore`. Tink-owned files (commands, skills, maintenance, runtime tools) are always brought to the latest version; your customized harnesses, memory, and config are preserved.
+Update asks one question - which agent surface to refresh - and handles the rest automatically. Language, install scope, and git policy are reused from the choices you made at install time; if you chose not to commit `.tink`, update never touches your `.gitignore`. Tink-owned files (commands, skills, runtime tools) are always brought to the latest version; your customized harnesses, memory, config, and all `.tink/maintenance/` history records 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.10.0`
+Current version: `1.11.0`
 
 Tink follows semver from `1.0.0` onward.
 

package/bin/install.js

@@ -1,4 +1,5 @@
 #!/usr/bin/env node
+import { spawnSync } from 'node:child_process';
 import crypto from 'node:crypto';
 import fs from 'node:fs';
 import os from 'node:os';
@@ -125,7 +126,70 @@ 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. 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`);
+  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  tink-harness dashboard [--no-open]\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  dashboard  Generate the harness health report from local .tink records and open it in your browser. Use --no-open to skip opening.\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 findTinkRoot() {
+  for (const dir of [process.cwd(), os.homedir()]) {
+    if (fs.existsSync(path.join(dir, '.tink'))) return dir;
+  }
+  return null;
+}
+
+function openInBrowser(file) {
+  let result;
+  if (process.platform === 'win32') {
+    result = spawnSync('cmd', ['/c', 'start', '', file], { stdio: 'ignore' });
+  } else if (process.platform === 'darwin') {
+    result = spawnSync('open', [file], { stdio: 'ignore' });
+  } else {
+    result = spawnSync('xdg-open', [file], { stdio: 'ignore' });
+  }
+  return !result.error && result.status === 0;
+}
+
+function runDashboard() {
+  const target = findTinkRoot();
+  const language = detectInstalledLanguage() || detectLanguage();
+  if (!target) {
+    console.error(language === 'ko'
+      ? '.tink 디렉토리를 찾을 수 없습니다(현재 디렉토리·홈 디렉토리 확인). 먼저 `npx tink-harness@latest install`을 실행하세요.'
+      : 'No .tink directory found in the current or home directory. Run `npx tink-harness@latest install` first.');
+    process.exit(1);
+  }
+  const toolFor = (name) => {
+    const installed = path.join(target, '.tink/tools', name);
+    return fs.existsSync(installed) ? installed : path.join(root, 'templates/tink/tools', name);
+  };
+  const steps = [
+    toolFor('generate-harness-lifecycle-summary.mjs'),
+    toolFor('render-harness-health-report.mjs')
+  ];
+  for (const tool of steps) {
+    const result = spawnSync(process.execPath, [tool], { cwd: target, stdio: 'inherit' });
+    if (result.status !== 0) {
+      console.error(language === 'ko'
+        ? `대시보드 생성 실패: ${path.basename(tool)}`
+        : `Dashboard step failed: ${path.basename(tool)}`);
+      process.exit(result.status || 1);
+    }
+  }
+  const reportPath = path.join(target, '.tink/maintenance/harness-health-report.html');
+  if (!fs.existsSync(reportPath)) {
+    console.error(language === 'ko'
+      ? `리포트 파일이 없습니다: ${reportPath}`
+      : `Report not found: ${reportPath}`);
+    process.exit(1);
+  }
+  console.log(language === 'ko' ? `대시보드: ${reportPath}` : `Dashboard: ${reportPath}`);
+  if (args.includes('--no-open')) return;
+  if (openInBrowser(reportPath)) {
+    console.log(language === 'ko' ? '기본 브라우저에서 열었습니다.' : 'Opened in your default browser.');
+  } else {
+    console.log(language === 'ko'
+      ? '브라우저 자동 열기에 실패했습니다. 위 경로의 파일을 직접 열어주세요.'
+      : 'Could not open a browser automatically. Open the file above manually.');
+  }
 }
 
 function normalizeSurfaces(surfaces) {
@@ -366,7 +430,8 @@ function handleCancel(value) {
 
 function readHarnessCount() {
   const dir = path.join(root, 'templates/tink/harnesses');
-  return fs.readdirSync(dir).filter((name) => name.endsWith('.md')).length;
+  // HARNESS.md is the human catalog, not a harness
+  return fs.readdirSync(dir).filter((name) => name.endsWith('.md') && name !== 'HARNESS.md').length;
 }
 
 function displayPath(base, filePath) {
@@ -410,10 +475,17 @@ 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/tools/');
 }
 
+function isSeedOnlyPath(src) {
+  // Runtime record files (ledger, friction, weave queue): the template only
+  // seeds them. Once they exist they hold user history and must never be
+  // overwritten by install or update.
+  const rel = path.relative(root, src).replace(/\\/g, '/');
+  return rel.startsWith('templates/tink/maintenance/');
+}
+
 // Generic task-type harnesses retired from the default set: generic work now
 // runs on the base run contract alone. Values are normalized (CR-stripped)
 // sha256 hashes of every version ever shipped, so update can tell shipped
@@ -445,6 +517,42 @@ function normalizedSha256(content) {
   return crypto.createHash('sha256').update(content.replace(/\r/g, '')).digest('hex');
 }
 
+// Default harnesses the user explicitly removed via an approved /tink:frog
+// operation. Update must not resurrect them.
+const retiredByFrog = new Set();
+
+function harnessNameFromDest(dest) {
+  const match = String(dest).replace(/\\/g, '/').match(/\.tink\/harnesses\/([^/]+)\.md$/);
+  return match ? match[1] : '';
+}
+
+function loadFroggedHarnessNames(target) {
+  retiredByFrog.clear();
+  const ledgerPath = path.join(target, '.tink/maintenance/ledger.jsonl');
+  if (!fs.existsSync(ledgerPath)) return;
+  let lines;
+  try {
+    lines = fs.readFileSync(ledgerPath, 'utf8').split('\n');
+  } catch {
+    return;
+  }
+  for (const line of lines) {
+    const text = line.replace(/^/, '').trim();
+    if (!text) continue;
+    try {
+      const entry = JSON.parse(text);
+      if (entry && entry.type === 'frog' && entry.result === 'applied' && Array.isArray(entry.files)) {
+        for (const file of entry.files) {
+          const name = harnessNameFromDest(file);
+          if (name && name !== 'index') retiredByFrog.add(name);
+        }
+      }
+    } catch {
+      // skip malformed ledger lines
+    }
+  }
+}
+
 function removeRetiredHarnesses(templateRoot, target) {
   const harnessDir = path.join(target, '.tink/harnesses');
   if (!fs.existsSync(harnessDir)) return;
@@ -481,7 +589,8 @@ function syncHarnessIndex(templateRoot, target, cleared) {
     // append default entries the installed index does not know yet
     const kept = installed.filter((entry) => !(entry && cleared.includes(entry.name)));
     const knownNames = new Set(kept.map((entry) => entry && entry.name));
-    const added = template.filter((entry) => entry && !knownNames.has(entry.name));
+    const added = template.filter((entry) =>
+      entry && !knownNames.has(entry.name) && !retiredByFrog.has(entry.name));
     const next = [...kept, ...added];
     if (next.length === installed.length && added.length === 0) return;
     log.message(`${dryRun ? 'would sync' : 'sync'} ${displayPath(target, indexPath)} (${installed.length - kept.length} retired removed, ${added.length} default added)`);
@@ -549,6 +658,13 @@ function isGeneratedLegacyRuleGraph(src, dest) {
 
 function writeFileFromTemplate(src, dest, base) {
   const exists = fs.existsSync(dest);
+  if (exists && !force && isSeedOnlyPath(src)) {
+    return;
+  }
+  if (isUpdate && !exists && retiredByFrog.has(harnessNameFromDest(dest))) {
+    log.message(`skip frog-removed ${displayPath(base, dest)}`);
+    return;
+  }
   if (exists && !force) {
     if (isUpdate) {
       const srcContent = fs.readFileSync(src);
@@ -783,6 +899,7 @@ function copySelected(scope, components, agent) {
     }
   }
   if (components.includes('harnesses')) {
+    if (isUpdate) loadFroggedHarnessNames(target);
     copyDir(path.join(templateRoot, 'tink/harnesses'), path.join(target, '.tink/harnesses'), target);
     copyDir(path.join(templateRoot, 'tink/rules'), path.join(target, '.tink/rules'), target);
     copyDir(path.join(templateRoot, 'tink/schemas'), path.join(target, '.tink/schemas'), target);
@@ -1099,6 +1216,11 @@ async function main() {
     process.exit(0);
   }
 
+  if (command === 'dashboard') {
+    runDashboard();
+    return;
+  }
+
   if (command !== 'install' && command !== 'update') {
     console.error(`Unknown command: ${command}`);
     usage();

package/commands/list.md

@@ -11,7 +11,7 @@ List available Tink harnesses without loading every harness body.
 2. Read only compact usage metadata from `.tink/runs/` (frontmatter `selected_harnesses` / `actually_loaded_harnesses` + dates), `.tink/maintenance/ledger.jsonl`, and `.tink/maintenance/weave-queue.json`. Do not load raw logs.
 3. Treat `.tink/current/` as weak evidence unless it is clearly from the same active conversation. If context is uncertain, label it `stale current candidate`, not proof of usage.
 4. Classify every harness into exactly one of three categories:
-   - **working** — directly performs or gates tasks (e.g. `ship`, `pr-merge`, `requirements-interview`, `plan-consensus`, `goal-checkpoint`, `delegation-brief`). Generic work (code change, research, review, docs) runs on the base run without a harness, so it does not appear here.
+   - **working** — directly performs or gates tasks (e.g. `ship`, `requirements-interview`, `plan-consensus`, `goal-checkpoint`, `delegation-brief`). Generic work (code change, research, review, docs) runs on the base run without a harness, so it does not appear here.
    - **meta** — manages other harnesses or Tink itself. Treat these names as meta regardless of `kind`: `harness-synthesis`, `harness-curation`, `tink-feedback-apply`.
    - **custom (this repo)** — `kind: synthesized` in `index.json` (created in this repo, not part of the default set). If a synthesized harness also matches a meta name, prefer meta.
 5. Compute the signal per harness:

package/commands/update.md

@@ -15,7 +15,8 @@ This command does not run the update itself. It detects how Tink was installed i
    - 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.
+   - **Always updated**: `.claude/commands/tink/`, `.claude/skills/tink/`, `.tink/tools/` — template changes always propagate here.
+   - **Never overwritten once they exist**: `.tink/maintenance/` record files (`ledger.jsonl`, `friction.jsonl`, `weave-queue.json`) hold user history; the template only seeds them when missing.
    - **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.
 
@@ -38,7 +39,8 @@ 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.
+- **Always overwrites**: commands, skills, and runtime tools (`.claude/commands/tink/`, `.claude/skills/tink/`, `.tink/tools/`) — so you get the latest harness runner, report tools, and command behavior automatically.
+- **Never overwrites records**: `.tink/maintenance/` ledger, friction, and weave-queue files are user history; they are only seeded when missing.
 - **Preserves if modified**: harnesses, hooks, memory, and config (`.tink/harnesses/`, `.tink/hooks/`, `.tink/memory/`, `.tink/config.json`) — respects your `weave` customizations and local settings.
 - **Reuses stored choices**: language, install scope, and git policy come from `.tink/config.json`. With `git_policy: "none"` (커밋 안 함) the updater never creates or edits `.gitignore`, and an existing whole-directory `.tink/` ignore line is left as-is.
 
@@ -62,7 +64,7 @@ If the source-repo guard triggers, print only this and stop — do not present p
 
 **설치 경로**: <plugin marketplace | npx standalone>
 
-**항상 업데이트됨**: commands, skills, maintenance, tools (최신 버전으로 자동 반영)
+**항상 업데이트됨**: commands, skills, tools (최신 버전으로 자동 반영) · maintenance 기록 파일은 보존
 
 **사용자 수정 파일** (업데이트 시 보존):
 - <path1>

package/package.json

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

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

@@ -11,7 +11,7 @@ List available Tink harnesses without loading every harness body.
 2. Read only compact usage metadata from `.tink/runs/` (frontmatter `selected_harnesses` / `actually_loaded_harnesses` + dates), `.tink/maintenance/ledger.jsonl`, and `.tink/maintenance/weave-queue.json`. Do not load raw logs.
 3. Treat `.tink/current/` as weak evidence unless it is clearly from the same active conversation. If context is uncertain, label it `stale current candidate`, not proof of usage.
 4. Classify every harness into exactly one of three categories:
-   - **working** — directly performs or gates tasks (e.g. `ship`, `pr-merge`, `requirements-interview`, `plan-consensus`, `goal-checkpoint`, `delegation-brief`). Generic work (code change, research, review, docs) runs on the base run without a harness, so it does not appear here.
+   - **working** — directly performs or gates tasks (e.g. `ship`, `requirements-interview`, `plan-consensus`, `goal-checkpoint`, `delegation-brief`). Generic work (code change, research, review, docs) runs on the base run without a harness, so it does not appear here.
    - **meta** — manages other harnesses or Tink itself. Treat these names as meta regardless of `kind`: `harness-synthesis`, `harness-curation`, `tink-feedback-apply`.
    - **custom (this repo)** — `kind: synthesized` in `index.json` (created in this repo, not part of the default set). If a synthesized harness also matches a meta name, prefer meta.
 5. Compute the signal per harness:

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

@@ -15,7 +15,8 @@ This command does not run the update itself. It detects how Tink was installed i
    - 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.
+   - **Always updated**: `.claude/commands/tink/`, `.claude/skills/tink/`, `.tink/tools/` — template changes always propagate here.
+   - **Never overwritten once they exist**: `.tink/maintenance/` record files (`ledger.jsonl`, `friction.jsonl`, `weave-queue.json`) hold user history; the template only seeds them when missing.
    - **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.
 
@@ -38,7 +39,8 @@ 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.
+- **Always overwrites**: commands, skills, and runtime tools (`.claude/commands/tink/`, `.claude/skills/tink/`, `.tink/tools/`) — so you get the latest harness runner, report tools, and command behavior automatically.
+- **Never overwrites records**: `.tink/maintenance/` ledger, friction, and weave-queue files are user history; they are only seeded when missing.
 - **Preserves if modified**: harnesses, hooks, memory, and config (`.tink/harnesses/`, `.tink/hooks/`, `.tink/memory/`, `.tink/config.json`) — respects your `weave` customizations and local settings.
 - **Reuses stored choices**: language, install scope, and git policy come from `.tink/config.json`. With `git_policy: "none"` (커밋 안 함) the updater never creates or edits `.gitignore`, and an existing whole-directory `.tink/` ignore line is left as-is.
 
@@ -62,7 +64,7 @@ If the source-repo guard triggers, print only this and stop — do not present p
 
 **설치 경로**: <plugin marketplace | npx standalone>
 
-**항상 업데이트됨**: commands, skills, maintenance, tools (최신 버전으로 자동 반영)
+**항상 업데이트됨**: commands, skills, tools (최신 버전으로 자동 반영) · maintenance 기록 파일은 보존
 
 **사용자 수정 파일** (업데이트 시 보존):
 - <path1>