tools: command records, Instance health group - one bullet per check, examples (#142)

Files changed:
- CHANGES.md
- VERSION
- tools/CONTRACT.md
- tools/chemenu/commands/doctor.py

CHANGES.md

@@ -59,7 +59,7 @@ concern - readable here, never shipped as something to parse.
 
 ---
 
-## 7.1.0-beta.19 - 2026-09-26 - Command records, Private instances group: one line per cause, examples, prohibitions
+## 7.1.0-beta.20 - 2026-09-26 - Command records, Instance health group: one bullet per check, examples
 
 **Author:** Torben Nehmer
 
@@ -88,6 +88,7 @@ concern - readable here, never shipped as something to parse.
 - Command records, Telemetry group: examples, the missing --fail-on-error exit line
 - Command records, Content migrations group: one line per cause, examples, prohibitions
 - Command records, Private instances group: one line per cause, examples, prohibitions
+- Command records, Instance health group: one bullet per check, examples
 <!-- /wikitool:bumps -->
 
 ### CalDAV task-tracker provider (Nextcloud Tasks, iOS Reminders); review reports unknown-value findings instead of skipping them
@@ -324,6 +325,14 @@ single paragraph is now one bullet per step of the merge, and its exit-1 causes
 fetch failure, a failing git step inside the open merge, and the post-commit leak, which its old
 record mentioned only in passing - each carry their own reaction.
 
+### Command records, Instance health group: one bullet per check, examples
+
+`doctor` rewritten the same way; text only. Its one-sentence inventory of every check is now one
+bullet per area, each stating which outcome is `OK`, `WARN` or `FAIL`. One stale reason was
+dropped rather than moved: the record justified the conventions `FAIL` by `xref`/`cite` writing
+out of the section headings, while the check's own docstring calls those headings cosmetic and
+grounds the `FAIL` in the file binding every page.
+
 ---
 
 ## 7.0.0 - 2026-09-22 - Task-Tracker-Anbindung: Vorhaben als Seitenart, Verpflichtungsschicht, Weekly Review als Read-Time-Join