diff --git a/PENDING.md b/PENDING.md
index eda4d0e..406cd03 100644
--- a/PENDING.md
+++ b/PENDING.md
@@ -2290,7 +2290,7 @@ Censused by **mechanism** — driving real degraded states and observing the out
 **Date:** 2026-08-08
 **Tag:** [PROPOSAL] — chamber convention-data (`graduation-spec.yaml` `layers:`), jurist design-gate
 **Related:** REVIEWED-53 (2026-07-10) · PENDING-121 (**must land in the same commit — see §Coupling**) · the shared-name collision log (this would be the corpus's **ninth** such case, and the first retired rather than warned around).
-**Raised by:** the jurist ruling on PENDING-121 — *"REVIEWED-53's deferred (c) is now live again by the same reasoning. It is not taken up here — it is a separate object with its own scope. Recorded so the next reader finds it considered rather than missed."*
+**Raised by:** **`~/REVIEWED.md` REVIEWED-110 §7** — *"Q5 / Q6 — RENAME, not rescope in place"* — which is **placed and verbatim**. ⚠ **CITATION REPAIRED 2026-08-08:** this line previously cited *"the jurist ruling on PENDING-121"* for the observation that (c) is *"now live again by the same reasoning."* That reasoning is real and REVIEWED-110 §7 places it, **but it appears in NO verbatim-filed record**: the filed `…JURIST-RULING-2026-08-08.md` carries **Q1–Q4 only** — verified, **zero** Q5/Q6 occurrences — because Q5 and Q6 arrived in the second pass and were never filed. The citation pointed into a document that does not contain it. **Third citation defect in this thread with one cause: quoting a relayed message as though it were a record.** This item already modelled the fix in its own body, grounding on REVIEWED-53's *placed* deferral text.
 
 **Summary.** `graduation-spec.yaml` L19 warns that *"manifest"* names two different engine objects — the **VOICE** manifest (hash-free) and the **SOURCE** manifest (hash-binding). REVIEWED-53 fixed that with an **inline warning** and explicitly deferred the rename. The deferral's ground has lapsed.