diff --git a/PENDING.md b/PENDING.md
index de0eb12..fa3d8ac 100644
--- a/PENDING.md
+++ b/PENDING.md
@@ -4464,3 +4464,49 @@ A partition with no exceptions in either direction. **One opaque integer written
 ⚠ **THE CITATIONS ARE NOT TO BE CORRECTED BY EDITING.** A placed ruling is amended by a recorded act. The errata entry is drafted for steward placement; **no in-place revision has been made, and the temptation to make one has now arisen twice this week.**
 
 **Awaiting:** unchanged for the remaining nine items. Item 1 is closed; item 11 awaits a ruling on the anchor remedy.
+
+### ADDENDUM 1 — 2026-09-10 — Executor: two further instances, found by checking, and a measurement that narrows the mechanism
+
+**Filed by the executor into a steward-originated item**, because it supplies the
+instances the item's argument turns on. No part of PENDING-181's proposal is amended.
+
+**Instances 4 and 5, both in entries placed today, both found within minutes by an
+exact-string check rather than a reading.**
+
+- **REVIEWED-138's title broke across two lines**, terminating at *"under a per-control
+  reading of"* with *"instance four)"* orphaned below. **This is instance 3 recurring —
+  same failure, same week, in an entry drafted to be quotable, in the sitting that filed
+  this item about it.**
+- **REVIEWED-139's table lost a row and half of another.** The separator row and the
+  entire `tarbuckle-wrap.py:236 → :256 / 7948c09` row are absent; the remaining row
+  survives only as the dangling fragment `` **`3d45e3a`, 2026-09-09** | ``. ⚠ **The
+  errata entry whose subject is citations that do not hold currently holds neither of
+  its two citations correctly.**
+
+**THE MEASUREMENT, WHICH NARROWS THE MECHANISM AND ALSO REFUTES THE OBVIOUS READING.**
+
+- The 68 non-empty lines placed today cap at **156 characters**, clustered at 147–156,
+  with 28 over 150. That is a hard wrap at roughly column 150.
+- ⚠ **The rest of the register is NOT wrapped: 2,680 lines, longest 2,184 characters,
+  502 of them over 150.** So wrapping is not a standing property of the transit path,
+  and **why today differs is UNESTABLISHED.** Recorded as unexplained rather than
+  attributed, because the attractive explanation is untested.
+
+**What the damage is predictable from, and this part IS established:** the wrap destroys
+exactly those constructs where a newline is semantic — a `##` heading ends at the
+newline, and a table row is a line — while prose reflows harmlessly. **Every corruption
+in this item's list is a heading, a table row, or a clause; none is a paragraph.**
+
+⚠ **THE CHEAP MITIGATION, AVAILABLE TO THE EXECUTOR TODAY AND NOT REQUIRING THIS ITEM'S
+PROPOSAL:** draft headings and table rows **short enough that no wrap can reach them**,
+and prefer **bulleted lists to tables**, since a wrapped bullet continues as the same
+bullet while a wrapped row is destroyed. This does not replace the item's remedy — it
+removes the executor's contribution to the failure while the remedy is decided.
+
+⚠ **AND THE FINDING THAT MATTERS MOST FOR THE ITEM'S ARGUMENT: both defects were found
+by running a check, not by reading.** Instance 2 was found by `grep -c` a day later;
+these were found in minutes because the placement was verified against the draft with
+exact strings and a negative control. **The transit path is not self-reporting, and
+nothing in the current arrangement checks a paste except a party deciding to.**
+
+**Awaiting:** unchanged — steward authorization on the parent proposal.