docs(memory-bank): record that the rc9 work items are running

The designs of Decision 27 are chosen, and four work items run in worktrees
under C:\Temp\ntfs-rc9 on the branch ai/rc9-before-stable. The inventory of
open decisions in progress.md now points to Decision 27.

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

.memory-bank/activeContext.md

@@ -25,12 +25,14 @@ of the new error, a computer name of 32,718 characters, holds on Server 2019,
 and this Memory Bank (#130, 08:47Z); `master` is `d0cb57c`. The new tests gave
 the same counts on the runner (three CI runs) and on six machine classes of the
 labs (24 runs, 0 failed). A probe found that a typo in a piped `AccessType`
-silently creates an Allow entry. He decided (Decision 27): rc9 fixes that
+silently creates an Allow entry. He decided (Decision 27) that rc9 fixes that
-family and the items 3 to 7 of its sheet, with a review. Open before the
+family and the items 3 to 7 of its sheet, with a review, and chose the
-stable pull request: rc9 (designs, tests, review, acceptance of about 70
+designs. Four work items run in worktrees under `C:\Temp\ntfs-rc9` (branch
-minutes), his decision on #34 on 2026-11-02, and his check of
+`ai/rc9-before-stable`; specs in the session folder `files\rc9\specs`). Open
-`PSGALLERY_API_KEY`. The stable change then touches only the label, the
+before the stable pull request: rc9 (integration, validation, review,
-CHANGELOG, and `$publishedVersions`.
+acceptance of about 70 minutes), his decision on #34 on 2026-11-02, and his
+check of `PSGALLERY_API_KEY`. The stable change then touches only the label,
+the CHANGELOG, and `$publishedVersions`.
 
 State at 2026-10-10: the maintainer integrated the release-gate stack into
 `master` (#116, #120, #118, #119, #121; `fa0701b`, CI green; GitHub closed #117
@@ -166,8 +168,8 @@ Decisions 22 and 24 on 2026-10-19 and decides 23 on 2026-11-02.
    `PSGALLERY_API_KEY` first, merges, and tags. Every release step is his.
 3. Decision 27 (2026-10-21): rc9 changes the library-only items, the dot
    patterns of `Get-ChildItem2 -Filter`, the 17 owner-restore handlers, the
-   errors of the descriptor sets, and three inconsistencies; designs are being
+   errors of the descriptor sets, and three inconsistencies; the designs are
-   researched. Decisions 22 and 24 are accepted (2026-10-19).
+   chosen, four work items are in progress. Decisions 22 and 24 are accepted.
 4. #34 waits for a tester until 2026-11-02 (Decision 23, option 3; the
    follow-up went up on 2026-10-19, no reply yet; checklist:
    `Tests/Lab/Non-Windows-File-Server-Test.md`). On that date the maintainer

.memory-bank/progress.md

@@ -136,7 +136,9 @@ Gallery version: 4.2.6. After 5.0.0, archive in favor of WindowsAccessControl
   merged #129 (08:24Z) and #130 (08:47Z); the new tests passed in three CI
   runs and in 24 lab runs on six machine classes (0 failed). A probe then
   found that piped optional parameters ignore a bad value (a typo for Deny
-  creates an Allow entry); Decision 27 sets the scope of rc9.
+  creates an Allow entry); Decision 27 sets the scope of rc9, the designs were
+  chosen on 2026-10-21, and four work items started (branch
+  `ai/rc9-before-stable`).
 
 ## Stable capabilities
 
@@ -177,10 +179,9 @@ Gallery version: 4.2.6. After 5.0.0, archive in favor of WindowsAccessControl
    (`2112ee3`): 402 unvisited sequence points in 183 methods, all classified
    (`Tests/Coverage`): 167 explained from source with evidence, 16 open (8:
    `FileSecurity` conversions, `RemoveAll` account filters; 8 getters of
-   pipeline parameters that no test binds by property name). Other open
+   pipeline parameters that no test binds by property name). Decision 27: rc9
-   decisions: lazy path overloads, abandoned `PrivilegeEnabler`, dot patterns
+   fixes the conversions, `RemoveAll`, the lazy overloads, the dot patterns,
-   of `Get-ChildItem2 -Filter`, 17 owner-restore handlers that do not pass on
+   and the 17 handlers; `PrivilegeEnabler` and unused classes stay. No
-   what a later command raises (a rare combination), unused classes. No
    trigger for an audit write's ownership retry was found on a local volume or
    a Windows file server (probe of 48 calls) and no test reaches it. A
    conditional ACE display remains a .NET representation limit, not evidence