From 78a244bf0949b371c07370c6f0a4bcf3bbe0ff86 Mon Sep 17 00:00:00 2001 From: kisfenyo Date: Tue, 18 Aug 2026 15:17:48 +0200 Subject: [PATCH] REPORT: CI run 355 by id, and the commit hash --- REPORT-register-and-floor.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/REPORT-register-and-floor.md b/REPORT-register-and-floor.md index 0f7f3797..adfb2c3c 100644 --- a/REPORT-register-and-floor.md +++ b/REPORT-register-and-floor.md @@ -234,6 +234,22 @@ its last report on 2026-07-15 08:39:00 — a stale record, not a live box. Both read as the task described. **No ISO rebuild is required:** the golden is fetched at first boot from the hub's manifest (0.216.0 — at the floor, not below it), and this gate governs *future* builds. + +## 9. Commits and CI + +| commit | contents | +|---|---| +| `0a5e9b14dc84ecfb179b2654d079c2f6d3f15fe2` | the gate, its tests, registration, both register rows, the block, and all §5 documentation | + +**CI run `355`, `head_sha 0a5e9b14d`, conclusion `success`** (started 2026-08-18T13:17:04Z). The +previous run `354` on `f267bc047` was also green, so this run's green is attributable to this change +rather than inherited from a red baseline — and per §13 of the task, a red run here would have been +mine to own. + +**The push needed no `--no-verify`.** The pre-push hook ran `repo_gates.py --fast`, including the new +`due-checks` gate, and passed — so the gate has now run in its real place, in both homes, not only in +its own test suite. + ## 10. NOT yet validated **The gate has never fired on a real overdue date in the live register.** Every conviction shown here