From d4f8dc51b9deb181aa1bd366979a9209686574f5 Mon Sep 17 00:00:00 2001
From: Daniel Samson <12231216+daniel-samson@users.noreply.github.com>
Date: Sun, 9 Aug 2026 14:19:39 +0100
Subject: [PATCH] =?UTF-8?q?docs:=20the=20hot-plug=20matrix=20is=20complete?=
 =?UTF-8?q?=20=E2=80=94=20124/124?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 docs/hot-plug-matrix-plan.md | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/docs/hot-plug-matrix-plan.md b/docs/hot-plug-matrix-plan.md
index 21106fc..1b22582 100644
--- a/docs/hot-plug-matrix-plan.md
+++ b/docs/hot-plug-matrix-plan.md
@@ -1,5 +1,12 @@
 # The hot-plug matrix: unplug anything, replug anywhere
 
+*Status: COMPLETE, 2026-08-09, same day — H1..H5 all green, full suite 124/124.
+The predicted cascade bug was real and found by H2: `tearDownPort` did not recurse
+into a hub yanked from a root port, so its subtree stayed live against vanished
+hardware and the replugged hub found its port occupied; fixed by mirroring
+`tearDownHubDevice`'s children-first recursion (77e7001). Every other cell passed
+against the establishment-track machinery unchanged.*
+
 *2026-08-09. The requirement, verbatim: "i want to be able to unplug devices and
 plug them back in, in any order and on any hub." The machinery exists end to end —
 per-device driver processes, cascading teardown (`tearDownHubDevice` recurses a