diff --git a/.memory-bank/activeContext.md b/.memory-bank/activeContext.md
index 891adcc..3bae459 100644
--- a/.memory-bank/activeContext.md
+++ b/.memory-bank/activeContext.md
@@ -137,7 +137,11 @@ open.
   Reviewed by the built-in code-review agent (custom `security-reviewer`
   unavailable): approve with Minor, fixed; a second review found one Major
   (record accuracy), addressed by the replay; a follow-up review found no
-  Blocker or Major and five Minors, corrected.
+  Blocker or Major and five Minors, corrected; a second follow-up review found no
+  Blocker or Major and four Minors, corrected. State of the labs at 07:30 UTC on
+  2026-10-10: no fixture and no probe residue in either lab (`Verify` of the
+  matrix lab 06:54, of the first lab 07:29); the six VMs of the matrix run, and
+  `OSWin11E` (started 06:44) shuts itself down about an hour after its start.
 
 ## Next step
 
diff --git a/.memory-bank/progress.md b/.memory-bank/progress.md
index 27e2210..1fc4db9 100644
--- a/.memory-bank/progress.md
+++ b/.memory-bank/progress.md
@@ -103,7 +103,9 @@ After 5.0.0, archive in favor of WindowsAccessControl (Decision 18).
   `db04ef2`. A second review of the later commits found one Major (the record
   called the cause settled without a baseline replay), addressed by the replay,
   `9344ff7`, and `ab0d8e1`; a follow-up review of those fixes found no Blocker or
-  Major and five Minors, corrected in `e2384e5` and `70f494a`. Record:
+  Major and five Minors, corrected in `e2384e5` and `70f494a`; a second
+  follow-up review (the first-lab run and the cleanup changes) found no Blocker or
+  Major and four Minors, corrected in `b78784d` and `dbb4bd6`. Record:
   `Tests/Lab/Acceptance-2026-10-10-os-matrix.md`; nothing was pushed.
 
 ## Stable capabilities