tink-harness 1.9.20 → 1.9.21

package/.claude-plugin/plugin.json

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

package/CHANGELOG.md

@@ -6,6 +6,12 @@ All notable changes to Tink are tracked here.
 
 No unreleased changes yet.
 
+## [1.9.21] - 2026-06-11
+
+### Changed
+
+- README repositioned problem-first (EN/KO): the hero now leads with "Stop losing context between Claude Code and Codex runs", followed by Who-this-is-for, a concrete tour of the files Tink leaves behind, and a "Why not just CLAUDE.md / slash commands / skills / MCP?" comparison table. The knitting metaphor moved into the origin-story section, and a small star call-to-action sits under the demo GIF. Added a release-pacing note to VERSIONING.md.
+
 ## [1.9.20] - 2026-06-11
 
 ### Changed

package/README.ko.md

@@ -4,16 +4,61 @@
 
 # Tink
 
-Claude Code와 Codex를 위한 작은 하네스 레이어입니다.
+**Claude Code · Codex 작업의 맥락이 더는 사라지지 않게.**
 
-Tink는 지금 작업에 맞는 하네스를 고르고, 실행 상태를 보이게 만들고, 실제 사용 중 생긴 실패와 피드백으로 하네스 세트를 개선합니다.
+Tink는 사소하지 않은 모든 에이전트 작업을 눈에 보이는 파일로 남깁니다 — 작업 계약, 실행 상태, 검증 단계, 그리고 승인해야만 저장되는 재사용 하네스. 서버도, 텔레메트리도, 숨은 상태도 없습니다.
 
-**최신 패키지:** v1.9.20 — 로컬 건강 리포트가 탭형 대시보드로 바뀌었습니다. 3D 하네스 지도, 쉬운 말 건강 요약, Claude Code와 Codex 양쪽 복사-붙여넣기 명령이 포함된 다음 행동 제안을 제공합니다. 전체 변경 이력은 [CHANGELOG](CHANGELOG.md)를 확인하세요.
+<sub>Claude Code와 Codex를 위한 작은 하네스 레이어</sub>
+
+**최신 패키지:** v1.9.21 — 로컬 건강 리포트가 탭형 대시보드로 바뀌었습니다. 3D 하네스 지도, 쉬운 말 건강 요약, Claude Code와 Codex 양쪽 복사-붙여넣기 명령이 포함된 다음 행동 제안을 제공합니다. 전체 변경 이력은 [CHANGELOG](CHANGELOG.md)를 확인하세요.
 
 [English](README.md) · **한국어** · [변경 이력](CHANGELOG.md)
 
 ---
 
+## 누구를 위한 도구인가
+
+이런 순간에 쓰세요:
+
+- Claude Code나 Codex가 작업 사이에 맥락을 자꾸 잃을 때
+- 같은 리뷰 / 리팩터링 / 디버깅 절차를 매번 손으로 반복할 때
+- 숨은 채팅 기억 대신 눈에 보이는 실행 상태를 원할 때
+- 재사용 가능한 에이전트 워크플로를 원하지만, 명시적 승인 후에만 저장되길 원할 때
+
+내 얘기 같다면, 버려도 되는 repo에서 먼저 시도해 보세요:
+
+```bash
+npx tink-harness@latest install
+```
+
+## 실제로 남는 것
+
+사소하지 않은 작업마다 열어보고, diff하고, 커밋할 수 있는 평범한 파일이 남습니다:
+
+```text
+.tink/current/                      # 진행 중인 실행 — 언제든 열람 가능
+  contract.json                     #   작업이 끝났을 때 참이어야 하는 것
+  plan.md                           #   눈에 보이는 계획
+  checks.md                         #   "완료" 선언 전 돌릴 검증
+.tink/runs/
+  2026-06-11-1430-auth-refactor.md  # 끝난 실행의 간결한 기록
+.tink/harnesses/
+  refactor-review.md                # 재사용 작업 방식 — 승인해야 저장
+```
+
+## CLAUDE.md·슬래시 명령·스킬만으로는 왜 부족할까?
+
+| 도구 | 제공하는 것 | Tink가 얹는 것 |
+|---|---|---|
+| CLAUDE.md | 프로젝트 전역 지침 | 작업 단위 계약·실행 상태·검증 |
+| 슬래시 명령 | 재사용 프롬프트 | 하네스 선택, 실행 기록, 진행도 추적 |
+| 스킬 | 재사용 능력 | 사용 생애주기: 건강 점수·정리·개선 신호 |
+| MCP | 외부 컨텍스트·도구 | 로컬, 승인 게이트 워크플로 메모리 |
+
+Tink는 이들을 대체하지 않고 함께 동작합니다.
+
+---
+
 ## 빠른 시작
 
 1분이면 Tink를 직접 써볼 수 있습니다.
