SAFETY-38: record the CI-06 false red, and where each mutation lands

All ten mutations of `site_standing` are red in test_watchdog.py and in nothing
else - the other 19 files are green under every one of them, which is the
measurement of how unpinned the line was.

One exception, recorded rather than dropped: in the batch run M10
(`sorted(standing.values())[-1]`) also reported FAIL test_peakguard.py. Re-run
in isolation three times and once more through tools/mutation_run.sh - four
clean passes. The batch script had discarded the failure detail so the check
cannot be named; what can be said is that it did not reproduce in four attempts
and that no claim in this card rests on it. That is CI-06's file behaving the
way CI-06 records.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BwRLw7eKYj2byVdwB6kbjU

goodwe_controller/CHANGELOG.md

@@ -91,8 +91,11 @@ shipped `sum` is correct and must not be "fixed".**
   300 W gate. Closed by part 9a's device-clamped counterfactual.
 * **10 mutations of that one line, each on a fresh full-repo copy mounted `:ro`,
   bytecode purged by `tools/mutation_run.sh`, the edit re-read from disk and the
-  byte delta printed. All 10 red.** Ledger and the honest gaps in
-  `DECISIONS/SAFETY-38-site-standing-pin.md`.
+  byte delta printed. All 10 red — every one of them in `test_watchdog.py` and
+  in nothing else.** ⚠️ One **false red** from `test_peakguard.py` on M10 did
+  not reproduce in four subsequent runs; it is CI-06's known flakiness, no claim
+  here rests on it, and it is recorded rather than quietly dropped. Ledger and
+  the honest gaps in `DECISIONS/SAFETY-38-site-standing-pin.md`.
 
 **Inverter B gets its own MQTT device, and inverter A keeps the one it has
 (TEL-07).** MQTT discovery announced **one** device, and every entity hung off