{"version":"2.1.239","anchor":"relay-delivered-turns-can-count-as-verified-human-turns","canonical_anchor":"relay-delivered-turns-can-count-as-verified-human-turns","heading":"Relay-delivered turns can count as verified human turns","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/relay-delivered-turns-can-count-as-verified-human-turns","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Relay-delivered turns can count as verified human turns\n\nRelayed messages can now count as coming from a real person, unless they inlined image attachments.\n\n**What**\n\nThe three new relay routing fields carried on a user message now feed the check that decides whether a turn came from a real person, alongside the existing verified-Slack marker. A turn that inlined image attachments is excluded from that path.\n\n**Details**\n\n- Queued user messages now carry the list of inlined image paths, and the prompt-prefix builder returns it (empty by default); the verified-turn predicate requires that list to be empty.\n- A Slack connect consent dialog was added to the dialog-cancel handling.\n- Whether the relay path itself is switched on is decided elsewhere, not in this code.\n\n**Evidence**\n\n`hearthRelayThreadTs`, `inlinedImagePaths`\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}