@@ -66,6 +111,8 @@ node .tink/tools/render-harness-health-report.mjs
 
 ![Tink 대시보드 데모 — 건강 그룹 클릭, 하네스 카드 탐색, 3D 지도 조작](.github/assets/demo.gif)
 
+<sub>당신의 워크플로와 맞는다면, ⭐ 하나가 다른 개발자들이 찾는 데 도움이 됩니다.</sub>
+
 하네스와 그들이 쓰는 규칙·메모리, 그 연결을 보여주는 인터랙티브 3D 지도 — 무리마다 고유한 색을 갖고, 살아있는 관계 위로 신호가 흐릅니다:
 
 ![Tink 하네스 지도 — 하네스·규칙·메모리·단계를 보여주는 인터랙티브 3D 뷰](.github/assets/dashboard-map.ko.png)

package/README.md

@@ -6,30 +6,73 @@
   <strong>Tink</strong>
 </h1>
 
-<p>A small harness layer for Claude Code and Codex</p>
+<p><strong>Stop losing context between Claude Code and Codex runs.</strong></p>
 
 <p>
-  Tink helps Claude Code or Codex choose the right harness, keep run state visible, and improve the harness set as you work.
+  Tink keeps every non-trivial agent task in visible files - a task contract, run state,
+  verification steps, and reusable harnesses that are saved only after your approval.
+  No server, no telemetry, no hidden state.
 </p>
 
-<p>
-  <em>Tink is <strong>knit</strong> in reverse: untying tangled workflows and knitting better ones back together. It also nods to Tinker Bell, the small helper at your side.</em>
-</p>
+<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.9.20"><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.21"><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.20 - 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.21 - 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)
 
 ---
 
+## Who this is for
+
+Use Tink when:
+
+- Claude Code or Codex keeps losing task context between runs
+- you repeat the same review / refactor / debug workflow by hand
+- you want visible run state instead of hidden chat memory
+- you want reusable agent workflows - saved only after explicit approval
+
+If that sounds like your day, try it on a throwaway repo first:
+
+```bash
+npx tink-harness@latest install
+```
+
+## What you actually get
+
+Every non-trivial task leaves plain files you can open, diff, and commit:
+
+```text
+.tink/current/                      # the active run - always inspectable
+  contract.json                     #   what must be true when the task is done
+  plan.md                           #   the visible plan
+  checks.md                         #   verification to run before claiming "done"
+.tink/runs/
+  2026-06-11-1430-auth-refactor.md  # compact record of each finished run
+.tink/harnesses/
+  refactor-review.md                # reusable ways of working - approval-gated
+```
+
+## Why not just CLAUDE.md / slash commands / skills?
+
+| Tooling | What it gives you | What Tink adds on top |
+|---|---|---|
+| CLAUDE.md | project-wide instructions | per-task contracts, run state, and verification |
+| Slash commands | reusable prompts | harness selection, run records, progress tracking |
+| Skills | reusable capability | usage lifecycle: health scores, cleanup and improvement signals |
+| MCP | external context and tools | local, approval-gated workflow memory |
+
+Tink composes with all of these - it does not replace them.
+
+---
+
 ## Install & quick start
 
 Try Tink in about a minute.
@@ -82,6 +125,8 @@ node .tink/tools/render-harness-health-report.mjs
 
 ![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>
+
 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)
@@ -96,6 +141,8 @@ No server, no telemetry, no hidden cache - it is a static local page that only p
 
 ## Why I made this
 
+*Tink is <strong>knit</strong> in reverse: untying tangled workflows and knitting better ones back together. It also nods to Tinker Bell, the small helper at your side.*
+
 New coding harnesses show up almost every day. Many of them are genuinely useful.
 
 At first, I tried them one by one and kept the ones that fit me. But the more I mixed them, the more my environment got tangled. Resetting everything again and again was tiring, so I ended up falling back to a skill-based workflow that I could understand and control.

package/VERSIONING.md

@@ -1,6 +1,6 @@
 # Versioning
 
-Current version: `1.9.20`
+Current version: `1.9.21`
 
 Tink follows semver from `1.0.0` onward.
 
@@ -86,3 +86,7 @@ npx tink-harness@latest update
 ```
 
 `update` preserves user-modified files. The `--force` flag is reserved for emergency repair and is not the recommended path.
+
+## Release pacing
+
+Batch small fixes on `main` and aim for at most about one release per day. Rapid version churn reads as instability to first-time visitors; a release should bundle a coherent set of changes with a short, plain note.

package/package.json

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