docs(lab): record the live tests of the published 5.0.0-rc6

The tag 5.0.0-rc6 published the package to the PowerShell Gallery; the
Release job failed after the upload, because Publish-PSResource gave up
waiting while the Gallery accepted the package and its retry got 409. The
live tests downloaded the package, checked the hash of the Gallery, and
passed in both editions, except the one test whose expected warning text
5.0.0-rc7 changed. The rc6 record gets a section on the release; the run
is the baseline of the rc7 record.

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

Tests/Lab/Acceptance-2026-10-08-5.0.0-rc6.md

@@ -145,5 +145,28 @@ deletes them.
   gate.
 - File servers that aren't Windows, such as the IBM ESS system of #34:
   only the feedback of the reporter covers them.
-- The package that CI publishes for the tag: the live tests run against it
+
-  after the release, with `-Version 5.0.0-rc6`.
+## After the release
+
+The tag `5.0.0-rc6` on `b51d970`, the merge of #115, published the package
+to the PowerShell Gallery on 2026-10-08 at 20:40 UTC. The **Release** job
+failed after the upload: `Publish-PSResource` stopped waiting for the
+Gallery after 100 seconds while the Gallery accepted the package, and its
+second attempt got the error 409, "already exists". So the job didn't
+create the GitHub release; rerunning the failed job creates it, as
+[If a release fails](../../Docs/Contributing/05-Releasing.md#if-a-release-fails)
+describes.
+
+`Invoke-NTFSSecurityLabTest.ps1 -Version 5.0.0-rc6` downloaded the package
+from the Gallery, checked it against the SHA-512 that the Gallery
+publishes, and ran in both editions, 20:43 to 21:00 UTC. The SHA-256 of
+`NTFSSecurity.5.0.0-rc6.nupkg` is
+`83EBCADEE0698A9523661352A69B9D25F6EB2903F45A6C4FAB36F5BF4B139100`.
+
+The live tests came from the branch of 5.0.0-rc7, which expects the
+warning of `Get-NTFSEffectiveAccess` for a computer that can't be reached
+to name the computer. The package failed only that test, in the role Admin
+of both editions, with exactly the text that the live tests of 5.0.0-rc6
+expect; every other test passed: Delegate 38, ServerAdmin 13, Admin 39,
+and Server 72 with 1 skipped, in each edition. The fixture was removed at
+21:03 UTC, and its removal checked as above.

Tests/Lab/Acceptance-2026-10-08-5.0.0-rc7.md

@@ -106,15 +106,20 @@ a checkpoint, from 16:04 to 16:20 UTC.
 
 ## Baseline
 
-None. 5.0.0-rc6 isn't published yet, and the live tests changed only in
+The published 5.0.0-rc6 from the PowerShell Gallery, whose hash the script
-the text that they expect from the warning of `Get-NTFSEffectiveAccess`
+checks against the one the Gallery publishes, in both editions, 20:43 to
-for a computer that can't be reached, which names the computer now. The
+21:00 UTC, with the same live tests. It failed one test in each edition,
+the warning of `Get-NTFSEffectiveAccess` for a computer that can't be
+reached, which names the computer since 5.0.0-rc7: Admin 39 passed and 1
+failed; Delegate 38, ServerAdmin 13, and Server 72 with 1 skipped passed.
+The live tests find no other difference between the two versions; the
 local tests cover the other changes of 5.0.0-rc7.
 
 ## Cleanup
 
 `Invoke-NTFSSecurityLabTest.ps1 -RemoveFixture` at 16:21 UTC, after the
-first two runs, and at 16:44 UTC, after the acceptance. Each check
+first two runs, at 16:44 UTC, after the acceptance, and at 21:03 UTC,
+after the baseline. Each check
 compared the lab with the 10 SIDs of the fixture's accounts and groups,
 read before the removal, which found the fixture. After each removal: