diff --git a/clients/valleywide/session-logs/2026-07/2026-07-07-howard-vwp-server-clock-backup-2525.md b/clients/valleywide/session-logs/2026-07/2026-07-07-howard-vwp-server-clock-backup-2525.md
index ae7e1ef3..f51fd6f5 100644
--- a/clients/valleywide/session-logs/2026-07/2026-07-07-howard-vwp-server-clock-backup-2525.md
+++ b/clients/valleywide/session-logs/2026-07/2026-07-07-howard-vwp-server-clock-backup-2525.md
@@ -75,3 +75,36 @@ Then investigated the remaining backup breakage via `/msp360` and `cbb.exe` on t
 - RMM cmd ids: timezone change `61a2e177`; various diagnostics.
 - Discord DM to Mike: message_id `1524081568828882985`. Bot alert to #dev-alerts: message_id `1524076358605475982`.
 - Client slug: `valleywide`.
+
+## Update: 21:17 PT — waiting on Mike + repo scratch hygiene
+
+**VWP-SERVER backup 2525 — still blocked on Mike.** DM'd him the root cause + two fix options
+(15:56). No reply through the afternoon. Set up a self-paced poll of his Discord DM
+(`discord-dm.sh read mike`) via ScheduleWakeup at ~20-25 min intervals; polled 3x, no reply;
+user then said to end the checking, so the loop was stopped (ScheduleWakeup stop). **Nothing on
+the backup has been changed** — the remediation (delete the 2051-07-10 restore point in the agent
+Backup Storage view, then run the plan once for a fresh 2026 baseline, preserving ~509 GB history)
+is still pending Mike's decision. Resume point: re-check his DM, act on his choice, then rebuild
+the wiki (`/wiki-compile client:valleywide --full`).
+
+**Repo scratch/token hygiene (from `/sync`).** A `git add -A` sweep committed stray root scratch
+files. Cleaned up:
+- Untracked + removed 9 `.rmm*` scratch files that prior sessions had committed to repo root
+  (`.rmm_token`, `.rmm_b64_localadmin`, `.rmm-key-probe.ps1`, `.rmm-scan.ps1`, `.rmm_change_cmd`,
+  `.rmm_cmds`, `.rmm_desktop_cmd`, `.rmm_server_cmd`, `.rmm_station2_cmd`). Committed `8b016ed`.
+- Security check on the committed secrets: `.rmm_token` was a GuruRMM **admin** JWT but already
+  **expired** (`exp 2026-07-06 06:28 UTC`, ~30h prior) — no rotation needed. `.rmm_b64_localadmin`
+  was an `-EncodedCommand` PowerShell *script* (blanks a Localadmin password), not a stored secret.
+  Files remain in git history (left as-is; nothing live exposed).
+- Added `.gitignore` rules: `.rmm*` and `.vwp*` under the Session-scratch section.
+- Later removed 3 more untracked scratch files (`scratch-audit-functions.ps1`,
+  `scratch-audit-policies.ps1`, `.rmm_token.tmp`).
+- Found 11 **tracked** `scratch-*.ps1` files (all Howard, dated today) that are a coherent
+  **AD/DC-promotion + Windows Server Backup migration** working set (functional-level preflight,
+  DC-promo/CA dry-runs, robocopy preseed, SMB share for machine-account migration, start-backup).
+  Per user decision: **left tracked, untouched** — likely an active migration. Did NOT add a
+  blanket `scratch-*` ignore (would misrepresent tracked files).
+
+**Pending / next steps:**
+- Get Mike's answer on the VWP-SERVER backup fix; execute; then `/wiki-compile client:valleywide --full`.
+- The 11 `scratch-*.ps1` migration scripts are an open/active workstream (separate from the 2525 issue).