docs: reports contract names only the collector's two counting calls under its session id; INSTALL.md qualifies the title claim (#157)

Files changed:
- CHANGES.md
- INSTALL.md
- VERSION
- reports/CONTRACT.md

CHANGES.md

@@ -59,7 +59,7 @@ concern - readable here, never shipped as something to parse.
 
 ---
 
-## 8.0.0-beta.6 - 2026-09-30 - bug-report instruction: offer WIKI_TRACE=1 for a reproduction
+## 8.0.0-beta.7 - 2026-09-30 - reports/CONTRACT.md: only the collector's two counting calls take the bugreport session id
 
 **Author:** Torben Nehmer
 
@@ -111,8 +111,24 @@ concern - readable here, never shipped as something to parse.
 - new_page/type_resolver comments no longer claim only entities declare a layout:
 - 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
 <!-- /wikitool:bumps -->
 
+### reports/CONTRACT.md: only the collector's two counting calls take the bugreport session id
+
+The contract said all of the collector's `wikitool` calls run under `bugreport-<stamp>`. Only
+`instructions verify` and `docs verify` do; `version show`, `doctor` and `budget status` inherit
+the caller's id, as `gates.md` and the script already said. `INSTALL.md`'s troubleshooting entry
+also no longer claims page titles stay out of the whole bundle: they stay out of what the script
+generates, while the trace - included by default - may carry them.
+
+### bug-report instruction: offer WIKI_TRACE=1 for a reproduction
+
+A distributed instance records no trace by default, so the default "trace in" often had nothing to
+include. `instructions/bug-report.md` now offers, when the failure can be reproduced, to repeat the
+failing step in one new shell with `WIKI_TRACE=1` set for that session only - never by changing
+the checkout's telemetry configuration.
+
 ### Bug-report collector: tools/bugreport.py and instructions/bug-report.md (Gitea #157)
 
 A failure on one machine used to reach the maintainer as a description. `tools/bugreport.py` now

INSTALL.md

@@ -477,8 +477,10 @@ tools/wikitool instructions verify
   [instructions/bug-report.md](instructions/bug-report.md) ausführen lassen, oder direkt
   `python3 tools/bugreport.py`. Das Skript braucht nur Python 3.8 oder neuer, läuft auch ohne
   funktionierendes `wikitool` und schreibt ein Bündel nach `reports/bugreport-<Zeitstempel>/`
-  samt Zip. Geheimnisse werden entfernt, Seitentitel bleiben draußen (`--titles` nimmt sie mit);
-  das Bündel enthält trotzdem Maschinen-, Benutzer- und Pfadnamen. Es wird nirgends hochgeladen -
+  samt Zip. Geheimnisse werden entfernt, und aus allem, was das Skript selbst erzeugt, bleiben
+  Seitentitel draußen (`--titles` nimmt sie mit). Der Sitzungs-Trace ist standardmäßig dabei
+  (`--no-trace` lässt ihn weg) und kann wie Chronologie und Transkripte Seiteninhalt und Titel
+  enthalten; das Bündel enthält außerdem Maschinen-, Benutzer- und Pfadnamen. Es wird nirgends hochgeladen -
   den Kanal wählst du selbst.
 - **Ich will am Tool-Stack selbst weiterarbeiten (nicht nur Wiki-Inhalt betreiben)** - eine neue
   Instanz hat dafür keinen Weg: `dist export` lässt `instructions/dev/` (Stack-Entwicklung,

VERSION

@@ -1 +1 @@
-8.0.0-beta.6
+8.0.0-beta.7

reports/CONTRACT.md

@@ -50,8 +50,10 @@ session trace, the chronology and transcripts, which may hold page content and t
 removed by the collector; the rest is the reader's to check before a bundle leaves the machine.
 Nothing uploads it: the channel is the user's choice.
 
-The collector's own `wikitool` calls run under the session id `bugreport-<stamp>`, so a
-`reports/telemetry/bugreport-*` directory is that run's trace and belongs to no session of yours.
+The collector's two counting `wikitool` calls (`instructions verify`, `docs verify`) run under the
+session id `bugreport-<stamp>`; its budget-exempt ones inherit the caller's. A
+`reports/telemetry/bugreport-*` directory is therefore that run's trace and belongs to no session
+of yours.
 
 ## Retention