diff --git a/docs/CURRENT-STATE.md b/docs/CURRENT-STATE.md
index 0c00e04..b3a11bb 100644
--- a/docs/CURRENT-STATE.md
+++ b/docs/CURRENT-STATE.md
@@ -2013,6 +2013,25 @@
   at `life: dead`** -- that moved it BACK to `dying` and re-armed the undertaker loop. It
   did not help and it changed state. Both are now written into Path M as explicit
   prohibitions.
+  **>>> CONVERGENCE UPDATE 2026-08-03 05:08Z: THE PACKAGE-INSTALL BLOCKER IS GONE; A KNOWN
+  IPv6 CONDITION SURFACED. <<<** 8/9 machines `started`, 6 units `active`, **ZERO units in
+  `error`** -- the first deploy had NINE at `hook failed: "install"` from `NO_PUBKEY`, so the
+  D-135 amendment (b) convergence is PROVEN end to end: packages install through the proxy.
+  The remaining `blocked` states are the expected early-convergence set (`vault/0` needs-init,
+  `octavia` awaiting-configure, mysql not-yet-clustered, `ceph-rbd-mirror` missing its
+  cross-DC peer, `designate` nameservers = Stage 7) EXCEPT one that is a real finding:
+  **keystone/0 `Invalid vips: [2602:f3e2:f02:11::50, :20::50, :21::50]`** -- the three GUA v6
+  VIPs from the overlay. MEASURED cause: the keystone LXD container has ZERO global IPv6
+  addresses (`ip -6 addr show scope global` empty, exit 0), so the charm cannot place a v6
+  VIP on a space the container has no global v6 on. **This is a KNOWN-SHAPE condition, not a
+  regression from this session:** finding D3 (07-31 deploy) already records "the NODES are
+  dual-stacked; the LXD CONTAINERS the API charms run in are NOT". It surfaced then as
+  `prefer-ipv6` fatal errors; with D-139's GUA VIP overlay the same container-v6 gap now
+  surfaces as `Invalid vips`. It is the IPv6/dual-stack layer still being hardened
+  (BUILDOUT), and it is LOGGED, not fixed -- it needs an operator decision (carry the v4 VIPs
+  only for now, or address the containers on the v6 planes) and is NOT chased mid-convergence.
+  The v4 VIPs in the same config (`10.12.4.50 10.12.8.50 10.12.12.50`) are accepted.
+
   **>>> THE dc0 BUNDLE IS RE-DEPLOYED ONTO THE REBUILT CONTROLLER WITH THE CONVERGED CONFIG,
   2026-08-03. `Deploy of bundle completed.` EXIT 0. <<<** 04:39:32Z -> 04:41:26Z. Step 4.4
   config gate ALL PASS, and it clears the two failure modes that blocked the first attempt: