#787 HITL gates reads same as side-effects -> approval spam on research (research->approve->act)

run_goal/_deferred with approval gates tools.http.request regardless of whether it's a READ (GET to research a page) or a SIDE-EFFECT (POST to a webhook). A 'research X, ask approval, then email/webhook' prompt therefore asks the user to approve EVERY research page fetch (Trump U -> Trump Shuttle -> ...), instead of one approval for the actual outbound actions. Customer-facing: the simplest research+approval+action workflow becomes an approval slog. FIX: make HITL side-effect-aware -- auto-allow reads (http GET, search.web) and gate only writes/sends (http POST/PUT/PATCH/DELETE, email.send, shell.run, mcp side-effects). Verified: the SAME task unattended (require_approval=false) ran clean end-to-end (webhook.site captured the real JSON POST + the emailhook email via Highway SMTP), so engine/tools are fine -- defect is the approval policy granularity.