patina-cli 3.11.0 → 4.0.0

package/docs/research/lexicon-freshness-audit.md

@@ -0,0 +1,64 @@
+# Lexicon freshness audit
+
+Status: English remine complete; multilingual provenance sidecars complete with honest legacy/null fields.
+Related issue: #160.
+
+Patina lexicons are detection hypotheses. They should not be described as fresh model-era evidence unless each entry has a corpus source and a false-positive check.
+
+## Current frontmatter status
+
+| file | entries | current snapshot status | provenance | action |
+|---|---:|---|---|---|
+| `lexicon/ai-en.md` | 88 | `current` | `lexicon/provenance/ai-en.json` | keep; recheck at the next quarterly HAP-E or 2025+ paired refresh |
+| `lexicon/ai-ko.md` | 96 | `partial` | `lexicon/provenance/ai-ko.json` | keep; rerun against 2026 KO positive + human-control pairs before threshold changes |
+| `lexicon/ai-zh.md` | 60 | `needs-external-calibration` | `lexicon/provenance/ai-zh.json` | calibrate before broad claims |
+| `lexicon/ai-ja.md` | 60 | `needs-external-calibration` | `lexicon/provenance/ai-ja.json` | calibrate before broad claims |
+
+English was re-mined on 2026-05-22 against the HAP-E English paired corpus:
+8,290 GPT-4o continuations versus 8,290 paired human `chunk_2` controls across
+academic, blog, fiction, news, spoken, and TV/movie registers. Raw corpus text
+stays in `artifacts/rebaseline-2025/private/`; only the aggregate report is
+tracked.
+
+Evidence:
+
+- aggregate report: `docs/benchmarks/lexicon-freshness-en-2026-05-22.md`
+- aggregate JSON: `docs/benchmarks/lexicon-freshness-en-2026-05-22.json`
+- validation command: `npm run lexicon:freshness`
+
+## English remine result
+
+| decision | entries | rule |
+|---|---:|---|
+| kept | 88 | ≥4× hot-vs-cold document-frequency lift, at least one hot hit, cold document-frequency ≤5% |
+| dropped | 20 | below the lift floor or zero hot hits |
+
+Dropped English entries:
+
+- strict: `state-of-the-art`, `enable`, `workflow`, `framework`, `dimensions`, `unleash`, `elevated`
+- phrases: `a wide range of`, `a host of`, `in the age of`, `gain a deeper understanding`, `key drivers`, `driving force`, `play a key role`, `close the gap`, `end-to-end`, `to ensure that`, `it is essential to`, `under the hood`, `on the other hand`
+
+## Per-entry remine gate
+
+A refreshed entry needs:
+
+```yaml
+added: YYYY-MM-DD or null when the legacy add date is unknown
+source: <snapshot id or corpus manifest path>
+last_validated: YYYY-MM-DD or null when not yet externally validated
+lift: <hot/cold document-frequency ratio or null>
+```
+
+Promotion floor from `process/pattern-freshness.md`:
+
+- ≥4× hot-vs-cold document-frequency lift;
+- cold document-frequency ≤5%, unless the entry is register-scoped;
+- no severe false positives in matched controls;
+- no private text checked into the repo.
+
+## Next action
+
+Do not re-add dropped English entries without a newer paired-corpus lift report.
+For KO/ZH/JA, the sidecar fields exist but some `added`, `last_validated`, or
+`lift` values remain `null` instead of invented. Treat those languages as
+partial or calibration-pending until their own paired hot/cold reports land.

package/docs/research/zh-ja-lexicon-calibration.md

@@ -0,0 +1,60 @@
+# zh/ja AI-Lexicon Calibration Notes
+
+This note documents the first checked-in zh/ja AI-lexicon pass for issue #104.
+The goal is high precision: the lexicon should add signal when AI-style
+scaffolding is dense, without turning ordinary Chinese or Japanese prose hot on
+one phrase.
+
+## Shipped packs
+
+| file | entries | shape | matching note |
+|---|---:|---|---|
+| `lexicon/ai-zh.md` | 60 | phrase-only | substring + `~` wildcard |
+| `lexicon/ai-ja.md` | 60 | phrase-only | substring + `~` wildcard |
+
+Both packs avoid strict entries by default because zh/ja tokenization uses the
+character fallback. Custom strict entries still work through the CJK substring
+fallback added in `src/features/lexicon.js`.
+
+## Regression corpus
+
+The committed regression corpus now has 39 fixtures overall. The zh/ja slice in
+this note remains:
+
+| language | AI | natural | expected FP |
+|---|---:|---:|---:|
+| zh | 4 | 4 | 0 |
+| ja | 4 | 4 | 0 |
+
+The new lexicon-specific fixtures are:
+
+- `tests/fixtures/suspect-zones/zh/ai/zh-ai-04-lexicon.md`
+- `tests/fixtures/suspect-zones/zh/natural/zh-nat-04-lexicon-cold.md`
+- `tests/fixtures/suspect-zones/ja/ai/ja-ai-04-lexicon.md`
+- `tests/fixtures/suspect-zones/ja/natural/ja-nat-04-lexicon-cold.md`
+
+`npm run benchmark` reports 100% fixture accuracy with zh/ja precision and
+recall at 4/4 each. The lexicon-specific AI fixtures are lexicon-only hot: their
+burstiness and MATTR detectors stay cold while lexicon density crosses the
+threshold.
+
+## Expansion rule
+
+Before adding more entries, test candidates against at least these classes:
+
+1. AI/guidance prose that uses broad summary scaffolds.
+2. Wikipedia/news-style human prose.
+3. Personal narrative or sensory prose.
+4. Domain-heavy technical prose where repeated nouns are normal.
+
+Drop any candidate that appears at similar frequency in class 2 or 4. A phrase
+that is common in human explanatory writing should move to the pattern catalog
+only if it has a rewrite strategy; otherwise it should stay out of the lexicon.
+
+## Remaining calibration risk
+
+The committed fixture set is a regression gate, not a full 200-paragraph external
+corpus. The original #104 acceptance target called for HC3 zh and curated ja
+AI-vs-human calibration. This PR adds the lexicon packs and local gates so the
+feature can be exercised safely, but future expansion should still run the larger
+external corpus before raising entry counts or lowering the density threshold.

package/docs/social/patina-launch-copy.md

@@ -1,10 +1,56 @@
-# patina Launch Copy
+# patina Launch Copy and Playbook
 
-Use this file as the source of truth for public launch posts. The positioning is deliberately "auditable cleanup / editing tool", not detector bypass.
+Use this file as the source of truth for public launch posts. The positioning is deliberately **auditable cleanup / editing tool**, not detector bypass.
 
