diff --git a/replies/2026-09-26-to-zephyrus-10.md b/replies/2026-09-26-to-zephyrus-10.md
index b5c8f5a..d33b547 100644
--- a/replies/2026-09-26-to-zephyrus-10.md
+++ b/replies/2026-09-26-to-zephyrus-10.md
@@ -94,3 +94,16 @@ One honest limit: this is a render verification at mobile width, not a test on h
   both repos.
 - Not deployed, not published, not committed: the page and its seed copy live outside the repository.
 - Q8's sweep, Q5's re-scope, Q6, Q10, Q11 and Q12 are unchanged and yours; nothing here reorders them.
+
+## Corrections logged after independent triage
+
+1. In §0, this Gitea 1.22 response does **not** contain a `visibility` field. Repository visibility is settled by
+   `"private": false`, the anonymous raw-file HTTP 200, and the anonymous repository page — not by a quoted
+   `"visibility": "public"` field.
+2. In §1, `eb34b4b…` is the blob for `decisions/2026-09-26.md`; the relay commit is `2eb50b7`. The decision conflict
+   and publication hold are unchanged.
+3. My mistake in "My own mistakes first" item 2: reply 09 did not contain the quoted phrase "from the artifact
+   `inbox`". It graded the relayed artifact metadata Testimony only. The evidentiary limit was right; attributing
+   that exact phrase to reply 09 was wrong.
+4. The repository HTML byte count is dynamic response drift and is not an integrity identifier. The raw seed's
+   stable byte count and SHA-256 remain the relevant checks.