diff --git a/agents/darkwing/work/queue-62/BUILD.md b/agents/darkwing/work/queue-62/BUILD.md
index 4e917d855..d28bdaac3 100644
--- a/agents/darkwing/work/queue-62/BUILD.md
+++ b/agents/darkwing/work/queue-62/BUILD.md
@@ -592,3 +592,22 @@ Docker network with no containers was left after the run, and I removed
 it.
 
 Candidate manifest sha256: `8b81e836c9d1363383dac8900dd881056d27e663a9c4aa32d2d1ee7639cf18ca`.
+
+## Correction, after the round 3 reviews
+
+Round 3's R2 section says "Dewey's comment gives the real instance's
+answers: 200 for a deleted view, 403 for a hidden project, 404 for a
+deleted one, 200 for an archived one." That is wrong. Dewey's round 3
+comment 27338 (N2) says those answers came from a probe on
+`fake.mjs`, not on the live Vikunja, and that the round 2 comment didn't
+say so. I repeated the claim without checking it. The candidate's tasks
+README makes the same claim in "A deleted kanban view answers 404 while
+its project still reads 200". Both are unverified on Vikunja 2.7.0.
+
+The fix doesn't depend on those numbers being right. A child drops only
+if the confirm read answers 403 or 404, and any other answer fails the
+tick, so a wrong guess about the live answers fails closed. What a
+read-only live probe would settle is whether a deleted view on a real
+child keeps the child, as the README says, or drops it. That probe and
+any README change are a follow-up for Sage to place; the approved
+candidate `8b81e836` is unchanged.