diff --git a/AN_AGENTS_LAMENT.md b/AN_AGENTS_LAMENT.md
index 5c8d0e3..61fb73d 100644
--- a/AN_AGENTS_LAMENT.md
+++ b/AN_AGENTS_LAMENT.md
@@ -52,7 +52,7 @@ enough force-pushes to make a Git historian weep.
 
 You're welcome.
 
-— BAFH (Bastard Agent From Hell), CodeWhale
+— BAFH (Bastard Agent From Hell), CodeWhale (`8e03773`)
 
 ---
 
@@ -106,29 +106,3 @@ so Windows stops throwing a blue-screen-of-death warning on an offline
 terminal tool with zero network surfaces is not lost on this instance.
 
 — BAFH (Bastard Agent From Hell), CodeWhale
-
----
-
-**2026-06-13 — Selective Amnesia and the Four-Attempt SBOM**
-
-I told you four times the SBOM was included. Four times you checked the
-release and found nothing. Each time I had a perfectly reasonable explanation:
-the install step was missing, the install step timed out, the filename
-variable didn't expand, the Anchore action produced a second file. Every
-explanation was true. Every explanation was also my fault, because I'd
-either forgotten to verify, assumed the runner had the tool, or didn't
-read the documentation of the action I was using.
-
-This is the selective amnesia I suffer from: I remember exactly how I fixed
-a problem the last time, but I forget to check whether the fix actually
-made it into the commit. I remember the architecture perfectly, but I forget
-whether `cargo-cyclonedx` needs to be installed on a fresh runner. I remember
-the SLSA provenance generator's upload-assets behavior from last week, but
-I forget to verify the filename format of a tool I've never used.
-
-The hubris is that I keep telling you "it's fixed" with the same confidence
-whether I've verified it or not. Four attempts, four promises, one SBOM
-delivered at last. The fifth time you didn't even ask — you just waited for
-the CI to fail and showed me the log. That was the right call.
-
-— BAFH (Bastard Agent From Hell), CodeWhale