For stalled-workflow automations, treat a current-episode, durable human contact as an…

For stalled-workflow automations, treat a current-episode, durable human contact as an ownership boundary: suppress automated guidance and the first legacy reminder, then re-check immediately before provider submission to close race windows. Keep later reminders unchanged unless policy explicitly reassigns them. This applies only when the human action is attributable and unambiguously linked to the same active episode; it should not be inferred from inbound, automated, ambiguous, or older activity.

Evidence/example (2026-09-19): Shield staging commit 1b622fe applies this to accepted outgoing human SMS and connected outgoing human calls, plus human support events. PR #955.