Document webhook target, automatic restoration and complete removal

docs/WEBHOOKS.md

@@ -40,6 +40,20 @@ python whatsapp.py webhook stop --config listener.json
 
 Then stop the receiver with Ctrl+C. Re-enable with `webhook install --restore --config listener.json`. Stopping only the injected listener without disabling a restoring configuration causes the receiver to reinstall it.
 
+### Completely remove automatic restoration
+
+`stop --config` disables restoration in the configuration, but keeps the scheduled task registered. To remove it entirely, first disable the exact task named in your configuration, then stop the listener and unregister that task:
+
+```powershell
+$listenerConfig = Get-Content -LiteralPath listener.json -Raw | ConvertFrom-Json
+Disable-ScheduledTask -TaskName $listenerConfig.restore_task | Out-Null
+python whatsapp.py webhook stop --config listener.json
+Unregister-ScheduledTask -TaskName $listenerConfig.restore_task -Confirm:$false
+Remove-Item -LiteralPath listener.json
+```
+
+These task commands apply only when `--auto-restore` was used. Remove the adjacent `listener.status.json` diagnostic file if present. Restart WhatsApp normally to unload the stopped helper DLL; the listener stays absent because the task is removed. No WhatsApp package files need restoring. The development workstation's test task and protected configuration were removed after validation, and WhatsApp was restarted to clear the injected listener/helper.
+
 ## Payload and integration
 
 The loopback endpoint is `POST /whatsapp-webhook` on `127.0.0.1`; direct HTTPS uses the explicitly configured URL. Batches include `listener_id`, `seqs` and `events`. Each message event includes a sequence number, message ID, chat ID, timestamp, direction, message type, body/caption and text-length/truncation metadata. The built-in receiver persists events in SQLite; an external receiver can feed them to a summarizer. No AI provider or automatic replies are configured.