diff --git a/CHANGES.md b/CHANGES.md
index 62005e7..182a90e 100644
--- a/CHANGES.md
+++ b/CHANGES.md
@@ -59,7 +59,7 @@ concern - readable here, never shipped as something to parse.
 
 ---
 
-## 8.0.0-beta.8 - 2026-09-30 - Bug-report collector can pseudonymise identities, in two stages
+## 8.0.0-beta.9 - 2026-09-30 - bug-report instruction: step 1 no longer calls every bundle unpseudonymised
 
 **Author:** Torben Nehmer
 
@@ -113,8 +113,15 @@ concern - readable here, never shipped as something to parse.
 - Demo corpus follows the decided project pages: three states, seed with their items (#156)
 - bug-report instruction: offer WIKI_TRACE=1 for a reproduction
 - reports/CONTRACT.md: only the collector's two counting calls take the bugreport session id
+- bug-report instruction: step 1 no longer calls every bundle unpseudonymised
 <!-- /wikitool:bumps -->
 
+### bug-report instruction: step 1 no longer calls every bundle unpseudonymised
+
+Step 1 told the agent to announce that the bundle "is not pseudonymised" and then, one paragraph
+later, to offer `--pseudonymise`. It now says the bundle holds machine, user and path names and the
+git remotes unless it is pseudonymised.
+
 ### Bug-report collector can pseudonymise identities, in two stages (Gitea #158)
 
 A bundle carries machine, user and path names, and an installation failure usually turns on the
diff --git a/VERSION b/VERSION
index bc4d1e9..c5f6633 100644
--- a/VERSION
+++ b/VERSION
@@ -1 +1 @@
-8.0.0-beta.8
+8.0.0-beta.9
diff --git a/instructions/bug-report.md b/instructions/bug-report.md
index 9b4da3f..c74ac09 100644
--- a/instructions/bug-report.md
+++ b/instructions/bug-report.md
@@ -82,8 +82,8 @@ session. The bundle does not leave that place because of it.
 ## Steps
 
 1. **Tell the user what is about to happen**, in the instance's KB language: a bundle will be written
-   under `reports/`, it is not pseudonymised, it holds machine, user and path names and the git
-   remotes, and it is not sent anywhere. Ask whether the session trace, page titles and transcripts
+   under `reports/`, it holds machine, user and path names and the git remotes unless it is
+   pseudonymised (below), and it is not sent anywhere. Ask whether the session trace, page titles and transcripts
    may go in. The defaults are: trace in, titles out, no transcripts.
 
    Ask which channel the bundle will take, and recommend pseudonymisation for every channel except a