docs(lab): record the dry run of the -Version path of the sequence runner

Run-MatrixSequence.ps1 -Version 5.0.0-rc6 ran once on OSFile19 in
Windows PowerShell as a dry run. The controller used the published
module, the validation reported LIVE_RESULT_NOT_ACCEPTED as it must
(151 passed, 78 failed, 2 skipped: the live tests that rc6 predates), and
the cleanup verdict was CLEAN. It tests the mechanics and accepts nothing.
The deployment notes say how to pass the file servers and when to start
the evaluation client.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: AI Assistant <ai@example.com>

.memory-bank/deployment-notes.md

@@ -49,9 +49,17 @@ Local `-ModulePath` runs are validation; the gate needs the published bytes.
    the identity of the manifest. Dry run on rc6: all checks passed.
 2. `Tests/Lab/Invoke-NTFSSecurityLabTest.ps1 -Version <version>` in the
    existing lab, both editions, and `Tests/Lab/Acceptance/Run-MatrixSequence.ps1
-   -Version <version>` for each cell of the matrix (Decision 24). Check every
-   role from the result files with `Validate-LabResults.ps1`, never from the
-   marker `DONE` of the controller.
+   -Version <version>` for each cell of the matrix (Decision 24; pass the file
+   servers as one quoted string, `-FileServer 'OSFile19,OSFile22,OSFile25'`, and
+   start `OSWin11E` shortly before, because its license period ends an hour
+   after each start). Check every role from the result files with
+   `Validate-LabResults.ps1`, never from the marker `DONE` of the controller.
+   Dry run of the `-Version` path of the sequence runner with the published rc6
+   on OSFile19 (Desktop): the mechanics work, the failing tests are the newer
+   ones that rc6 predates, and the cleanup verdict was CLEAN. The first lab ran
+   the final local candidate through the same stages (readiness, controller,
+   `Validate-LabResults.ps1`, snapshot, `-RemoveFixture`, `Test-MatrixCleanup.ps1`
+   with the four domain controllers and both machines) in one detached driver.
 3. Remove the fixture and check the end state independently with
    `Test-MatrixCleanup.ps1`, which takes the lab name and the machine names
    (`-LabName WindowsAccessControlLab -DomainController F1ADC1, F1BDC1, F2DC1,

Tests/Lab/Acceptance-2026-10-10-os-matrix.md

@@ -625,7 +625,14 @@ fails, which the reuse of the name explains and the module doesn't.
   a release is the run with `-Version` of the exact prerelease from the
   PowerShell Gallery in every cell, which handoff 3 sequences after the maintainer
   decides which fixes belong to 5.0.0-rc7. The same cells have to be repeated for
-  a changed binary.
+  a changed binary. The `-Version` path of `Run-MatrixSequence.ps1` ran once as a
+  dry run with the published 5.0.0-rc6 on OSFile19 in Windows PowerShell (07:39 to
+  07:45 UTC, kit at `664ef3a`): the controller used the published module, the
+  validation reported `LIVE_RESULT_NOT_ACCEPTED` as it must (151 passed, 78
+  failed, 2 skipped: the live tests that rc6 predates, such as the later-command
+  tests, `Get-ChildItem2 -Filter`, `InheritedFrom`, and the two new ServerAdmin
+  tests), and the cleanup verdict was CLEAN. That tests the mechanics only and
+  accepts nothing.
 - Case 9 (accounts of other domains and forests) needs trusts that the matrix
   lab doesn't have; it runs only in `WindowsAccessControlLab`, where the
   baseline passed it and the final candidate passed it in run `fl1` (see "First