Sharpen changelog rule: only end-user-meaningful changes

Claude-Session: https://claude.ai/code/session_01A9CfUa4E9Zd5swfoNsYPs7
2026-06-20 19:12:44 -04:00
parent 707d71eaf0
commit 50838832d4
1 changed files with 1 additions and 1 deletions
@@ -96,6 +96,6 @@ Seeded on demand, never automatically — an empty cache at launch is indistingu
 - Group entries by month, newest month first; a version milestone (e.g. **2.0**) may prefix the entry it applies to.
 - Write each entry as its own blank-line-separated paragraph — **no bullet or dash markers**, because the Apple inline-Markdown subset IndieAbout renders doesn't style them (see the `indie-about` skill for the supported subset).
 - Derive entries from the git log, but rewrite (don't copy) each into a concise, end-user-understandable description of the crux of the change.
- Include only changes significant to an end user; skip internal / tooling / refactor-only commits. In particular, never log changes to the changelog itself (its preamble, formatting, or how it's derived) — these have zero end-user value.
+- Include only changes with substantive meaning for an end user — app behavior, new features, and the like. Skip anything else (internal / tooling / refactor / docs-only commits).
 - When one commit holds several user-facing changes, split them into separate paragraphs.
 - When several commits address the same user-facing change, collapse them into one paragraph.