diff --git a/docs/manual/runs.md b/docs/manual/runs.md
index 9261fb9..384f30c 100644
--- a/docs/manual/runs.md
+++ b/docs/manual/runs.md
@@ -13,7 +13,7 @@ A run is not analogous to a unit test. A closer framing is: boot a fuzzer for an
 ```
 sanderling test --spec spec.ts --bundle-id com.example.app --duration 30m
   │
-  ├── uninstall and reinstall the app (clean slate, every run)
+  ├── launch the app under test (pass --clear-data to wipe app data first)
   ├── boot the sidecar, connect the agent socket
   ├── bundle the spec, load it into goja
   │
@@ -26,6 +26,10 @@ sanderling test --spec spec.ts --bundle-id com.example.app --duration 30m
               └── meta.json
 ```
 
+## App state across runs
+
+By default the installed app is left in place between runs. Whatever state the previous run left behind (account, cached responses, onboarding completion) carries over. Pass `--clear-data` to wipe app data before launch and start cold every run. See [CLI reference](./cli/#sanderling-test) for the flag.
+
 ## Why runs are long and linear
 
 sanderling does not restart the app every N steps. Each restart throws away two things.