REPORT: correct the register line count (620 -> 688, one measure) and record the CI run ids

Both earlier commit messages carried a wrong line count - 621->688 and 688->700 - because I
mixed wc -l with a Python line split and then carried the error forward. Corrected in the
report rather than by rewriting history, and named there.

CI verified by run id against head_sha: 500, 501, 502 all success.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01LB8FmJaGd2cyjvy6dbEjpM

REPORT.md

@@ -153,13 +153,21 @@ block exists for, and it was never entered.
 
 | | before | after |
 |---|---|---|
-| file lines | **621** | **688** |
+| file lines (`wc -l`) | **620** | **688** |
 | total `R-` rows | **181** | **182** |
 | open-state rows | **170** | **169** |
 | closed / decided / answered rows | **11** | **13** |
 
-*(The brief's "620 lines and 181 open" matches the file length and the row count; the count of rows
-whose leading verdict is actually open was 170.)*
+*(The brief's "620 lines and 181 open" matches the file length and the row count exactly; the count
+of rows whose LEADING verdict is actually open was 170, which is the number that matters and is not
+the same thing.)*
+
+**A correction to my own commit messages, made here rather than by rewriting history:** the
+`db38f4c` message says `621 -> 688` and the `1a1b32b` message says `688 -> 700`. Both are wrong. I
+mixed two measures — `wc -l` and a Python line split that counts the trailing newline as a line — and
+then carried the error forward. **The table above is `wc -l` throughout and is the number to trust:
+620 → 688.** It changes nothing about the work and it is exactly the class of sloppiness this project
+files rows about, so it is named rather than quietly fixed.
 
 **Rows closed:** **R-434** — with the deletion-not-replacement reasoning, and with the fact that its
 own "blocked on R-433" verdict was wrong recorded in the closing cell.
@@ -240,6 +248,15 @@ were not touched.
 `python3 scripts/unproven.py --summary`: **NOT WALKED 35 of 55 — unchanged.** No claim moved, which
 is correct: nothing was proven today. All **14** `felhom.eu` gates green before every push.
 
+**CI, checked by run id against `head_sha` rather than assumed** (the R-417 recipe — the
+`actions/jobs` endpoint, paged to the end):
+
+| run id | commit | conclusion |
+|---|---|---|
+| **500** | `db38f4c` — hub v0.111.1 + the stopping line | **success** |
+| **501** | `0f65f7a` — manifest bump to 0.111.1 | **success** |
+| **502** | `1a1b32b` — REPORT + R-437 | **success** |
+
 ## 8. Observations
 
 1. **`strings` stops at the em dash, so the alarm sentence appeared truncated in the deployed