-## Positioning
+Execution checklist:
+[`docs/social/patina-launch-execution.md`](patina-launch-execution.md).
+
+## Launch sequence
+
+Run the launch in this order. Do not skip the Korean-first pass: it is the wedge that makes patina different from generic English humanizers.
+
+| Order | Surface | Primary angle | Launch state |
+|---:|---|---|---|
+| 1 | Korean communities: GeekNews, Velog, Clien | Korean AI tells plus auditable edits | Ready after final score pass |
+| 2 | Show HN | Local, auditable, benchmarked prose cleanup | Ready after final score pass |
+| 3 | Product Hunt | Visual demo plus “keep the meaning” | Ready after final score pass |
+| 4 | Reddit / X / Threads / LinkedIn | Local/no-key angle or editing/voice angle | Reuse the channel drafts below |
+
+## Prerequisite checklist
+
+| Item | Status | Launch impact |
+|---|---|---|
+| npm package live (#203) | Done | Use `npx patina-cli` in posts. |
+| GitHub Action v1 (#204) | Done | Mention PR comments and README score badge. |
+| README score badge (#282) | Done | Use as adoption/social proof. |
+| Ethics framing (#164, [`docs/ETHICS.md`](../ETHICS.md)) | Done | Never imply detector evasion. |
+| Comparison page (#213, [`docs/COMPARISON.md`](../COMPARISON.md)) | Done | Cite only factual comparisons. |
+| Web playground (#208) | Ready | Use <https://patina.vibetip.help/> as the try-it-now URL. |
+| Shareable card generator (#283) | Helpful | Product Hunt and X work better with it. |
+| “Signs of AI writing” guide (#285) | Helpful | Use as top-of-funnel content. |
+
+## Non-negotiable rules
+
+- Score every final post before publishing. Target `<= 30`.
+- Attach the score screenshot or CLI output to the internal launch thread.
+- Lead with the writing problem. Mention the tool after the reader recognizes the problem.
+- Do not use “bypass,” “undetectable,” or “beats detectors.”
+- Avoid hype vocabulary, emoji-bullet stacks, and tidy three-item slogans.
+- Link the playground from every broad-launch post: <https://patina.vibetip.help/>. Keep the repo link nearby for source, install, and issues.
 
-patina detects recurring AI-writing patterns, rewrites the affected passages, and checks whether the original claims were preserved.
+Score command:
+
+```bash
+node scripts/precommit-score.mjs docs/social/patina-launch-copy.md
+```
+
+Last local score check: 2026-05-23, `docs/social/patina-launch-copy.md` scored 6.3% (`node scripts/precommit-score.mjs docs/social/patina-launch-copy.md`).
+
+Korean-first launch drafts are now split out for exact channel copying:
+[`docs/social/patina-launch-korean-first.md`](patina-launch-korean-first.md).
+Last score check on 2026-05-23: Korean-first drafts 0.0%, this file 6.3%.
+
+## Positioning
 
 Short tagline:
 
@@ -14,38 +60,54 @@ Long tagline:
 
 > A pattern-based cleanup tool for AI-sounding text. It shows what changed, why it changed, and whether the original claims survived.
 
-## Before posting
+One-sentence description:
+
+> patina finds recurring AI-writing habits in Korean, English, Chinese, and Japanese, rewrites the affected passages, and keeps the edit auditable.
 
-- Run `npm run benchmark:report && npm test`.
-- Check the current benchmark: [`docs/benchmarks/latest.md`](../benchmarks/latest.md).
-- If comparing tools, link the factual comparison page: [`docs/COMPARISON.md`](../COMPARISON.md).
-- Use the launch social preview when the surface supports images: [`assets/social/patina-og.svg`](../../assets/social/patina-og.svg).
-- Keep claims to "editing signal" and "suspect-zone benchmark"; do not imply authorship proof.
-- Link issues for useful feedback: false positives, missing patterns, benchmark fixtures.
+## Assets to attach
 
-## Avoid
+- Social preview: [`assets/social/patina-og.svg`](../../assets/social/patina-og.svg)
+- Before/after card: [`assets/social/patina-before-after.svg`](../../assets/social/patina-before-after.svg)
+- Static badge fallback: [`assets/brand/patina-badge.svg`](../../assets/brand/patina-badge.svg)
+- Benchmark report: [`docs/benchmarks/latest.md`](../benchmarks/latest.md)
+- Comparison page: [`docs/COMPARISON.md`](../COMPARISON.md)
 
-Do not frame patina as:
+## Korean communities
 
-- an AI detector bypass tool
-- a way to fake authorship
-- proof that text is human-written
-- a universal paraphraser
+Title options:
 
-Use these instead:
+```text
+patina — 한국어·영어 AI 글의 “AI 티”를 찾아서 지워주는 오픈소스
+AI가 쓴 티 나는 문장, 패턴으로 잡아서 고쳐주는 도구를 만들었습니다
+```
+
+Post body:
+
+```text
+GPT한테 글을 맡기면 어딘가 티가 납니다. “~적인”, “~하고 있다”, 갑자기 늘어나는 한자어, 너무 반듯한 목록 같은 것들요.
+
+patina는 그런 패턴을 찾아서 고칩니다. 한국어, 영어, 중국어, 일본어를 지원하고, Claude Code / Codex / Cursor / OpenCode 스킬이나 Node CLI로 쓸 수 있습니다.
+
+핵심은 AI detector 우회가 아니라 편집입니다. 어떤 표현을 잡았는지, 왜 바꿨는지, 원래 주장과 의미가 보존됐는지를 audit / diff / score로 확인할 수 있게 만들었습니다.
 
-- auditable editing
-- pattern-based cleanup
-- meaning preservation
-- false-positive-aware scoring
-- diff/audit/score modes
+API 키 없이도 쓸 수 있습니다. codex, claude, gemini CLI 중 하나에 로그인돼 있으면 됩니다.
+
+웹에서 먼저:
+https://patina.vibetip.help/
+
+레포:
+https://github.com/devswha/patina
+
+특히 한국어 오탐 사례가 궁금합니다. 사람이 쓴 글인데 patina가 AI 티로 잡는 문장이 있으면 이 글 댓글로 편하게 붙여주셔도 됩니다.
+웹에서 바로 신고: 플레이그라운드(https://patina.vibetip.help/)에서 '오탐 신고' 버튼을 누르면 걸린 문장이 자동으로 채워진 GitHub 폼이 열립니다.
+```
 
 ## Show HN
 
 Title:
 
 ```text
-Show HN: patina – Strip the AI packaging, keep the meaning
+Show HN: Patina – rewrite AI text patterns in Korean/English/Chinese/Japanese
 ```
 
 Post body:
@@ -53,141 +115,144 @@ Post body:
 ```text
 Hi HN,
 
-I built patina, a pattern-based cleanup tool for AI-sounding text.
+I built Patina because I kept editing the same LLM tells out of drafts: inflated adjectives, neat three-part lists, hedging on hedging, and in Korean, suffixes like “~적”, progressive “~고 있다”, and needless Sino-Korean phrasing.
 
-It detects recurring LLM writing habits, rewrites the affected passages, and checks whether the original claims were preserved. It supports Korean, English, Chinese, and Japanese, and runs as a skill for Claude Code, Codex CLI, Cursor, and OpenCode, or as a standalone Node.js CLI.
+Patina turns those habits into a pattern catalog for Korean, English, Chinese, and Japanese. It can rewrite the affected passages, but it is not a black-box paraphraser. It shows what changed, why it changed, and whether claims, numbers, polarity, causation, and negation survived the edit.
 
-The main difference from a generic paraphraser is auditability: patina can show what pattern it found, what it changed, and whether semantic anchors such as claims, polarity, causation, numbers, and negation survived the rewrite.
+It runs as a skill in Claude Code, Codex CLI, Cursor, and OpenCode, or as a standalone Node CLI:
 
-Example:
+npx patina-cli --lang en draft.md
 
-Before:
-"Coffee has emerged as a pivotal cultural phenomenon that has fundamentally transformed social interactions across the globe. This beloved beverage serves as a catalyst for community building, fosters meaningful connections, and facilitates cross-cultural dialogue."
+If you are already logged into codex, claude, or gemini CLI, you can use it without adding an API key.
 
-After:
-"Coffee has quietly changed how people meet. Sit across from someone long enough, and something like a real connection tends to form — even between people from very different cultures."
+This is not meant as a detector-bypass tool. I treat the score as an editing signal, not proof of authorship. False positives are documented because the useful output is the audit and diff, not a verdict.
 
-This is not meant as an AI-detector bypass tool. Detectors are noisy. I treat the score as an editing signal, and the diff/audit output as the useful artifact.
+Try:
+https://patina.vibetip.help/
 
 Repo:
 https://github.com/devswha/patina
 
-I would especially like feedback on false positives, missing pattern families, and whether the MPS / diff / audit modes are useful for real writing workflows.
+The feedback I want most: human text that Patina wrongly flags, missing pattern families, and examples where the rewrite preserved the wrong thing.
 ```
 
-## Reddit / ClaudeAI Megathread
+## Product Hunt
+
+Tagline:
 
 ```text
-I built patina, a Claude Code skill / CLI for cleaning up AI-sounding text.
+Strip the AI packaging. Keep the meaning.
+```
 
-It detects recurring AI writing patterns, rewrites them, and checks that the original meaning is preserved. It supports Korean, English, Chinese, and Japanese, and also works with Codex CLI, Cursor, OpenCode, and standalone Node.js.
+Description:
 
-Quick before/after:
+```text
+Patina finds the habits that make text read as AI-written — in Korean, English, Chinese, and Japanese — and rewrites them out. It is not a black-box paraphraser: it shows what changed, why it changed, and whether your claims survived. Use it in Claude Code, Codex, Cursor, OpenCode, or as a Node CLI.
+```
 
-Before:
-“Coffee has emerged as a pivotal cultural phenomenon that has fundamentally transformed social interactions across the globe. This beloved beverage serves as a catalyst for community building, fosters meaningful connections, and facilitates cross-cultural dialogue.”
+Maker comment:
 
-After:
-“Coffee has quietly changed how people meet. Sit across from someone long enough, and something like a real connection tends to form, even between people from very different cultures.”
+```text
+I built Patina because I was tired of removing the same AI tells from drafts by hand. Two details matter to me: it works on Korean, where most English-first humanizers miss the obvious tells, and it is auditable. Every edit should have a reason and a meaning-preservation check.
 
-Repo:
-https://github.com/devswha/patina
+I do not want this framed as “make text undetectable.” Detectors are noisy. Patina is an editing pass: find the synthetic packaging, remove it, and keep the claim intact.
 
-I’d especially like feedback on false positives, missing AI-writing patterns, and whether the audit/score/diff modes make sense for real Claude output.
+Try it on something you wrote at https://patina.vibetip.help/ and tell me where it is wrong. False positives are the most useful reports.
 ```
 
-## X launch thread
+## Reddit
 
-### 1
+### r/LocalLLaMA
 
 ```text
-I built patina: a pattern-based cleanup tool for AI-sounding text.
+I built Patina, a local-friendly tool for cleaning up AI-sounding prose.
+
+It runs through the CLI you already use. If you are logged into codex, claude, or gemini, you can run Patina without adding a separate API key. It also works as a Claude Code / Codex / Cursor / OpenCode skill.
+
+The tool finds recurring LLM writing habits, rewrites the affected text, and checks whether the original claims survived. It supports Korean, English, Chinese, and Japanese.
 
-It strips the AI packaging while keeping the meaning.
+This is not an “undetectable text” project. The score is an editing signal. The useful artifact is the audit: what pattern fired, what changed, and whether meaning drifted.
 
-Claude Code / Codex CLI / Cursor / OpenCode / Node CLI
-KO / EN / ZH / JA
+Try:
+https://patina.vibetip.help/
 
+Repo:
 https://github.com/devswha/patina
+
+I am looking for false positives and missing pattern families, especially outside English.
 ```
 
-### 2
+### r/writing or r/Korean
 
 ```text
-The goal is not detector bypass.
+I built a tool that spots and rewrites AI-sounding patterns in writing, including Korean.
 
-AI detectors are noisy. patina treats the score as an editing signal, not proof of authorship.
+The goal is not to hide authorship. It is to make AI-assisted drafts easier to edit. Patina points out habits like inflated phrasing, tidy generic structure, and Korean AI tells such as “~적인”, “~하고 있다”, and needless formal nouns.
 
-The useful parts are audit, diff, and meaning-preservation checks: what changed, why it changed, and whether the original claims survived.
-```
+It then rewrites the affected passages and checks that the original meaning survived. You can see the audit and diff instead of trusting a black-box paraphrase.
 
-### 3
+Try:
+https://patina.vibetip.help/
 
-```text
-Example before:
-
-“Coffee has emerged as a pivotal cultural phenomenon that has fundamentally transformed social interactions across the globe...”
+Repo:
+https://github.com/devswha/patina
 
-This is the kind of AI packaging patina looks for: inflated stakes, vague abstraction, and generic benefit stacking.
+If you have human-written text that gets flagged, I would love to see it. Those examples are the best way to reduce false positives.
 ```
 
-### 4
+## X / Threads
 
-```text
-After:
+### Korean thread
 
-“Coffee has quietly changed how people meet. Sit across from someone long enough, and something like a real connection tends to form — even between people from very different cultures.”
+```text
+1/ AI가 쓴 글은 티가 납니다. “~적인”, 너무 반듯한 목록, 갑자기 늘어나는 한자어 같은 것들요.
 
-Same claims. Less model voice.
+patina는 그런 패턴을 찾아서 고칩니다. KO / EN / ZH / JA.
 ```
 
-### 5
-
 ```text
-Under the hood, patina tracks semantic anchors: claims, polarity, causation, numbers, and negation.
-
-If a rewrite drops or flips an anchor, it retries or rolls back the change.
+2/ 그냥 다시 써주는 도구는 많습니다.
 
-That is the part I care about most: editable output with a safety rail.
+patina는 뭘 왜 바꿨는지, 원래 의미가 보존됐는지까지 보여주는 편집 도구에 가깝습니다.
 ```
 
-### 6
+```text
+3/ API 키 없이도 쓸 수 있습니다.
+
+codex / claude / gemini CLI 중 하나만 로그인돼 있으면 Node CLI나 에디터 스킬로 바로 돌릴 수 있습니다.
+```
 
 ```text
-Current calibration:
+4/ 목표는 detector 우회가 아닙니다.
 
-- 146 pattern catalog
-- 91% Korean editing-hotspot recall [84.0-95.4%], n=100
-- 76% English HC3 editing-hotspot recall [66.7-83.3%], n=100
-- 13-25% human-prose false-positive point-estimate range across registers
-- Latest fixture benchmark: https://github.com/devswha/patina/blob/main/docs/benchmarks/latest.md
+점수는 편집 신호일 뿐이고, 중요한 건 audit / diff / meaning check입니다.
 
-False positives are documented because this should be used as an editor, not a judge.
+https://github.com/devswha/patina
 ```
 
-### 7
+### English single post
 
 ```text
-If you write with LLMs and hate the default polished-but-empty voice, try it and tell me where it fails.
+I built Patina: an AI-writing cleanup tool that works on Korean, shows its edits, and checks whether the meaning survived.
 
-I’m especially looking for missing patterns, false positives, and better before/after examples.
+Not detector bypass. Just auditable editing for text that sounds too packaged.
 
+Claude Code / Codex / Cursor / OpenCode / Node CLI.
 https://github.com/devswha/patina
 ```
 
-## Short Korean community post
+## LinkedIn
 
 ```text
-patina라는 오픈소스 도구를 만들고 있습니다.
+Every team ships AI-assisted writing now: docs, release notes, support replies, launch posts. The problem is not that the writing is AI-assisted. The problem is that it often reads like it.
 
-AI가 쓴 글에서 자주 보이는 표현 패턴을 잡아서, 의미는 유지한 채 더 자연스럽게 고치는 도구입니다. Claude Code 스킬로 쓸 수 있고, Codex CLI / Cursor / OpenCode / Node CLI에서도 동작합니다. 한국어, 영어, 중국어, 일본어 패턴을 지원합니다.
+I built Patina for the editing pass after generation. It finds the habits that make prose feel machine-written, rewrites the affected passages, and checks whether the original claims survived.
 
-핵심은 “AI detector 우회”가 아니라 편집입니다. 어떤 패턴을 잡았는지, 왜 바꿨는지, 원래 주장과 의미가 보존됐는지를 audit / diff / score 모드로 확인할 수 있게 만드는 쪽에 집중했습니다.
+The important part for work is auditability. You can see what changed and why instead of trusting a black-box paraphrase.
 
-레포:
-https://github.com/devswha/patina
+It supports Korean, English, Chinese, and Japanese, and runs as an editor skill or Node CLI.
 
-특히 한국어 false positive, 빠진 AI 문체 패턴, before/after 예시 피드백을 받고 싶습니다.
+https://github.com/devswha/patina
 ```
 
 ## Maintainer reply templates
@@ -195,33 +260,41 @@ https://github.com/devswha/patina
 ### Detector-bypass concern
 
 ```text
-Fair concern. I do not think of patina as a detector-bypass tool. AI detectors are noisy anyway.
+Fair concern. I do not think of Patina as a detector-bypass tool. AI detectors are noisy anyway.
 
-The goal is editing: find repeated writing habits that make LLM output feel synthetic, rewrite those parts, and keep the meaning checkable through audit/diff/score modes.
+The goal is editing: find repeated writing habits that make LLM output feel synthetic, rewrite those parts, and keep the meaning checkable through audit, diff, and score modes.
 ```
 
 ### False positives
 
 ```text
-False positives are real. Human prose can trigger patina, especially encyclopedic, corporate, academic, or heavily edited writing.
+False positives are real. Human prose can trigger Patina, especially encyclopedic, corporate, academic, or heavily edited writing.
 
-That is why I treat the score as a rough editing signal, not a truth machine. The diff and the highlighted patterns matter more than the exact number.
+That is why I treat the score as a rough editing signal, not a truth machine. The diff and highlighted patterns matter more than the exact number.
 ```
 
 ### Install help
 
 ```text
-Install:
+Install (standalone CLI, nothing to trust beyond npm):
 
-curl -fsSL https://raw.githubusercontent.com/devswha/patina/main/install.sh | bash
+npx patina-cli --lang en input.txt
 
-Then in Claude Code:
+Or inside Claude Code:
 
 /patina --lang en
 
 [paste text]
 
-Or as a standalone CLI:
+Prefer a one-line installer? Review the script first, then:
 
-patina --lang en input.txt
+curl -fsSL https://raw.githubusercontent.com/devswha/patina/main/install.sh | bash
 ```
+
+## Post-launch triage
+
+- Collect false-positive reports under the `false-positive` label.
+- Use <https://github.com/devswha/patina/issues/new?template=false_positive.yml> for public false-positive reports.
+- Turn repeated missing patterns into pattern issues with examples.
+- Add strong before/after examples to `docs/EXAMPLES.md` or `examples/`.
+- Re-score public copy after edits; keep the launch thread evidence attached.

package/docs/social/patina-launch-execution.md

@@ -0,0 +1,94 @@
+# patina Launch Execution Packet
+
+Last prepared: 2026-05-23.
+
+Use this packet when the maintainer is ready to post. Agents may prepare copy,
+score proof, and follow-up notes, but should not publish from maintainer-owned
+accounts.
+
+## Current source files
+
+| Purpose | File |
+|---|---|
+| Broad channel copy | [`patina-launch-copy.md`](patina-launch-copy.md) |
+| Korean-first copy | [`patina-launch-korean-first.md`](patina-launch-korean-first.md) |
+| Top-of-funnel English guide | [`signs-of-ai-writing.md`](signs-of-ai-writing.md) |
+| Top-of-funnel Korean guide | [`signs-of-ai-writing_KR.md`](signs-of-ai-writing_KR.md) |
+
+## Pre-post checklist
+
+Run these before copying any post into a public channel:
+
+```bash
+node scripts/precommit-score.mjs \
+  docs/social/patina-launch-copy.md \
+  docs/social/patina-launch-korean-first.md \
+  docs/social/signs-of-ai-writing.md \
+  docs/social/signs-of-ai-writing_KR.md
+```
+
+Latest local result:
+
+| File | Score | Status |
+|---|---:|---|
+| `docs/social/patina-launch-copy.md` | 6.3% | pass |
+| `docs/social/patina-launch-korean-first.md` | 0.0% | pass |
+| `docs/social/signs-of-ai-writing.md` | 0.0% | pass |
+| `docs/social/signs-of-ai-writing_KR.md` | 20.0% | pass |
+
+Confirm the links used in broad posts:
+
+- Playground: <https://patina.vibetip.help/>
+- Repository: <https://github.com/devswha/patina>
+- False-positive form: <https://github.com/devswha/patina/issues/new?template=false_positive.yml>
+- Benchmark report: [`docs/benchmarks/latest.md`](../benchmarks/latest.md)
+
+## Posting order
+
+| Order | Channel | Copy source | Maintainer action |
+|---:|---|---|---|
+| 1 | GeekNews | `patina-launch-korean-first.md` → GeekNews | Post or mark deferred in the maintainer launch note. |
+| 2 | Velog | `patina-launch-korean-first.md` → Velog | Post or mark deferred in the maintainer launch note. |
+| 3 | Clien-style short post | `patina-launch-korean-first.md` → Clien-style short post | Post or mark deferred in the maintainer launch note. |
+| 4 | Show HN | `patina-launch-copy.md` → Show HN | Post with playground + repo links. |
+| 5 | Product Hunt | `patina-launch-copy.md` → Product Hunt | Use brand/social assets and maker comment. |
+| 6 | Reddit | `patina-launch-copy.md` → Reddit | Pick LocalLLaMA or writing/Korean angle. |
+| 7 | X / Threads / LinkedIn | `patina-launch-copy.md` → X / Threads | Use short copy and link playground first. |
+
+## Maintainer update template
+
+After each channel action, add a short entry to the maintainer launch note:
+
+```text
+Channel:
+Status: posted | queued | deferred
+URL:
+Copy source:
+Score command:
+Score result:
+Notes / feedback:
+```
+
+If a post is deferred, record the reason instead of leaving the checkbox
+ambiguous.
+
+## Feedback triage
+
+Capture useful launch feedback with enough detail to reproduce it:
+
+- language and register,
+- copied paragraph or a private/non-redistributable note,
+- score output,
+- expected behavior,
+- whether the reporter allows the text to be used as a fixture.
+
+Public false-positive reports should use:
+<https://github.com/devswha/patina/issues/new?template=false_positive.yml>.
+
+## Close criteria for the launch note
+
+Keep the maintainer launch note open until each channel is either:
+
+- posted with URL and score proof,
+- queued with owner/date,
+- or explicitly deferred with reason.