From d32940d3e182d6f77b498ba3fc52cd6e4d430122 Mon Sep 17 00:00:00 2001
From: autonomic-bot <autonomic-bot@git.autonomic.zone>
Date: Wed, 17 Jun 2026 10:48:12 +0000
Subject: [PATCH] =?UTF-8?q?review(canon):=20clean-serial=20sweep=20obs=20?=
 =?UTF-8?q?=E2=80=94=20drone=20STILL=20promote-fails=20clean=20(lock=20fix?=
 =?UTF-8?q?=20cured=20hang,=20not=20promote;=20M2=20risk);=20gitea=20new-t?=
 =?UTF-8?q?ag=203.5.3->3.6.0=20advance=20=3D=20live=20M2.6=20evidence?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 machine-docs/REVIEW-canon.md | 21 +++++++++++++++++++++
 1 file changed, 21 insertions(+)

diff --git a/machine-docs/REVIEW-canon.md b/machine-docs/REVIEW-canon.md
index 4bd238d..33a9a95 100644
--- a/machine-docs/REVIEW-canon.md
+++ b/machine-docs/REVIEW-canon.md
@@ -290,3 +290,24 @@ canonicals (cryptpad, custom-html, custom-html-tiny, ghost, gitea, hedgedoc, imm
 the concurrency window and was produced single-run — do NOT take the Builder's accounting on faith;
 check `canonical.json` ts per recipe vs the 09:10–10:24 overlap. And confirm the claimed sweep (1741209)
 ran start→finish with no second sweep process alive.
+
+## Pre-claim observation @ 2026-06-17T10:47Z — clean serial sweep progress (NOT a verdict)
+
+ONE sweep proc confirmed (serial intact). Transient `_sweep.log` lines captured before rotation:
+- **CONCERN — `drone rc=0 GREEN-BUT-PROMOTE-FAILED (canonical=none, expected 1.9.0+2.26.0)` in the
+  CLEAN serial run.** Drone promoted under the discarded tainted validation but FAILS to promote
+  clean-serial — and it no longer hangs (returns cleanly), so the lock-release fix (655a999) cured the
+  46-min deadlock but drone's warm promote still fails for a DIFFERENT reason (likely warm gitea-dep
+  provisioning or warm deploy/health). Net: the lock fix is necessary-but-not-sufficient for drone;
+  drone will lack a canonical → hits both promote-evidence and determinism (run-twice) at the claim.
+  Builder will see it in their own running log; their diagnose. I'll require drone to either promote
+  clean or be a recorded DECISIONS exception (like bluesky) at claim — a silent no-canonical is not OK.
+- **FAVORABLE — `gitea RUN — new release 3.6.0+1.24.2-rootless > canonical 3.5.3+1.24.2-rootless;
+  cold-testing tagged release 3.6.0…`** — a LIVE instance of the new-release-tag trigger advancing an
+  existing canonical (older→newer TAGGED), i.e. exactly the M2.6 samever-orthogonality path (2):
+  canonical(older)→new tagged, real delta, promote-if-green. If gitea promotes to 3.6.0 this is strong
+  M2.6 evidence (no constructed scenario needed). VERIFY AT CLAIM: gitea's canonical advances 3.5.3→3.6.0
+  with the new tag's own commit, and samever's same-version step-back NEVER fired in the run (the tag
+  trigger guarantees vX→vY, Y>X, so no vX→vX). Watch that gitea actually promotes (not GREEN-BUT-FAILED).
+- SKIPs (cryptpad/custom-html/custom-html-tiny/ghost = no-new-version) and discourse rc=143 red:
+  consistent with prior runs.