Add engagement-only conversation mode

docs/data-flow.md

@@ -88,7 +88,9 @@ flowchart TD
     CLAIM -- sent --> IGNORE
     CLAIM -- pending --> RECON["Reconcile against Matrix history"]
     CLAIM -- no --> STATE["Load or snapshot conversation policy"]
-    STATE --> STOP{"Manual, seller, image, boundary, unsafe, or turn limit?"}
+    STATE --> ENGAGE{"Engagement-only policy?"}
+    ENGAGE -- yes --> COMPLETE["Record response goal; mark triage done"]
+    ENGAGE -- no --> STOP{"Manual, seller, image, boundary, unsafe, or turn limit?"}
     STOP -- yes --> HANDOFF["Persist terminal/human-required outcome"]
     STOP -- no --> GEN["Generate policy-specific reply"]
     GEN --> SAFE{"Outbound checks pass?"}
@@ -104,6 +106,8 @@ flowchart TD
 
 The inbound event key, intended reply, claim status, and conversation state make retries idempotent. Immediately after any limiter wait, automation refreshes Matrix and revalidates the latest inbound event, boundaries, images, the shared seller/off-platform decision, policy status, and the one-media-request limit. Newer state makes the old claim terminally `superseded`; it is never sent. If the replacement event is a seller or off-platform push, the same revalidation ends and classifies the conversation instead of leaving it for a later pass. If the process dies after Matrix accepted a reply, reconciliation finds the outbound event and marks the old claim sent instead of sending it again.
 
+Engagement-only conversations use the same confirmed-opener, durable-state, and newest-inbound eligibility checks, but stop before reply claims, media exchange, second-stage screening, or generation. The first verified reply persists the `engaged` terminal state, supersedes any stale claim defensively, and resolves triage to Done. Seller/off-platform rules still run during the shared retrospective scan and may classify the conversation more specifically, but neither path sends a reply.
+
 General R4R generation explicitly permits consensual adult NSFW conversation. A model response that softly refuses, moralizes, or diverts solely because the topic is sexual is rejected before send and falls through to the next configured chat model. General replies may offer a generic approved saved picture without that offer being miscounted as a request for recipient media. Prompt instructions and deterministic output validation also keep generated private-chat text within deliverable capabilities: text and the approved saved-picture flow are supported, while voice notes, audio messages, and live voice/video/phone calls are rejected before a suggestion or automated reply can proceed.
 
 Legacy conversations may make at most one optional autonomous media request, including a request already present in the opener. The hybrid policy retains its single rapport-gated media ask. Deterministic, sequence-aware refusal checks run before generation and again at send time; generated media asks must pass the same non-explicit, non-coercive validator.