docs: how a sideloaded build is removed from the watch

The watch removes the .prg after installing it; the app is removed from
the watch's own menu and its fr70.* storage files deleted by hand.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2 files changed, 6 insertions, 3 deletions

diff --git a/docs/DEVELOPER_GUIDE.md b/docs/DEVELOPER_GUIDE.md
index 77d2f02..d33f383 100644
--- a/docs/DEVELOPER_GUIDE.md
+++ b/docs/DEVELOPER_GUIDE.md
@@ -144,7 +144,7 @@ Debug builds print `DIAG first_frame startup_ms=... mem_used=... mem_total=...`
   2. Add the setting to `resources/settings/settings.xml` and its strings to `resources/strings/strings.xml`. `make lint` validates both against the SDK schema and checks that they agree (`tools/check_resources.py`).
   3. Read the fields through a `Forms.Store` in a reader like `source/settings/OtpForm.mc`, so tests can use `Forms.MemoryStore`. Put every field in the form's hash content and its default in the form's `defaults()`; the test `settingsDefaultsMatchProperties` checks those against `properties.xml`.
   4. Add a phase to `SettingsJob` in README 10.3 order. Heavy work (encoding, many records) goes into its own steps: one step is one timer event under the watchdog.
-- **On-watch numbers**: sideload a debug build (`make build DEVICE=fr70`, copy `build/debug/fr70.prg` to the watch's `GARMIN/APPS` folder over USB). Then open the menu and choose "Debug: benchmark".
+- **On-watch numbers**: sideload a debug build (`make build DEVICE=fr70`, copy `build/debug/fr70.prg` to the watch's `GARMIN/APPS` folder over USB). Then open the menu and choose "Debug: benchmark". The watch installs the app and removes the `.prg` from the folder; to remove the app, use the watch's own app menu, then delete the `fr70.*` storage files in `GARMIN/APPS/DATA` and `GARMIN/APPS/SETTINGS` ([YOUR_STEPS.md](YOUR_STEPS.md#45-remove-the-debug-build)).
 - **A barcode symbology**: add an encoder module under `source/codes/` and dispatch to it in `Codes.encode`. Then:
   - Add reference rows in `tools/gen_code_vectors.py` (zxing-cpp's writer, or segno for QR) and run `make codes`.
   - Add `CODEDUMP` lines for seeded payloads in its test, so `tools/check_codes.py` decodes them in every test run.
diff --git a/docs/YOUR_STEPS.md b/docs/YOUR_STEPS.md
index c6b5d07..1a66761 100644
--- a/docs/YOUR_STEPS.md
+++ b/docs/YOUR_STEPS.md
@@ -104,6 +104,8 @@ The debug build has fake demo entries and the on-watch benchmark. It gets no pho
 3. Copy `build/debug/fr70.prg` into the folder `GARMIN/APPS` (on some watches `GARMIN/Apps`).
 4. Eject the watch and unplug it. The app "OTP Wallet" appears in the watch's apps list.
 
+The watch installs the app and then removes `fr70.prg` from `GARMIN/APPS`, so the file isn't there afterwards. The app's storage shows up as `fr70.DAT`, `fr70.IDX` and `fr70.IMT` in `GARMIN/APPS/DATA`, and `fr70.SET` in `GARMIN/APPS/SETTINGS`. A sideloaded app never appears in the Connect IQ Store app.
+
 If the watch doesn't show up in the file manager, stop and tell me. Don't install anything on the computer for this without us talking first.
 
 ### 4.2 Benchmark
@@ -139,8 +141,9 @@ While a card is open: the backlight should be on (the Forerunner 70 has a MIP sc
 
 ### 4.5 Remove the debug build
 
-1. Connect the watch over USB again, delete `fr70.prg` from `GARMIN/APPS`, eject, unplug.
-2. Check that OTP Wallet is gone from the apps list.
+1. On the watch, remove OTP Wallet: highlight it in the apps list, hold UP (MENU) and choose **Remove**, or find it under **Settings**, **Activities & Apps** (or **Apps**). The exact labels on the Forerunner 70 may differ.
+2. Connect the watch over USB and delete its leftover storage: `fr70.DAT`, `fr70.IDX` and `fr70.IMT` in `GARMIN/APPS/DATA`, and `fr70.SET` in `GARMIN/APPS/SETTINGS`. Leave every other file alone: files with 8-character names such as `G7AA3237.*` belong to apps installed from the Store (Settings Spike and others).
+3. Eject, unplug, and check that OTP Wallet is gone from the apps list.
 
 ## Part 5: Store beta, and the update from 0.7.0 to 0.8.0