1. In Windows PowerShell using the daemon's SPT_HOME, back up: `$p=Join-Path $(if($env:SPT_HOME){$env:SPT_HOME}else{Join-Path $env:LOCALAPPDATA 'spt-core'}) 'daemon.json'; $bak="$p.302.$([DateTime]::UtcNow.ToString('yyyyMMddHHmmss')).bak"; Copy-Item -LiteralPath $p -Destination $bak -ErrorAction Stop`. Verified here: `C:\Users\decid\AppData\Local\spt-core\daemon.json`.
2. Set all three file-backed periods, preserving other settings and UTF-8: `$c=Get-Content -Raw -Encoding UTF8 -LiteralPath $p | ConvertFrom-Json; foreach($k in 'notif_pump_period_ms','registry_pump_period_ms','sync_pull_period_ms'){$c | Add-Member -NotePropertyName $k -NotePropertyValue 600000 -Force}; [IO.File]::WriteAllText($p,($c | ConvertTo-Json -Depth 100),[Text.UTF8Encoding]::new($false))`.
3. Run `spt node refresh`; require success. This reloads coordinator config while retaining the broker, PTYs, and net runtime; do NOT stop/start the daemon. Let the initial priming burst settle before timing.
4. Exercise the affected local and remote spt rc sessions for ~2 minutes: hitch gone supports pump-round attribution (#1/#2); repeated hitch persists after priming means not cadence-driven pump work. Wake-triggered rounds remain possible; this does not separate #1 from #2.
5. Restore exactly: `Copy-Item -LiteralPath $bak -Destination $p -Force -ErrorAction Stop; spt node refresh`. Require success; compare whether the original hitch returns, and report both arms. Keep the backup with the observation.