Skip to content

Commit c84c262

Browse files
committed
docs(devlog): fix the alert list and record that #87 closed
The six open js/polynomial-redos alerts I listed included #84, which had already been fixed fourteen minutes before I wrote the list, and omitted #50, which is open. Still six, one member wrong. The live set is #83, #60, #53, #52, #51, #50, all from 2026-08-12/13 - so the scoped claim holds: this campaign introduced exactly one and fixed exactly that one. And the one it introduced has now closed. Alert #87 reads fixed as of 03:17:06Z from the rescan of main. The earlier text predicted that and declined to claim it in advance, which turned out to be the right call.
1 parent e4ba9c4 commit c84c262

1 file changed

Lines changed: 10 additions & 1 deletion

File tree

‎devlog/_plan/260817_wave5_execution/090_wave6_closeout.md‎

Lines changed: 10 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -330,7 +330,7 @@ JS/TS run there; until it does, this campaign does not claim it closed.
330330

331331
A reviewer asked whether other instances of the same pattern remain. **Yes — 30 occurrences of
332332
`/\/+$/` across `src/`**, with open `js/polynomial-redos` alerts on at least six
333-
(#83, #84, #60, #53, #51, #52) covering `openai-chat-url.ts`, `openai-responses-url.ts`,
333+
(#83, #60, #53, #52, #51, #50) covering `openai-chat-url.ts`, `openai-responses-url.ts`,
334334
`openai-responses.ts`, `openai-chat.ts` and `anthropic.ts`.
335335

336336
All predate this campaign (created 2026-08-12/13), so the scoped claim — *this campaign
@@ -353,3 +353,12 @@ the *file* count; measured now it is **39 occurrences across 27 files**, one of
353353
comment explaining the removal. Understating the remaining debt inside the section whose whole
354354
purpose is to not understate it was the wrong direction to be wrong in. Repo-wide open alerts
355355
have also drifted from 71 to 70 with the same rescan.
356+
**Correction to the alert list.** The six I named included **#84**, which had already been fixed
357+
at 03:03:30Z — before I wrote the list — and omitted **#50**, which is open. Still six, but one
358+
member was wrong. The live open set is #83, #60, #53, #52, #51, #50, all created 2026-08-12/13,
359+
which leaves the scoped claim intact: this campaign introduced exactly one `js/polynomial-redos`
360+
alert and fixed exactly that one.
361+
362+
**And the one it introduced is now closed.** Alert #87 reads `fixed`, `fixed_at
363+
2026-08-18T03:17:06Z`, from the JS/TS rescan of `main` at `1f4e0470e`. The earlier text
364+
predicted this would happen on the next scan and declined to claim it had; the prediction held.

0 commit comments

Comments
 (0)