chore(memory-bank): record that the maintainer opens PRs

The remote-mutation hook blocked creating the pull requests even after
the maintainer's explicit request: its override is read from the
environment that VS Code starts the hook with, so the agent can't set
it for a single command. The hook also matches text inside commit
messages.

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

.memory-bank/activeContext.md

@@ -9,9 +9,10 @@ source: current task evidence
 
 ## Current focus
 
-Work packages 1 and 2 are pushed; the maintainer opens their PRs:
-`ai/housekeeping` into `master`, and `ai/ship-help` into
-`ai/housekeeping`. The work packages and their order are in `progress.md`.
+Work packages 1 and 2 are pushed and green; the maintainer opens their
+PRs: `ai/housekeeping` into `master`, and `ai/ship-help` into
+`ai/housekeeping`. The agent can't open them (see `techContext.md`,
+Constraints). The work packages and their order are in `progress.md`.
 
 ## Evidence
 
@@ -22,9 +23,9 @@ Work packages 1 and 2 are pushed; the maintainer opens their PRs:
 - The same build listed 870 tests on the Tests tab: the NUnit import files
   each Pester 5 test under every enclosing block (Pester, file, Describe,
   Context), so 216 tests appear four times and 2 three times. The
-  follow-up commit on `ai/ship-help` reports the results through the build
-  worker API instead (`POST api/tests/batch`), one entry per test; a local
-  run of step 04 against a sample test file sent 11 entries for 11 tests.
+  follow-up commit `c9fbaf5` reports the results through the build worker
+  API instead (`POST api/tests/batch`); AppVeyor 54834216 of `c9fbaf5`
+  passed and lists 218 tests, one entry each.
 - The AppVeyor job log API returns `application/octet-stream`; decode the
   bytes as UTF-8 before searching it.
 - Merging work package 1 with a merge commit keeps `ai/ship-help` valid;
@@ -35,6 +36,5 @@ Work packages 1 and 2 are pushed; the maintainer opens their PRs:
 
 ## Next step
 
-The maintainer pushes the follow-up commit on `ai/ship-help`, opens both
-PRs, and checks that AppVeyor lists 218 tests; then work package 3 (Read
-the Docs).
+The maintainer opens both PRs with the prepared `gh pr create` commands;
+then work package 3 (Read the Docs) after the go-ahead.

.memory-bank/techContext.md

@@ -70,6 +70,15 @@ source: repository evidence
 - `CHANGELOG.md` lists user-visible changes only; CI and build-only changes
   get no entry
   ([Decision 7](decisions/0007-changelog-user-visible-only.md)).
+- Remote mutations are the maintainer's: the user-level preToolUse hook
+  `Block-RemoteMutation.ps1` denies `git push` and mutating `gh` commands
+  (`pr create`, `pr close`, and others) from the agent session, even after
+  an explicit request. Its override, `COPILOT_ATELIER_ALLOW_REMOTE=1`, is
+  read from the environment that VS Code starts the hook with; setting it
+  inside an agent command has no effect (verified 2026-10-04). The hook
+  matches the whole command text, so a commit message that quotes such a
+  command is blocked too. Prepare the commands and descriptions; the
+  maintainer runs them.
 
 ## Validation