diff --git a/docs/session-ledger.md b/docs/session-ledger.md
index ae6a04e..a3da478 100644
--- a/docs/session-ledger.md
+++ b/docs/session-ledger.md
@@ -706,19 +706,17 @@
 item **20** CLOSED for Office1 + the skill's per-DC discipline). Gauntlet ALL GREEN (67), repo-lint 0-fail,
 next-free D now **129**. `main` untouched (stage-close merge deferred).
 
-**TWO CARRY-FORWARDS (deliverables CLOSED; these are NOT -- do not mark them done):**
-1. **Boot-race proof.** `site-baseleg-office1.service` is installed + enabled, but the `After=libvirtd`+poll
-   race is UNPROVEN until an ACTUAL reboot self-heals `ssh voffice1` with no manual step. If `ssh voffice1`
-   is dead after any reboot, `bash scripts/site-baseleg.sh check office1` is the one-command diagnosis (skill
-   routing row).
-   **>> TEST REBOOT FORCED by operator 2026-07-17** (prove it now, not wait for a natural one). The session
-   that issued `sudo reboot` died with the host. **POST-REBOOT SESSION -- verify BEFORE any manual `ip`
-   command:** (a) `systemctl status site-baseleg-office1.service` = active(exited), status=0; (b) its journal
-   (`sudo journalctl -u site-baseleg-office1.service -b`) logs **`added leg`** (leg was absent at boot -> the
-   unit CREATED it) -- `leg present` would mean something else persisted it, weaker proof; (c) `bash
-   scripts/site-baseleg.sh check office1` -> ok; (d) `ssh voffice1` returns live with NO manual step. All four
-   PASS -> RETIRE this carry-forward and record "boot-race PROVEN 2026-07-17". Any FAIL -> the ordering/poll
-   needs work (widen `BRIDGE_WAIT`, re-check which daemon creates the bridge) -- do NOT retire.
+**CARRY-FORWARDS:**
+1. **Boot-race proof -- PROVEN 2026-07-18 (RETIRED).** The operator-forced test reboot (host booted
+   2026-07-17 23:38:41) exercised the `After=libvirtd`+poll race, and all four checks PASSED:
+   (a) `site-baseleg-office1.service` active(exited) status=0; (b) the unit journal logs
+   **`added leg: 10.10.0.10/24 on virbr2`** + `route set: 10.10.1.0/24 via 10.10.0.20 dev virbr2` at
+   23:38:53 -- the STRONG proof (leg ABSENT at boot -> the unit CREATED it, not "leg present"); (c) `bash
+   scripts/site-baseleg.sh check office1` -> ok; (d) `ssh voffice1` returned live with NO manual `ip`
+   command this session. So the D-126 base-leg oneshot self-heals `office1-local`'s dropped L3 leg across a
+   real reboot, unattended. (Journal read needed root; jessea123 was added to the `systemd-journal` group
+   2026-07-18 + relog so future sessions read unit journals without sudo.) Register item 20 / skill routing
+   row stand as the durable mechanism.
 2. **DC leg rows.** `site-baseleg.sh` generalizes to the DCs but a DC row is DEFERRED-until-measured (hard
    rule 2; the harness fails on an un-commented DC supernet). At each DC standup, MEASURE the vcloud->DC
    reach and add a MEASURED leg row + install ONLY if that net is isolated (register item 20 / skill invariant).