From f6058b9a0022c04d85185b6915cc73eb94ca3fe3 Mon Sep 17 00:00:00 2001
From: autonomic-bot <autonomic-bot@git.autonomic.zone>
Date: Thu, 11 Jun 2026 15:49:33 +0000
Subject: [PATCH] =?UTF-8?q?review(bsky):=20post-verdict=20DECISIONS=20cons?=
 =?UTF-8?q?ult=20=E2=80=94=20pin-choice=20+=20EXPECTED=5FNA=20entries=20co?=
 =?UTF-8?q?nsistent=20(digest-pin=20rejected=20for=20abra=20tooling);=20ve?=
 =?UTF-8?q?rdict=20unchanged?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 REVIEW-bsky.md | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/REVIEW-bsky.md b/REVIEW-bsky.md
index 89a6c74..a9655d3 100644
--- a/REVIEW-bsky.md
+++ b/REVIEW-bsky.md
@@ -229,3 +229,10 @@ done WITH the PR open — merging is the operator's, post-merge reseeding docume
 weakening, no secret leak, screenshot real, PR unmerged. The Builder is cleared to write
 `## DONE` to STATUS-bsky.md. (Post-verdict I will consult JOURNAL/DECISIONS only to
 contextualise — it does not change this verdict.)
+
+### Post-verdict consult (does NOT change the verdict)
+Read DECISIONS.md bsky entries after writing M2 PASS. Fully consistent: pin-choice entry
+REJECTS 0.5.1 (no release tag + index.ts migration) AND digest-suffix pinning (abra
+survey/upgrade tooling chokes on `tag@digest`) → exact-version tag 0.4.219 chosen (satisfies
+plan §2.2 "digest-pinned OR exact-version tag"). EXPECTED_NA entry matches the harness
+behaviour I verified. No contradiction, no new finding.