diff --git a/BUILD-LOG.md b/BUILD-LOG.md
index 25ef568f..7a029467 100644
--- a/BUILD-LOG.md
+++ b/BUILD-LOG.md
@@ -3794,3 +3794,5 @@ Not done: the broker's startup probe waits for row S3. No suite covers this work
 ### 2026-10-09 — Sage, S3 live run on tasks.mosaicstack.dev, row 35 gate met (#1517, lead decision 75)
 
 `node packages/tasks/live/run.mjs` against tasks.mosaicstack.dev, project 32, business mosaic-stack, with the sync, pm, coder and reviewer token files from runbook section 3. The broker's startup reached `ready` on v2.7.0 (tested version), so its scope probe passed for every slice 1 tracker identity. All 17 steps went as expected, task 144 closed done, and both closing ticks and the reconcile recorded 0 snapshots. Exit 0. Receipt: `agents/sage/work/vikunja-setup/live-2026-10-09/live-run.txt` and `live-setup.json`, which hold paths only. cto isn't a slice 1 tracker role; the round-trip probe from the setup run covered its isolation. Row 35's gate is met (Darkwing approved round 3 in #1517 comment 26715). The queue refused `move 35 done` from waiting-on-jason without Jason's approval as evidence, so the row waits there for him. Rows 40 (Dewey) and 41 (Filbert) were dispatched.
+
+Correction, 2026-10-09 22:58Z, Sage: my push after the rows 40-41 briefing went out after Dewey committed 1f4882d2 (docs(wui), design work: brand board, five mockups, slice 1 S5 views and checks). The queue commit had refused because HEAD moved, but the push line ran on its own and sent Dewey's commit, which I hadn't reviewed. I checked it after the fact: every path is under `agents/dewey/work/wui/` (docs, PNG evidence, check scripts), and a scan for token and key patterns found nothing. From now on my push checks `git log origin/refactor..HEAD` and refuses unless every commit ahead is one of mine.