From b93211e37e3f1d8fe633ceb5c16b335be854b2ab Mon Sep 17 00:00:00 2001 From: Jason Woltje Date: Sun, 11 Oct 2026 16:17:16 -0500 Subject: [PATCH] docs(queue-62): the correction's fail-closed sentence overclaimed; name the assumption Co-Authored-By: Claude Opus 5.5 --- agents/darkwing/work/queue-62/BUILD.md | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/agents/darkwing/work/queue-62/BUILD.md b/agents/darkwing/work/queue-62/BUILD.md index d28bdaac3..107adc9b4 100644 --- a/agents/darkwing/work/queue-62/BUILD.md +++ b/agents/darkwing/work/queue-62/BUILD.md @@ -604,10 +604,12 @@ 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 +The fix rests on one assumption about the live instance: `GET +/projects/` answers 403 or 404 only when the bot can't read the +project. Any other answer fails the tick. If the live route answered 404 +for a project whose kanban view was deleted, the child would drop and +round 2's false tombstones would come back. A read-only live probe would +settle 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.