Release Healer Man 0.1.6

RELEASE_RUNBOOK.md

@@ -18,6 +18,21 @@ approval before it commits, pushes `main`, builds the signed APK, and publishes
 the Gitea release. Signing passwords and the Gitea token are passed to the
 child process in memory rather than on its command line.
 
+Before changing versions or running the longer test/build sequence, the manager
+runs an isolated release-candidate check. It validates tracked and untracked
+files without changing the real Git index, so extra blank lines at EOF and
+other whitespace errors fail immediately. Run the same fast check at any time:
+
+```powershell
+npm run release:check
+```
+
+Editors should honor the repository's `.editorconfig`. The checked-in VS Code
+settings also trim extra final newlines whenever a file is saved.
+Git may print a one-time CRLF-to-LF conversion warning when an existing Windows
+working copy is first staged under `.gitattributes`; that warning is not a
+release failure, and subsequent repository text stays consistently LF.
+
 The local release key is `F:\secure\healer-man-release.jks`. When the companion
 `healer-man-release-password.dpapi` file is present, blank signing-password
 fields are filled from that Windows user-encrypted credential in memory. The
@@ -254,11 +269,14 @@ npm run dev
 First check for whitespace errors and review the final file list:
 
 ```powershell
-git diff --check
+npm run release:check
 git status --short
 git diff --stat
 ```
 
+Use `npm run release:check` before the longer release validation. Unlike
+`git diff --check`, it includes new, untracked files.
+
 Stage the intended release:
 
 ```powershell
@@ -520,7 +538,7 @@ Set-Location F:\Projects\HealerMan
 npm run content:test
 npm run build
 git status --short
-git diff --check
+npm run release:check
 git add -A
 git status --short
 git diff --cached --stat