From 093d677c05380392b66c11b4442b24c530aba84c Mon Sep 17 00:00:00 2001 From: Levi Neuwirth Date: Mon, 31 Aug 2026 20:28:58 +0200 Subject: [PATCH] docs(ci-reds): U19's title repeated the claim its body withdraws The heading said "a terminal bell never arrives within a 5s poll" while the body two paragraphs down withdraws exactly that: the evidence shows the bell was not OBSERVED within five seconds, not that it never came. A title is the part most readers keep, so it was the worse place to leave it. Retitled to match. U16 said its reds and greens were "across two days". Every run the row cites --- both reds and every green --- is 2026-08-31, which the sentences immediately above it already said twice ("again the same day", "returned within the day"). Corrected in both files. --- docs/active-work.md | 4 ++-- docs/ci-red-signatures.md | 7 ++++--- 2 files changed, 6 insertions(+), 5 deletions(-) diff --git a/docs/active-work.md b/docs/active-work.md index 8a6e37f..a48aba3 100644 --- a/docs/active-work.md +++ b/docs/active-work.md @@ -433,8 +433,8 @@ U17, U18 and U19. *(This heading said "four" while listing more; corrected.)* the failure returned within the day. The child-inheritance chain stays a candidate; this occurrence demonstrates it no more than the first did. **It then passed in all three stages of the next gate - run** — two reds and many greens across two days, intermittent at a - rate nothing has measured. + run** — two reds and many greens **all on 2026-08-31**, intermittent at + a rate nothing has measured. - **U19, new** — `terminal_bell_baseline_…` timed out on a **5-second** poll, in the same run as U16's second. The evidence is that **no bell was observed within five seconds** — not that one never came, and not diff --git a/docs/ci-red-signatures.md b/docs/ci-red-signatures.md index 2d9ce44..8546a42 100644 --- a/docs/ci-red-signatures.md +++ b/docs/ci-red-signatures.md @@ -1589,8 +1589,9 @@ demonstrates the chain either. **And it passed again immediately after**, in all three stages of the next gate run — `03-lib`, `04-lib-crdt` and the same `07-sweep` context — at `ea786a2`, log `20260831T174716Z-3535694`. Two reds and many greens -across two days: **intermittent**, at a rate nothing here has -measured. +**all on 2026-08-31**: **intermittent**, at a rate nothing here has +measured. *(An earlier version said "across two days"; every run cited +by this row is the same day, as the sentences above it already said.)* **Not folded into U14 or U15.** Different selector, different fragments, different step, and a different kind of failure: those are wall-clock @@ -1735,7 +1736,7 @@ would pass is uninteresting — a transient network error is *expected* to pass on retry, and doing so would establish nothing while destroying nothing either. It is left for whoever next pushes to this branch. -### U19 — a terminal bell never arrives within a 5s poll +### U19 — a terminal bell is not observed within a 5s poll Recorded on the CRDT identity-undo lane, 2026-08-31, local (Linux), `scripts/gate` step `07-sweep`, log `20260831T174104Z-3438184` — the