diff --git a/docs/CURRENT-STATE.md b/docs/CURRENT-STATE.md
index e4049af..0c00e04 100644
--- a/docs/CURRENT-STATE.md
+++ b/docs/CURRENT-STATE.md
@@ -2013,6 +2013,21 @@
   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.
+  **>>> 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:
+  **item 1** -- `ovn-chassis` carries ALL THREE options (`bridge-interface-mappings`
+  = `br-ex:52:54:00:8c:2a:8c br-ex:52:54:00:50:48:88` (exactly two MACs), `ovn-bridge-mappings`
+  = `physnet1:br-ex`, `prefer-chassis-as-gw` = `true`), so the options map merged key-by-key;
+  **item 2** -- every origin now resolves to `cloud:jammy-caracal` or the charm default
+  `caracal`, NOT a raw `deb` line, so the `NO_PUBKEY 5EDB1B62EC4926EA` signing-key failure
+  CANNOT recur -- the `cloud:` path installs `ubuntu-cloud-keyring` as its side effect, and
+  the apt-cacher-ng proxy serves the UCA content. Convergence IN PROGRESS: at t+0 nine
+  machines `pending`, 33 units `waiting`, zero error/blocked -- the expected shape.
+  **NEXT: watch to the phase-01 PRE-vault-init end state** (nine machines `started`, zero
+  units `error`, only `vault/0` and `octavia` blocked on their expected triggers), then
+  Step 5 (vault bring-up).
+
   **>>> THE dc0 JUJU CONTROLLER WAS REBUILT FROM MAAS 2026-08-03 AND THE ENVIRONMENT IS READY
   FOR THE DEPLOY. <<<** Operator ruling: *"There is no reason to troubleshoot the controller
   issues or gracefully try to repair at this point. It will be easier and cleaner just the